Search (9 results, page 1 of 1)

0.025858585 = product of:
  0.10343434 = sum of:
    0.10343434 = sum of:
      0.04797038 = weight(_text_:language in 1752) [ClassicSimilarity], result of:
        0.04797038 = score(doc=1752,freq=10.0), product of:
          0.16497234 = queryWeight, product of:
            3.9232929 = idf(docFreq=2376, maxDocs=44218)
            0.042049456 = queryNorm
          0.29077834 = fieldWeight in 1752, product of:
            3.1622777 = tf(freq=10.0), with freq of:
              10.0 = termFreq=10.0
            3.9232929 = idf(docFreq=2376, maxDocs=44218)
            0.0234375 = fieldNorm(doc=1752)
      0.017246505 = weight(_text_:29 in 1752) [ClassicSimilarity], result of:
        0.017246505 = score(doc=1752,freq=2.0), product of:
          0.14791684 = queryWeight, product of:
            3.5176873 = idf(docFreq=3565, maxDocs=44218)
            0.042049456 = queryNorm
          0.11659596 = fieldWeight in 1752, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5176873 = idf(docFreq=3565, maxDocs=44218)
            0.0234375 = fieldNorm(doc=1752)
      0.03821745 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
        0.03821745 = score(doc=1752,freq=10.0), product of:
          0.14725003 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.042049456 = 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.25 = coord(1/4)

Content

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?"

Date

21. 3.2008 19:29:28

0.010749864 = product of:
  0.042999458 = sum of:
    0.042999458 = product of:
      0.064499184 = sum of:
        0.03575501 = weight(_text_:language in 4823) [ClassicSimilarity], result of:
          0.03575501 = score(doc=4823,freq=2.0), product of:
            0.16497234 = queryWeight, product of:
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.042049456 = queryNorm
            0.21673335 = fieldWeight in 4823, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4823)
        0.028744178 = weight(_text_:29 in 4823) [ClassicSimilarity], result of:
          0.028744178 = score(doc=4823,freq=2.0), product of:
            0.14791684 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.042049456 = queryNorm
            0.19432661 = fieldWeight in 4823, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4823)
      0.6666667 = coord(2/3)
  0.25 = coord(1/4)

Abstract

As part of a larger assessment of relationships in the Dewey Decimal Classification (DDC) system, this study investigates the semantic nature of relationships in the DDC notational hierarchy. The semantic relationship between each of a set of randomly selected classes and its parent class in the notational hierarchy is examined against a set of relationship types (specialization, class-instance, several flavours of whole-part).The analysis addresses the prevalence of specific relationship types, their lexical expression, difficulties encountered in assigning relationship types, compatibility of relationships found in the DDC with those found in other knowledge organization systems (KOS), and compatibility of relationships found in the DDC with those in a shared formalism like the Web Ontology Language (OWL). Since notational hierarchy is an organizational mechanism shared across most classification schemes and is often considered to provide an easy solution for ontological transformation of a classification system, the findings of the study are likely to generalize across classification schemes with respect to difficulties that might be encountered in such a transformation process.

Date

21.11.2011 12:29:56

0.009538297 = product of:
  0.038153186 = sum of:
    0.038153186 = product of:
      0.05722978 = sum of:
        0.028744178 = weight(_text_:29 in 5797) [ClassicSimilarity], result of:
          0.028744178 = score(doc=5797,freq=2.0), product of:
            0.14791684 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.042049456 = queryNorm
            0.19432661 = fieldWeight in 5797, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5797)
        0.028485604 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
          0.028485604 = score(doc=5797,freq=2.0), product of:
            0.14725003 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.042049456 = 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.6666667 = coord(2/3)
  0.25 = coord(1/4)

Source

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

0.0067420295 = product of:
  0.026968118 = sum of:
    0.026968118 = product of:
      0.08090435 = sum of:
        0.08090435 = weight(_text_:language in 3130) [ClassicSimilarity], result of:
          0.08090435 = score(doc=3130,freq=4.0), product of:
            0.16497234 = queryWeight, product of:
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.042049456 = queryNorm
            0.4904116 = fieldWeight in 3130, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.0625 = fieldNorm(doc=3130)
      0.33333334 = coord(1/3)
  0.25 = coord(1/4)

Abstract

Based on the research on three general classification schemes, this paper discusses issues encountered when expressing classification schemes in SKOS and explores opportunities of resolving major issues using OWL 2 Web Ontology Language.

0.005056522 = product of:
  0.020226087 = sum of:
    0.020226087 = product of:
      0.06067826 = sum of:
        0.06067826 = weight(_text_:language in 2783) [ClassicSimilarity], result of:
          0.06067826 = score(doc=2783,freq=4.0), product of:
            0.16497234 = queryWeight, product of:
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.042049456 = queryNorm
            0.3678087 = fieldWeight in 2783, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.046875 = fieldNorm(doc=2783)
      0.33333334 = coord(1/3)
  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.

0.004213768 = product of:
  0.016855072 = sum of:
    0.016855072 = product of:
      0.050565217 = sum of:
        0.050565217 = weight(_text_:language in 305) [ClassicSimilarity], result of:
          0.050565217 = score(doc=305,freq=4.0), product of:
            0.16497234 = queryWeight, product of:
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.042049456 = queryNorm
            0.30650726 = fieldWeight in 305, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.0390625 = fieldNorm(doc=305)
      0.33333334 = coord(1/3)
  0.25 = coord(1/4)

Abstract

