Search (24 results, page 1 of 2)

0.030597413 = product of:
  0.050995685 = sum of:
    0.013321568 = weight(_text_:on in 3276) [ClassicSimilarity], result of:
      0.013321568 = score(doc=3276,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.121501654 = fieldWeight in 3276, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=3276)
    0.025459683 = weight(_text_:information in 3276) [ClassicSimilarity], result of:
      0.025459683 = score(doc=3276,freq=18.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.2909321 = fieldWeight in 3276, product of:
          4.2426405 = tf(freq=18.0), with freq of:
            18.0 = termFreq=18.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=3276)
    0.012214432 = product of:
      0.024428863 = sum of:
        0.024428863 = weight(_text_:technology in 3276) [ClassicSimilarity], result of:
          0.024428863 = score(doc=3276,freq=2.0), product of:
            0.14847288 = queryWeight, product of:
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.049850095 = queryNorm
            0.16453418 = fieldWeight in 3276, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3276)
      0.5 = coord(1/2)
  0.6 = coord(3/5)

Abstract

The originality of this book, which deals with such a new subject matter, lies in the application of methods and concepts never used before - such as Ontologies and Taxonomies, as well as Thesauri - to the ordering of knowledge based on primary information. Chapters in the book also examine the study of Ontologies, Taxonomies and Thesauri from the perspective of Systematics and General Systems Theory. "Ontologies, Taxonomy and Thesauri in Information Organisation and Retrieval" will be extremely useful to those operating within the network of related fields, which includes Documentation and Information Science.

Content

Inhalt: 1. From classifications to ontologies Knowledge - A new concept of knowledge - Knowledge and information - Knowledge organisation - Knowledge organisation and representation - Cognitive sciences - Talent management - Learning systematisation - Historical evolution - From classification to knowledge organisation - Why ontologies exist - Ontologies - The structure of ontologies 2. Taxonomies and thesauri From ordering to taxonomy - The origins of taxonomy - Hierarchical and horizontal order - Correlation with classifications - Taxonomy in computer science - Computing taxonomy - Definitions - Virtual taxonomy, cybernetic taxonomy - Taxonomy in Information Science - Similarities between taxonomies and thesauri - ifferences between taxonomies and thesauri 3. Thesauri Terminology in classification systems - Terminological languages - Thesauri - Thesauri definitions - Conditions that a thesaurus must fulfil - Historical evolution - Classes of thesauri 4. Thesauri in (cladist) systematics Systematics - Systematics as a noun - Definitions and historic evolution over time - Differences between taxonomy and systematics - Systematics in thesaurus construction theory - Classic, numerical and cladist systematics - Classic systematics in information science - Numerical systematics in information science - Thesauri in cladist systematics - Systematics in information technology - Some examples 5. Thesauri in systems theory Historical evolution - Approach to systems - Systems theory applied to the construction of thesauri - Components - Classes of system - Peculiarities of these systems - Working methods - Systems theory applied to ontologies and taxonomies

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.017673712 = product of:
  0.04418428 = sum of:
    0.03230309 = weight(_text_:on in 604) [ClassicSimilarity], result of:
      0.03230309 = score(doc=604,freq=6.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.29462588 = fieldWeight in 604, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=604)
    0.011881187 = weight(_text_:information in 604) [ClassicSimilarity], result of:
      0.011881187 = score(doc=604,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.13576832 = fieldWeight in 604, 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=604)
  0.4 = coord(2/5)

Abstract

iQvoc is a new open source SKOS-XL vocabulary management tool developed by the Federal Environment Agency, Germany, and innoQ Deutschland GmbH. Its immediate purpose is maintaining and publishing reference vocabularies in the upcoming Linked Data cloud of environmental information, but it may be easily adapted to host any SKOS- XL compliant vocabulary. iQvoc is implemented as a Ruby on Rails application running on top of JRuby - the Java implementation of the Ruby Programming Language. To increase the user experience when editing content, iQvoc uses heavily the JavaScript library jQuery.

Source

Proceedings of the Sixth Workshop on Scripting and Development for the Semantic Web, Crete, Greece, May 31, 2010, CEUR Workshop Proceedings, SFSW - http://ceur-ws.org/Vol-699/Paper2.pdf

