Search (11 results, page 1 of 1)

0.025201196 = product of:
  0.06300299 = sum of:
    0.053677894 = weight(_text_:section in 2362) [ClassicSimilarity], result of:
      0.053677894 = score(doc=2362,freq=2.0), product of:
        0.26305357 = queryWeight, product of:
          5.276892 = idf(docFreq=613, maxDocs=44218)
          0.049850095 = queryNorm
        0.20405689 = fieldWeight in 2362, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.276892 = idf(docFreq=613, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
    0.009325097 = weight(_text_:on in 2362) [ClassicSimilarity], result of:
      0.009325097 = score(doc=2362,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.08505116 = fieldWeight in 2362, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
  0.4 = coord(2/5)

Abstract

According to my findings several relations available in the thesaurus query interface as "roles", are not used, i.e. there are not yet any assertions with them. And those which are used do not contribute to complete concept definitions of concepts which represent thesaurus main entries. In other words: The authors claim to already have a "description logic based nomenclature", where there is not yet one which deserves that title by being much more than a thesaurus with strict subsumption and additional inheritable semantic links. In the last section of the paper the authors say: "The most time consuming process in this conversion was making a careful analysis of the Thesaurus to understand the best way to translate it into OWL." "For other conversions, these same types of distinctions and decisions must be made. The expressive power of a proprietary encoding can vary widely from that in OWL or RDF. Understanding the original semantics and engineering a solution that most closely duplicates it is critical for creating a useful and accu-rate ontology." My question is: What decisions were made and are they exemplary, can they be rec-ommended as "the best way"? I raise strong doubts with respect to that, and I miss more profound discussions of the issues at stake. The following notes are dedicated to a critical description and assessment of the results of that conversion activity. They are written in a tutorial style more or less addressing students, but myself being a learner especially in the field of medical knowledge representation I do not speak "ex cathedra".

0.024165256 = product of:
  0.060413137 = sum of:
    0.026643137 = weight(_text_:on in 539) [ClassicSimilarity], result of:
      0.026643137 = score(doc=539,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.24300331 = fieldWeight in 539, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.078125 = fieldNorm(doc=539)
    0.03377 = product of:
      0.06754 = sum of:
        0.06754 = weight(_text_:22 in 539) [ClassicSimilarity], result of:
          0.06754 = score(doc=539,freq=2.0), product of:
            0.17456654 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049850095 = queryNorm
            0.38690117 = fieldWeight in 539, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=539)
      0.5 = coord(1/2)
  0.4 = coord(2/5)

Abstract

A discussion on current initiatives regarding terminology registries.

Date

26.12.2011 13:22:07

0.018403849 = product of:
  0.092019245 = sum of:
    0.092019245 = weight(_text_:section in 5448) [ClassicSimilarity], result of:
      0.092019245 = score(doc=5448,freq=2.0), product of:
        0.26305357 = queryWeight, product of:
          5.276892 = idf(docFreq=613, maxDocs=44218)
          0.049850095 = queryNorm
        0.34981182 = fieldWeight in 5448, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.276892 = idf(docFreq=613, maxDocs=44218)
          0.046875 = fieldNorm(doc=5448)
  0.2 = coord(1/5)

Source

Kompatibilität, Medien und Ethik in der Wissensorganisation - Compatibility, Media and Ethics in Knowledge Organization: Proceedings der 10. Tagung der Deutschen Sektion der Internationalen Gesellschaft für Wissensorganisation Wien, 3.-5. Juli 2006 - Proceedings of the 10th Conference of the German Section of the International Society of Knowledge Organization Vienna, 3-5 July 2006. Ed.: H.P. Ohly, S. Netscher u. K. Mitgutsch

0.01094872 = product of:
  0.0273718 = sum of:
    0.015985882 = weight(_text_:on in 1169) [ClassicSimilarity], result of:
      0.015985882 = score(doc=1169,freq=8.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.14580199 = fieldWeight in 1169, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1169)
    0.011385918 = weight(_text_:information in 1169) [ClassicSimilarity], result of:
      0.011385918 = score(doc=1169,freq=10.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.1301088 = fieldWeight in 1169, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1169)
  0.4 = coord(2/5)

Abstract

T.1: Today's thesauri are mostly electronic tools, having moved on from the paper-based era when thesaurus standards were first developed. They are built and maintained with the support of software and need to integrate with other software, such as search engines and content management systems. Whereas in the past thesauri were designed for information professionals trained in indexing and searching, today there is a demand for vocabularies that untrained users will find to be intuitive. ISO 25964 makes the transition needed for the world of electronic information management. However, part 1 retains the assumption that human intellect is usually involved in the selection of indexing terms and in the selection of search terms. If both the indexer and the searcher are guided to choose the same term for the same concept, then relevant documents will be retrieved. This is the main principle underlying thesaurus design, even though a thesaurus built for human users may also be applied in situations where computers make the choices. Efficient exchange of data is a vital component of thesaurus management and exploitation. Hence the inclusion in this standard of recommendations for exchange formats and protocols. Adoption of these will facilitate interoperability between thesaurus management systems and the other computer applications, such as indexing and retrieval systems, that will utilize the data. Thesauri are typically used in post-coordinate retrieval systems, but may also be applied to hierarchical directories, pre-coordinate indexes and classification systems. Increasingly, thesaurus applications need to mesh with others, such as automatic categorization schemes, free-text search systems, etc. Part 2 of ISO 25964 describes additional types of structured vocabulary and gives recommendations to enable interoperation of the vocabularies at all stages of the information storage and retrieval process.
T.2: The ability to identify and locate relevant information among vast collections and other resources is a major and pressing challenge today. Several different types of vocabulary are in use for this purpose. Some of the most widely used vocabularies were designed a hundred years ago and have been evolving steadily. A different generation of vocabularies is now emerging, designed to exploit the electronic media more effectively. A good understanding of the previous generation is still essential for effective access to collections indexed with them. An important object of ISO 25964 as a whole is to support data exchange and other forms of interoperability in circumstances in which more than one structured vocabulary is applied within one retrieval system or network. Sometimes one vocabulary has to be mapped to another, and it is important to understand both the potential and the limitations of such mappings. In other systems, a thesaurus is mapped to a classification scheme, or an ontology to a thesaurus. Comprehensive interoperability needs to cover the whole range of vocabulary types, whether young or old. Concepts in different vocabularies are related only in that they have the same or similar meaning. However, the meaning can be found in a number of different aspects within each particular type of structured vocabulary: - within terms or captions selected in different languages; - in the notation assigned indicating a place within a larger hierarchy; - in the definition, scope notes, history notes and other notes that explain the significance of that concept; and - in explicit relationships to other concepts or entities within the same vocabulary. In order to create mappings from one structured vocabulary to another it is first necessary to understand, within the context of each different type of structured vocabulary, the significance and relative importance of each of the different elements in defining the meaning of that particular concept. ISO 25964-1 describes the key characteristics of thesauri along with additional advice on best practice. ISO 25964-2 focuses on other types of vocabulary and does not attempt to cover all aspects of good practice. It concentrates on those aspects which need to be understood if one of the vocabularies is to work effectively alongside one or more of the others. Recognizing that a new standard cannot be applied to some existing vocabularies, this part of ISO 25964 provides informative description alongside the recommendations, the aim of which is to enable users and system developers to interpret and implement the existing vocabularies effectively. The remainder of ISO 25964-2 deals with the principles and practicalities of establishing mappings between vocabularies.

Issue

Pt.1: Thesauri for information retrieval - Pt.2: Interoperability with other vocabularies.

0.005275072 = product of:
  0.02637536 = sum of:
    0.02637536 = weight(_text_:on in 4656) [ClassicSimilarity], result of:
      0.02637536 = score(doc=4656,freq=4.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.24056101 = fieldWeight in 4656, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4656)
  0.2 = coord(1/5)

Abstract

This document describes in brief how to express the content and structure of a thesaurus, and metadata about a thesaurus, in RDF. Using RDF allows data to be linked to and/or merged with other RDF data by semantic web applications. The Semantic Web, which is based on the Resource Description Framework (RDF), provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries.

0.004989059 = product of:
  0.024945294 = sum of:
    0.024945294 = weight(_text_:information in 4729) [ClassicSimilarity], result of:
      0.024945294 = score(doc=4729,freq=12.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.2850541 = fieldWeight in 4729, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=4729)
  0.2 = coord(1/5)

Abstract

The task of an information architect is to create web sites where users can actually find the information they are looking for. As the ocean of information rises and leaves what we seek ever more deeply buried in what we don't seek, this discipline becomes ever more relevant. Information architecture involves many different aspects of web site creation and organization, but its principal tools are information organization techniques developed in other disciplines. Most of these techniques come from library science, such as thesauri, taxonomies, and faceted classification. Topic maps are a relative newcomer to this area and bring with them the promise of better-organized web sites, compared to what is possible with existing techniques. However, it is not generally understood how topic maps relate to the traditional techniques, and what advantages and disadvantages they have, compared to these techniques. The aim of this paper is to help build a better understanding of these issues.

Source

Journal of information science. 30(2005) no.4, S.378-391

0.0033769999 = product of:
  0.016885 = sum of:
    0.016885 = product of:
      0.03377 = sum of:
        0.03377 = weight(_text_:22 in 1670) [ClassicSimilarity], result of:
          0.03377 = score(doc=1670,freq=2.0), product of:
            0.17456654 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049850095 = queryNorm
            0.19345059 = fieldWeight in 1670, 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=1670)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Date

26. 9.2006 21:00:22

0.0031971764 = product of:
  0.015985882 = sum of:
    0.015985882 = weight(_text_:on in 4642) [ClassicSimilarity], result of:
      0.015985882 = score(doc=4642,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.14580199 = fieldWeight in 4642, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.046875 = fieldNorm(doc=4642)
  0.2 = coord(1/5)

Abstract

Thesauri can be useful resources for indexing and retrieval on the Semantic Web, but often they are not published in RDF/OWL. To convert thesauri to RDF for use in Semantic Web applications and to ensure the quality and utility of the conversion a structured method is required. Moreover, if different thesauri are to be interoperable without complicated mappings, a standard schema for thesauri is required. This paper presents a method for conversion of thesauri to the SKOS RDF/OWL schema, which is a proposal for such a standard under development by W3Cs Semantic Web Best Practices Working Group. We apply the method to three thesauri: IPSV, GTAA and MeSH. With these case studies we evaluate our method and the applicability of SKOS for representing thesauri.

0.0023762374 = product of:
  0.011881187 = sum of:
    0.011881187 = weight(_text_:information in 2461) [ClassicSimilarity], result of:
      0.011881187 = score(doc=2461,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.13576832 = fieldWeight in 2461, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2461)
  0.2 = coord(1/5)

Abstract

Moderne Verfahren des Information Retrieval verlangen nach aussagekräftigen und detailliert relationierten Dokumentationssprachen. Der selektive Transfer einzelner Modellierungsstrategien aus dem Bereich semantischer Technologien für die Gestaltung und Relationierung bestehender Dokumentationssprachen wird diskutiert. Am Beispiel des Gegenstandsbereichs "Theater" der Schlagwortnormdatei wird ein hierarchisch strukturiertes Relationeninventar definiert, welches sowohl hinreichend allgemeine als auch zahlreiche spezifische Relationstypen enthält, welche eine detaillierte und damit funktionale Relationierung des Vokabulars ermöglichen. Die Relationierung des Gegenstandsbereichs wird als Ontologie im OWL-Format modelliert. Im Gegensatz zu anderen Ansätzen und Überlegungen zur Schaffung von Relationeninventaren entwickelt der vorgestellte Vorschlag das Relationeninventar aus der Begriffsmenge eines vorgegebenen Gegenstandsbereichs heraus. Das entwickelte Inventar wird als eine hierarchisch strukturierte Taxonomie gestaltet, was einen Zugewinn an Übersichtlichkeit und Funktionalität bringt.

0.002036775 = product of:
  0.0101838745 = sum of:
    0.0101838745 = weight(_text_:information in 1837) [ClassicSimilarity], result of:
      0.0101838745 = score(doc=1837,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.116372846 = fieldWeight in 1837, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=1837)
  0.2 = coord(1/5)

Abstract

Moderne Verfahren des Information Retrieval verlangen nach aussagekräftigen und detailliert relationierten Dokumentationssprachen. Der selektive Transfer einzelner Modellierungsstrategien aus dem Bereich semantischer Technologien für die Gestaltung und Relationierung bestehender Dokumentationssprachen wird diskutiert. Am Beispiel des Gegenstandsbereichs "Theater" der Schlagwortnormdatei wird ein hierarchisch strukturiertes Relationeninventar definiert, welches sowohl hinreichend allgemeine als auch zahlreiche spezifische Relationstypen enthält, welche eine detaillierte und damit funktionale Relationierung des Vokabulars ermöglichen. Die Relationierung des Gegenstandsbereichs wird als Ontologie im OWL-Format modelliert. Im Gegensatz zu anderen Ansätzen und Überlegungen zur Schaffung von Relationeninventaren entwickelt der vorgestellte Vorschlag das Relationeninventar aus der Begriffsmenge eines vorgegebenen Gegenstandsbereichs heraus. Das entwickelte Inventar wird als eine hierarchisch strukturierte Taxonomie gestaltet, was einen Zugewinn an Übersichtlichkeit und Funktionalität bringt.

0.002036775 = product of:
  0.0101838745 = sum of:
    0.0101838745 = weight(_text_:information in 4641) [ClassicSimilarity], result of:
      0.0101838745 = score(doc=4641,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.116372846 = fieldWeight in 4641, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=4641)
  0.2 = coord(1/5)

Abstract

This paper presents an overview of the work in progress at the W3C to produce a standard conversion of WordNet to the RDF/OWL representation language in use in the SemanticWeb community. Such a standard representation is useful to provide application developers a high-quality resource and to promote interoperability. Important requirements in this conversion process are that it should be complete and should stay close to WordNet's conceptual model. The paper explains the steps taken to produce the conversion and details design decisions such as the composition of the class hierarchy and properties, the addition of suitable OWL semantics and the chosen format of the URIs. Additional topics include a strategy to incorporate OWL and RDFS semantics in one schema such that both RDF(S) infrastructure and OWL infrastructure can interpret the information correctly, problems encountered in understanding the Prolog source files and the description of the two versions that are provided (Basic and Full) to accommodate different usages of WordNet.