This paper explores the history, uses cases, and future plans associated with availability of the Dewey Decimal Classification (DDC) system as linked data. Parts of the Dewey Decimal Classification (DDC) system have been available as linked data since 2009. Initial efforts included the DDC Summaries (the top three levels of the DDC) in eleven languages exposed as linked data in dewey.info. In 2010, the content of dewey.info was further extended by the addition of assignable numbers and captions from the Abridged Edition 14 data files in English, Italian, and Vietnamese. During 2012, we will add assignable numbers and captions from the latest full edition database, DDC 23. In addition to the "old friends" of different Dewey language versions, institutions such as the British Library and Deutsche Nationalbibliothek have made use of Dewey linked data in bibliographic records and authority files, and AGROVOC has linked to our data at a general level. We expect to extend our linked data network shortly to "new acquaintances" such as GeoNames, ISO 639-3 language codes, and Mathematics Subject Classification. In particular, we will examine the linking process to GeoNames as an example of cross-domain vocabulary alignment. In addition to linking plans, we report on use cases that facilitate machine-assisted categorization and support discovery in the Semantic Web environment.

0.0041714176 = product of:
  0.01668567 = sum of:
    0.01668567 = product of:
      0.05005701 = sum of:
        0.05005701 = weight(_text_:language in 3530) [ClassicSimilarity], result of:
          0.05005701 = score(doc=3530,freq=2.0), product of:
            0.16497234 = queryWeight, product of:
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.042049456 = queryNorm
            0.30342668 = fieldWeight in 3530, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3530)
      0.33333334 = coord(1/3)
  0.25 = coord(1/4)

Abstract

Classes in the Dewey Decimal Classification (DDC) system function as neighborhoods around focal topics in captions and notes. Topical neighborhoods are generated through specialization and instantiation, complex topic synthesis, index terms and mapped headings, hierarchical force, rules for choosing between numbers, development of the DDC over time, and use of the system in classifying resources. Implications of representation using a formal knowledge representation language are explored.

0.0037980804 = product of:
  0.0151923215 = sum of:
    0.0151923215 = product of:
      0.045576964 = sum of:
        0.045576964 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.045576964 = score(doc=2629,freq=2.0), product of:
            0.14725003 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.042049456 = 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.33333334 = coord(1/3)
  0.25 = coord(1/4)

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.0035755006 = product of:
  0.014302002 = sum of:
    0.014302002 = product of:
      0.042906005 = sum of:
        0.042906005 = weight(_text_:language in 2127) [ClassicSimilarity], result of:
          0.042906005 = score(doc=2127,freq=8.0), product of:
            0.16497234 = queryWeight, product of:
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.042049456 = queryNorm
            0.26008 = fieldWeight in 2127, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.9232929 = idf(docFreq=2376, maxDocs=44218)
              0.0234375 = fieldNorm(doc=2127)
      0.33333334 = coord(1/3)
  0.25 = coord(1/4)

Content

What are those "other" relationships that Dewey possesses and that seem so important to surface? Firstly, there is the relationship of concepts to resources. Dewey has been used for a long time, and over 200,000 numbers are assigned to information resources each year and added to WorldCat by the Library of Congress and the German National Library alone. Secondly, we have relationships between concepts in the scheme itself. Dewey provides a rich set of non-hierarchical relations, indicating other relevant and related subjects across disciplinary boundaries. Thirdly, perhaps most importantly, there is the relationship between the same concepts across different languages. Dewey has been translated extensively, and current versions are available in French, German, Hebrew, Italian, Spanish, and Vietnamese. Briefer representations of the top-three levels (the DDC Summaries) are available in several languages in the DeweyBrowser. This multilingual nature of the scheme allows searchers to access a broader range of resources or to switch the language of--and thus localize--subject metadata seamlessly. MelvilClass, a Dewey front-end developed by the German National Library for the German translation, could be used as a common interface to the DDC in any language, as it is built upon the standard DDC data format. It is not hard to give an example of the basic terminology of a class pulled together in a multilingual way: <class/794.8> a skos:Concept ; skos:notation "794.8"^^ddc:notation ; skos:prefLabel "Computer games"@en ; skos:prefLabel "Computerspiele"@de ; skos:prefLabel "Jeux sur ordinateur"@fr ; skos:prefLabel "Juegos por computador"@es .
Expressed in such manner, the Dewey number provides a language-independent representation of a Dewey concept, accompanied by language-dependent assertions about the concept. This information, identified by a URI, can be easily consumed by semantic web agents and used in various metadata scenarios. Fourthly, as we have seen, it is important to play well with others, i.e., establishing and maintaining relationships to other KOS and making the scheme available in different formats. As noted in the Dewey blog post "Tags and Dewey," since no single scheme is ever going to be the be-all, end-all solution for knowledge discovery, DDC concepts have been extensively mapped to other vocabularies and taxonomies, sometimes bridging them and acting as a backbone, sometimes using them as additional access vocabulary to be able to do more work "behind the scenes." To enable other applications and schemes to make use of those relationships, the full Dewey database is available in XML format; RDF-based formats and a web service are forthcoming. Pulling those relationships together under a common surface will be the next challenge going forward. In the semantic web community the concept of Linked Data (http://en.wikipedia.org/wiki/Linked_Data) currently receives some attention, with its emphasis on exposing and connecting data using technologies like URIs, HTTP and RDF to improve information discovery on the web. With its focus on relationships and discovery, it seems that Dewey will be well prepared to become part of this big linked data set. Now it is about putting the classification back into the world!"