Search (8 results, page 1 of 1)

0.040652603 = product of:
  0.081305206 = sum of:
    0.05588421 = weight(_text_:services in 2629) [ClassicSimilarity], result of:
      0.05588421 = score(doc=2629,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.3245064 = fieldWeight in 2629, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0625 = fieldNorm(doc=2629)
    0.025421001 = product of:
      0.050842002 = sum of:
        0.050842002 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.050842002 = score(doc=2629,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.30952093 = fieldWeight in 2629, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2629)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

The report discusses metadata strategies employed and problems encountered during the first step of transforming the DDC into a Web information resource. It focuses on the process of URI design, with regard to W3C recommendations and Semantic Web paradigms. Special emphasis is placed on usefulness of the URIs for RESTful web services.

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.038381025 = product of:
  0.07676205 = sum of:
    0.055445895 = weight(_text_:services in 1752) [ClassicSimilarity], result of:
      0.055445895 = score(doc=1752,freq=14.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.32196122 = fieldWeight in 1752, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1752)
    0.021316158 = product of:
      0.042632315 = sum of:
        0.042632315 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
          0.042632315 = score(doc=1752,freq=10.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.2595412 = fieldWeight in 1752, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1752)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Content

"Although the Dewey Decimal Classification is currently available on the web to subscribers as WebDewey and Abridged WebDewey in the OCLC Connexion service and in an XML version to licensees, OCLC does not provide any "web services" based on the DDC. By web services, we mean presentation of the DDC to other machines (not humans) for uses such as searching, browsing, classifying, mapping, harvesting, and alerting. In order to build web-accessible services based on the DDC, several elements have to be considered. One of these elements is the design of an appropriate Uniform Resource Identifier (URI) structure for Dewey. The design goals of mapping the entity model of the DDC into an identifier space can be summarized as follows: * Common locator for Dewey concepts and associated resources for use in web services and web applications * Use-case-driven, but not directly related to and outlasting a specific use case (persistency) * Retraceable path to a concept rather than an abstract identification, reusing a means of identification that is already present in the DDC and available in existing metadata. We have been working closely with our colleagues in the OCLC Office of Research (especially Andy Houghton as well as Eric Childress, Diane Vizine-Goetz, and Stu Weibel) on a preliminary identifier syntax. The basic identifier format we are currently exploring is: http://dewey.info/{aspect}/{object}/{locale}/{type}/{version}/{resource} where * {aspect} is the aspect associated with an {object}-the current value set of aspect contains "concept", "scheme", and "index"; additional ones are under exploration * {object} is a type of {aspect} * {locale} identifies a Dewey translation * {type} identifies a Dewey edition type and contains, at a minimum, the values "edn" for the full edition or "abr" for the abridged edition * {version} identifies a Dewey edition version * {resource} identifies a resource associated with an {object} in the context of {locale}, {type}, and {version}
Some examples of identifiers for concepts follow: <http://dewey.info/concept/338.4/en/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the English-language version of Edition 22. <http://dewey.info/concept/338.4/de/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the German-language version of Edition 22. <http://dewey.info/concept/333.7-333.9/> This identifier is used to retrieve or identify the 333.7-333.9 concept across all editions and language versions. <http://dewey.info/concept/333.7-333.9/about.skos> This identifier is used to retrieve a SKOS representation of the 333.7-333.9 concept (using the "resource" element). There are several open issues at this preliminary stage of development: Use cases: URIs need to represent the range of statements or questions that could be submitted to a Dewey web service. Therefore, it seems that some general questions have to be answered first: What information does an agent have when coming to a Dewey web service? What kind of questions will such an agent ask? Placement of the {locale} component: It is still an open question if the {locale} component should be placed after the {version} component instead (<http://dewey.info/concept/338.4/edn/22/en>) to emphasize that the most important instantiation of a Dewey class is its edition, not its language version. From a services point of view, however, it could make more sense to keep the current arrangement, because users are more likely to come to the service with a present understanding of the language version they are seeking without knowing the specifics of a certain edition in which they are trying to find topics. Identification of other Dewey entities: The goal is to create a locator that does not answer all, but a lot of questions that could be asked about the DDC. Which entities are missing but should be surfaced for services or user agents? How will those services or agents interact with them? Should some entities be rendered in a different way as presented? For example, (how) should the DDC Summaries be retrievable? Would it be necessary to make the DDC Manual accessible through this identifier structure?"

0.03492763 = product of:
  0.13971052 = sum of:
    0.13971052 = weight(_text_:services in 7190) [ClassicSimilarity], result of:
      0.13971052 = score(doc=7190,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.811266 = fieldWeight in 7190, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.15625 = fieldNorm(doc=7190)
  0.25 = coord(1/4)

0.025407877 = product of:
  0.050815754 = sum of:
    0.03492763 = weight(_text_:services in 5797) [ClassicSimilarity], result of:
      0.03492763 = score(doc=5797,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2028165 = fieldWeight in 5797, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5797)
    0.015888125 = product of:
      0.03177625 = sum of:
        0.03177625 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
          0.03177625 = score(doc=5797,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.19345059 = fieldWeight in 5797, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5797)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Content

"As knowledge brokers, we are living in interesting times for libraries and librarians. We wonder sometimes if our traditional tools like the Dewey Decimal Classification (DDC) system can cope with the onslaught of information. The categories provided don't always seem adequate for the knowledge-discovery habits of today's patrons. They have grown accustomed to new ways for their information needs to be met, from the fire-and-forget style of a hard-to-control classic Google search to the pervasive, always-on style of Google Now, anticipating users' information needs without their having even asked a verbal question. Contrariwise, I believe that we, as librarians, could be making better use of our tools. Many (like the DDC) are a reflection of the same social and epistemological forces that brought about modernity at the turn of the last century. We as librarians are in the unique position of providing services that are as ground-breaking as these tools. As we see the need to provide unique and cutting-edge knowledge discovery to our users, I argue in this article that the DDC can play a key role in fulfilling this purpose."

Source

Knowledge quest. 42(2013) no.2, S.22-29

0.017288294 = product of:
  0.069153175 = sum of:
    0.069153175 = weight(_text_:services in 538) [ClassicSimilarity], result of:
      0.069153175 = score(doc=538,freq=4.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.40155616 = fieldWeight in 538, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=538)
  0.25 = coord(1/4)

Abstract

The presentation will briefly introduce a series of major principles for bringing subject terminology to the network level. A closer look at one KOS in particular, the Dewey Decimal Classification, should help to gain more insight into the perceived difficulties and potential benefits of building taxonomy services out and on top of classic large-scale vocabularies or taxonomies.

Content

Präsentation während der Veranstaltung "Networked Knowledge Organization Systems and Services: The 6th European Networked Knowledge Organization Systems (NKOS) Workshop, Workshop at the 11th ECDL Conference, Budapest, Hungary, September 21st 2007".

0.012224671 = product of:
  0.048898686 = sum of:
    0.048898686 = weight(_text_:services in 5471) [ClassicSimilarity], result of:
      0.048898686 = score(doc=5471,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 5471, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5471)
  0.25 = coord(1/4)

Abstract

The paper outlines the first steps in an initiative to weave the Dewey Decimal Classification (DDC) as a resource into the fabric of the Web. In order for DDC web services to not only being »on« the Web, but rather a part of it, Dewey has to be available under the same rules as other information resources. The process of URI design for identified resources is described and a draft URI template is presented. In addition, basic semantic principles of RESTful web service architecture are discussed, and their appropriateness for making a large-scale knowledge organization system (KOS) like the DDC more congenial for Semantic Web applications is evaluated.

0.006985526 = product of:
  0.027942104 = sum of:
    0.027942104 = weight(_text_:services in 4796) [ClassicSimilarity], result of:
      0.027942104 = score(doc=4796,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.1622532 = fieldWeight in 4796, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.03125 = fieldNorm(doc=4796)
  0.25 = coord(1/4)

Abstract

Key recommendations of the report are: - That library leaders identify sets of data as possible candidates for early exposure as Linked Data and foster a discussion about Open Data and rights; - That library standards bodies increase library participation in Semantic Web standardization, develop library data standards that are compatible with Linked Data, and disseminate best-practice design patterns tailored to library Linked Data; - That data and systems designers design enhanced user services based on Linked Data capabilities, create URIs for the items in library datasets, develop policies for managing RDF vocabularies and their URIs, and express library data by re-using or mapping to existing Linked Data vocabularies; - That librarians and archivists preserve Linked Data element sets and value vocabularies and apply library experience in curation and long-term preservation to Linked Data datasets.

0.004415923 = product of:
  0.017663691 = sum of:
    0.017663691 = product of:
      0.035327382 = sum of:
        0.035327382 = weight(_text_:management in 2783) [ClassicSimilarity], result of:
          0.035327382 = score(doc=2783,freq=2.0), product of:
            0.15810528 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046906993 = queryNorm
            0.22344214 = fieldWeight in 2783, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046875 = fieldNorm(doc=2783)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Multiple groups at Mayo Clinic organize knowledge with the aid of metadata for a variety of purposes. The ontology group focuses on consumer-oriented health information using several controlled vocabularies to support and coordinate care providers, consumers, clinical knowledge and, as part of its research management, information on clinical trials. Poor findability, inconsistent indexing and specialized language undermined the goal of increasing trial participation. The ontology group designed a metadata framework addressing disorders and procedures, investigational drugs and clinical departments, adopted and translated the clinical terminology of SNOMED CT and RxNorm vocabularies to consumer language and coordinated terminology with Mayo's Consumer Health Vocabulary. The result enables retrieval of clinical trial information from multiple access points including conditions, procedures, drug names, organizations involved and trial phase. The jump in inquiries since the search site was revised and vocabularies were modified show evidence of success.