0.014208074 = product of:
  0.035520185 = sum of:
    0.011881187 = weight(_text_:information in 4792) [ClassicSimilarity], result of:
      0.011881187 = score(doc=4792,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.13576832 = fieldWeight in 4792, 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=4792)
    0.023639 = product of:
      0.047278 = sum of:
        0.047278 = weight(_text_:22 in 4792) [ClassicSimilarity], result of:
          0.047278 = score(doc=4792,freq=2.0), product of:
            0.17456654 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049850095 = queryNorm
            0.2708308 = fieldWeight in 4792, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4792)
      0.5 = coord(1/2)
  0.4 = coord(2/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. In Form einer Taxonomie wird ein hierarchisch strukturiertes Relationeninventar definiert, welches sowohl hinreichend allgemeine als auch zahlreiche spezifische Relationstypen enthält, die eine detaillierte und damit aussagekräftige Relationierung des Vokabulars ermöglichen. Das bringt einen Zugewinn an Übersichtlichkeit und Funktionalität. Im Gegensatz zu anderen Ansätzen und Überlegungen zur Schaffung von Relationeninventaren entwickelt der vorgestellte Vorschlag das Relationeninventar aus der Begriffsmenge eines bestehenden Gegenstandsbereichs heraus.

Source

Wissensspeicher in digitalen Räumen: Nachhaltigkeit - Verfügbarkeit - semantische Interoperabilität. Proceedings der 11. Tagung der Deutschen Sektion der Internationalen Gesellschaft für Wissensorganisation, Konstanz, 20. bis 22. Februar 2008. Hrsg.: J. Sieglerschmidt u. H.P.Ohly

0.014181092 = product of:
  0.03545273 = sum of:
    0.018650195 = weight(_text_:on in 572) [ClassicSimilarity], result of:
      0.018650195 = score(doc=572,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.17010231 = fieldWeight in 572, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=572)
    0.016802534 = weight(_text_:information in 572) [ClassicSimilarity], result of:
      0.016802534 = score(doc=572,freq=4.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.1920054 = fieldWeight in 572, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=572)
  0.4 = coord(2/5)

Abstract

We consider use of ontological background knowledge in intelligent information systems and analyze directions of their reduction in compliance with specifics of particular user task. Such reduction is aimed at simplification of knowledge processing without loss of significant information. We propose methods of generation of task thesauri based on domain ontology that contain such subset of ontological concepts and relations that can be used in task solving. Combinatorial optimization is used for minimization of task thesaurus. In this approach, semantic similarity estimates are used for determination of concept significance for user task. Some practical examples of optimized thesauri application for semantic retrieval and competence analysis demonstrate efficiency of proposed approach.

0.013157635 = product of:
  0.032894086 = sum of:
    0.026104836 = weight(_text_:on in 4639) [ClassicSimilarity], result of:
      0.026104836 = score(doc=4639,freq=12.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.23809364 = fieldWeight in 4639, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
    0.0067892494 = weight(_text_:information in 4639) [ClassicSimilarity], result of:
      0.0067892494 = score(doc=4639,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.0775819 = fieldWeight in 4639, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
  0.4 = coord(2/5)

Abstract

This thesis focuses on conversion of vocabularies for representation and integration of collections on the Semantic Web. A secondary focus is how to represent metadata schemas (RDF Schemas representing metadata element sets) such that they interoperate with vocabularies. The primary domain in which we operate is that of cultural heritage collections. The background worldview in which a solution is sought is that of the Semantic Web research paradigmwith its associated theories, methods, tools and use cases. In other words, we assume the SemanticWeb is in principle able to provide the context to realize interoperable collections. Interoperability is dependent on the interplay between representations and the applications that use them. We mean applications in the widest sense, such as "search" and "annotation". These applications or tasks are often present in software applications, such as the E-Culture application. It is therefore necessary that applications requirements on the vocabulary representation are met. This leads us to formulate the following problem statement: HOW CAN EXISTING VOCABULARIES BE MADE AVAILABLE TO SEMANTIC WEB APPLICATIONS?
We refine the problem statement into three research questions. The first two focus on the problem of conversion of a vocabulary to a Semantic Web representation from its original format. Conversion of a vocabulary to a representation in a Semantic Web language is necessary to make the vocabulary available to SemanticWeb applications. In the last question we focus on integration of collection metadata schemas in a way that allows for vocabulary representations as produced by our methods. Academisch proefschrift ter verkrijging van de graad Doctor aan de Vrije Universiteit Amsterdam, Dutch Research School for Information and Knowledge Systems.

0.012624079 = product of:
  0.031560197 = sum of:
    0.023073634 = weight(_text_:on in 592) [ClassicSimilarity], result of:
      0.023073634 = score(doc=592,freq=6.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.21044704 = fieldWeight in 592, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=592)
    0.0084865615 = weight(_text_:information in 592) [ClassicSimilarity], result of:
      0.0084865615 = score(doc=592,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.09697737 = fieldWeight in 592, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=592)
  0.4 = coord(2/5)

Abstract

The purpose of this article is to identify the most important factors and features in the evolution of thesauri and ontologies through a dialectic model. This model relies on a dialectic process or idea which could be discovered via a dialectic method. This method has focused on identifying the logical relationship between a beginning proposition, or an idea called a thesis, a negation of that idea called the antithesis, and the result of the conflict between the two ideas, called a synthesis. During the creation of knowl­edge organization systems (KOSs), the identification of logical relations between different ideas has been made possible through the consideration and use of the most influential methods and tools such as dictionaries, Roget's Thesaurus, thesaurus, micro-, macro- and metathesauri, ontology, lower, middle and upper level ontologies. The analysis process has adapted a historical methodology, more specifically a dialectic method and documentary method as the reasoning process. This supports our arguments and synthesizes a method for the analysis of research results. Confirmed by the research results, the principle of unity has shown to be the most important factor in the development and evolution of the structure of knowl­edge organization systems and their types. There are various types of unity when considering the analysis of logical relations. These include the principle of unity of alphabetical order, unity of science, semantic unity, structural unity and conceptual unity. The results have clearly demonstrated a movement from plurality to unity in the assembling of the complex structure of knowl­edge organization systems to increase information and knowl­edge storage and retrieval performance.

0.012117877 = product of:
  0.03029469 = sum of:
    0.013321568 = weight(_text_:on in 5828) [ClassicSimilarity], result of:
      0.013321568 = score(doc=5828,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.121501654 = fieldWeight in 5828, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5828)
    0.016973123 = weight(_text_:information in 5828) [ClassicSimilarity], result of:
      0.016973123 = score(doc=5828,freq=8.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.19395474 = fieldWeight in 5828, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5828)
  0.4 = coord(2/5)

Abstract

Some of the fundamental activities of the software development process are related to the discipline of Requirements Engineering, whose objective is the discovery, analysis, documentation and verification of the requirements that will be part of the system. Requirements are the conditions or capabilities that software must have or perform to meet the users needs. The present study is being developed to propose a model of cooperation between Information Science and Requirements Engineering. Aims to present the analysis results on the possibilities of using the knowledge organization systems: taxonomies, thesauri and ontologies during the activities of Requirements Engineering: design, survey, elaboration, negotiation, specification, validation and requirements management. From the results obtained it was possible to identify in which stage of the Requirements Engineering process, each type of knowledge organization system could be used. We expect that this study put in evidence the need for new researchs and proposals to strengt the exchange between Information Science, as a science that has information as object of study, and the Requirements Engineering which has in the information the raw material to identify the informational needs of software users.

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.009936477 = product of:
  0.024841193 = sum of:
    0.0101838745 = weight(_text_:information in 756) [ClassicSimilarity], result of:
      0.0101838745 = score(doc=756,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.116372846 = fieldWeight in 756, 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=756)
    0.014657319 = product of:
      0.029314637 = sum of:
        0.029314637 = weight(_text_:technology in 756) [ClassicSimilarity], result of:
          0.029314637 = score(doc=756,freq=2.0), product of:
            0.14847288 = queryWeight, product of:
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.049850095 = queryNorm
            0.19744103 = fieldWeight in 756, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.046875 = fieldNorm(doc=756)
      0.5 = coord(1/2)
  0.4 = coord(2/5)

Footnote

Preprint. To be published as Vol 122 in the Conferences in Research and Practice in Information Technology Series by the Australian Computer Society Inc. http://crpit.com/.

0.008280397 = product of:
  0.020700993 = sum of:
    0.0084865615 = weight(_text_:information in 2036) [ClassicSimilarity], result of:
      0.0084865615 = score(doc=2036,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.09697737 = fieldWeight in 2036, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2036)
    0.012214432 = product of:
      0.024428863 = sum of:
        0.024428863 = weight(_text_:technology in 2036) [ClassicSimilarity], result of:
          0.024428863 = score(doc=2036,freq=2.0), product of:
            0.14847288 = queryWeight, product of:
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.049850095 = queryNorm
            0.16453418 = fieldWeight in 2036, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2036)
      0.5 = coord(1/2)
  0.4 = coord(2/5)

Source

Journal of the Association for Information Science and Technology. 66(2015) no.7, S.1348-1366

0.006624318 = product of:
  0.016560795 = sum of:
    0.0067892494 = weight(_text_:information in 549) [ClassicSimilarity], result of:
      0.0067892494 = score(doc=549,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.0775819 = fieldWeight in 549, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.03125 = fieldNorm(doc=549)
    0.009771545 = product of:
      0.01954309 = sum of:
        0.01954309 = weight(_text_:technology in 549) [ClassicSimilarity], result of:
          0.01954309 = score(doc=549,freq=2.0), product of:
            0.14847288 = queryWeight, product of:
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.049850095 = queryNorm
            0.13162735 = fieldWeight in 549, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.978387 = idf(docFreq=6114, maxDocs=44218)
              0.03125 = fieldNorm(doc=549)
      0.5 = coord(1/2)
  0.4 = coord(2/5)

Abstract

LCSH is known as such since 1975. It always has created headings to serve the LC collections instead of a theoretical basis. It started to replace cross reference codes by thesaural codes in 1986, in a mechanical fashion. It was in no way transformed into a thesaurus. Its encyclopedic coverage, its pre-coordinate concepts make it substantially distinct, considering that thesauri usually map a restricted field of knowledge and use uniterms. The questions raised are whether the new symbols comply with thesaurus standards and if they are true to one or to several models. Explanations and definitions from other lists of subject headings and thesauri, literature in the field of classification and subject indexing will provide some answers. For instance, see refers from a subject heading not used to another or others used. Exceptionally it will lead from a specific term to a more general one. Some equate a see reference with the equivalence relationship. Such relationships are pointed by USE in LCSH. See also references are made from the broader subject to narrower parts of it and also between associated subjects. They suggest lateral or vertical connexions as well as reciprocal relationships. They serve a coordination purpose for some, lay down a methodical search itinerary for others. Since their inception in the 1950's thesauri have been devised for indexing and retrieving information in the fields of science and technology. Eventually they attended to a number of social sciences and humanities. Research derived from thesauri was voluminous. Numerous guidelines are designed. They did not discriminate between the "hard" sciences and the social sciences. RT relationships are widely but diversely used in numerous controlled vocabularies. LCSH's aim is to achieve a list almost free of RT and SA references. It thus restricts relationships to BT/NT, USE and UF. This raises the question as to whether all fields of knowledge can "fit" in the Procrustean bed of RT/NT, i.e., genus/species relationships. Standard codes were devised. It was soon realized that BT/NT, well suited to the genus/species couple could not signal a whole-part relationship. In LCSH, BT and NT function as reciprocals, the whole-part relationship is taken into account by ISO. It is amply elaborated upon by authors. The part-whole connexion is sometimes studied apart. The decision to replace cross reference codes was an improvement. Relations can now be distinguished through the distinct needs of numerous fields of knowledge are not attended to. Topic inclusion, and topic-subtopic, could provide the missing link where genus/species or whole/part are inadequate. Distinct codes, BT/NT and whole/part, should be provided. Sorting relationships with mechanical means can only lead to confusion.

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.004614727 = product of:
  0.023073634 = sum of:
    0.023073634 = weight(_text_:on in 5854) [ClassicSimilarity], result of:
      0.023073634 = score(doc=5854,freq=6.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.21044704 = fieldWeight in 5854, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5854)
  0.2 = coord(1/5)

Abstract

The quantitative evaluation of thesauri has been carried out much further since 1976. This type of evaluation is based on counting of special factors in thesaurus structure, some of which are counting preferred terms, non preferred terms, cross reference terms and so on. Therefore, various statistical tests have been proposed and applied for evaluation of thesauri. In this article, we try to explain some ratios in the field of unity quantitative evaluation in a thesaurus term network. Theoretical base of the ratios' indicators and indices construction, and epistemological thought in this type of quantitative evaluation, are discussed in this article. The theoretical base of quantitative evaluation is the epistemological thought of Immanuel Kant's Critique of pure reason. The cognition states of transcendental understanding are divided into three steps, the first is perception, the second combination and the third, relation making. Terms relation domains and conceptual relation domains can be analyzed with ratios. The use of quantitative evaluations in current research in the field of thesaurus construction prepares a basis for a restoration period. In modern thesaurus construction, traditional term relations are analyzed in detail in the form of new conceptual relations. Hence, the new domains of hierarchical and associative relations are constructed in the form of relations between concepts. The newly formed conceptual domains can be a suitable basis for quantitative evaluation analysis in conceptual relations.

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

Abstract

The ISO 2788 guidelines for monolingual thesauri contain a differentiation of "the hierarchical relationship" into "generic", "partitive", and "instance", which, for purposes of document retrieval, was deemed adequate. However, ontologies, designed as language inventories for a wider scope of knowledge representation, are based on all these and some more logical differentiations. Rereading the ISO 2788 standard and inspecting the published Cyc Upper Ontology, it is argued that the adoption of the document-retrieval definition of subsumption generally prevents the conception or use of a thesaurus as a substructure of an ontology of the new kind as constructed for AI applications. When a thesaurus is used for fact description and inference on fact descriptions, the instance-of relationship too should be reconsidered: It may also link concepts and metaconcepts, and then its distinction from subsumption is needed. The treatment of the instance-of relationship in thesauri, the Cyc Upper Ontology, and WordNet is described from this perspective

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.