Search (32 results, page 1 of 2)

0.02532377 = product of:
  0.037985653 = sum of:
    0.013304878 = weight(_text_:to in 4092) [ClassicSimilarity], result of:
      0.013304878 = score(doc=4092,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.16069452 = fieldWeight in 4092, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0625 = fieldNorm(doc=4092)
    0.024680775 = product of:
      0.04936155 = sum of:
        0.04936155 = weight(_text_:22 in 4092) [ClassicSimilarity], result of:
          0.04936155 = score(doc=4092,freq=2.0), product of:
            0.15947726 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045541126 = queryNorm
            0.30952093 = fieldWeight in 4092, 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=4092)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

This 1993 edition is the authoritative guide constructing single-language thesauri, one of the most powerful tools for information retrieval. Written by experts, Z39.19 shows how to formulate descriptors, establish relationships among terms, and present the information in print and on a screen. Also included are thesaurus maintenance procedures and recommended features for thesaurus management systems

Footnote

Rez. in: Knowledge organization 22(1995) no.3/4, S.180-181 (M. Hudon)

0.008869919 = product of:
  0.026609756 = sum of:
    0.026609756 = weight(_text_:to in 485) [ClassicSimilarity], result of:
      0.026609756 = score(doc=485,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.32138905 = fieldWeight in 485, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.125 = fieldNorm(doc=485)
  0.33333334 = coord(1/3)

0.008869919 = product of:
  0.026609756 = sum of:
    0.026609756 = weight(_text_:to in 2740) [ClassicSimilarity], result of:
      0.026609756 = score(doc=2740,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.32138905 = fieldWeight in 2740, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.125 = fieldNorm(doc=2740)
  0.33333334 = coord(1/3)

0.008677262 = product of:
  0.026031785 = sum of:
    0.026031785 = weight(_text_:to in 3285) [ClassicSimilarity], result of:
      0.026031785 = score(doc=3285,freq=10.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.3144084 = fieldWeight in 3285, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3285)
  0.33333334 = coord(1/3)

Abstract

The principles here stated apply only to the choice and form of headings and entry words - i.e. to the principal elements determining the order of entries - in catalogues of printed books in which entries under authors' names and, where these are inappropriate or insufficient, under the titles of works are combined in one alphabetical sequence. They are framed with special reference to catalogues enumerating the contents of large general libraries: but their application to the catalogues of other libraries and to other alphabetical lists of books is also recommended, with such modifications as may be required by the purposes of these catalogues and lists.

0.008480229 = product of:
  0.025440687 = sum of:
    0.025440687 = weight(_text_:to in 1169) [ClassicSimilarity], result of:
      0.025440687 = score(doc=1169,freq=52.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.3072692 = fieldWeight in 1169, product of:
          7.2111025 = tf(freq=52.0), with freq of:
            52.0 = termFreq=52.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1169)
  0.33333334 = coord(1/3)

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.

0.0082269255 = product of:
  0.024680775 = sum of:
    0.024680775 = product of:
      0.04936155 = sum of:
        0.04936155 = weight(_text_:22 in 4685) [ClassicSimilarity], result of:
          0.04936155 = score(doc=4685,freq=2.0), product of:
            0.15947726 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045541126 = queryNorm
            0.30952093 = fieldWeight in 4685, 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=4685)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

14. 8.2011 13:33:22

0.0081475405 = product of:
  0.02444262 = sum of:
    0.02444262 = weight(_text_:to in 4795) [ClassicSimilarity], result of:
      0.02444262 = score(doc=4795,freq=12.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.29521468 = fieldWeight in 4795, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.046875 = fieldNorm(doc=4795)
  0.33333334 = coord(1/3)

Abstract

SKOS (Simple Knowledge Organisation System) provides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, folksonomies, and other types of controlled vocabulary. As an application of the Resource Description Framework (RDF) SKOS allows concepts to be documented, linked and merged with other data, while still being composed, integrated and published on the World Wide Web. This document is an implementors guide for those who would like to represent their concept scheme using SKOS. In basic SKOS, conceptual resources (concepts) can be identified using URIs, labelled with strings in one or more natural languages, documented with various types of notes, semantically related to each other in informal hierarchies and association networks, and aggregated into distinct concept schemes. In advanced SKOS, conceptual resources can be mapped to conceptual resources in other schemes and grouped into labelled or ordered collections. Concept labels can also be related to each other. Finally, the SKOS vocabulary itself can be extended to suit the needs of particular communities of practice.

0.007839975 = product of:
  0.023519924 = sum of:
    0.023519924 = weight(_text_:to in 4801) [ClassicSimilarity], result of:
      0.023519924 = score(doc=4801,freq=4.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28407046 = fieldWeight in 4801, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.078125 = fieldNorm(doc=4801)
  0.33333334 = coord(1/3)

Abstract

Useful to system designers that want to specify a uniform command terminology, Z39.58-1992 describes nineteen non-proprietary command terms for use in online information retrieval systems. Defines the vocabulary, syntax, and operational meaning of the commands

0.007839975 = product of:
  0.023519924 = sum of:
    0.023519924 = weight(_text_:to in 4687) [ClassicSimilarity], result of:
      0.023519924 = score(doc=4687,freq=16.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28407046 = fieldWeight in 4687, product of:
          4.0 = tf(freq=16.0), with freq of:
            16.0 = termFreq=16.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4687)
  0.33333334 = coord(1/3)

Abstract

The World Wide Web as it is currently constituted resembles a poorly mapped geography. Our insight into the documents and capabilities available are based on keyword searches, abetted by clever use of document connectivity and usage patterns. The sheer mass of this data is unmanageable without powerful tool support. In order to map this terrain more precisely, computational agents require machine-readable descriptions of the content and capabilities of Web accessible resources. These descriptions must be in addition to the human-readable versions of that information. The OWL Web Ontology Language is intended to provide a language that can be used to describe the classes and relations between them that are inherent in Web documents and applications. This document demonstrates the use of the OWL language to - formalize a domain by defining classes and properties of those classes, - define individuals and assert properties about them, and - reason about these classes and individuals to the degree permitted by the formal semantics of the OWL language. The sections are organized to present an incremental definition of a set of classes, properties and individuals, beginning with the fundamentals and proceeding to more complex language components.

0.007839975 = product of:
  0.023519924 = sum of:
    0.023519924 = weight(_text_:to in 2379) [ClassicSimilarity], result of:
      0.023519924 = score(doc=2379,freq=16.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28407046 = fieldWeight in 2379, product of:
          4.0 = tf(freq=16.0), with freq of:
            16.0 = termFreq=16.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2379)
  0.33333334 = coord(1/3)

Abstract

This invaluable cataloging resource gives pre-service and practicing school library media specialists the tools they need to be intelligent consumers of commercial cataloging and competent organizers of new materials in their collections. The second edition contains expanded information on Library of Congress Subject Headings and electronic cataloging and cataloging systems, as well as Dewey Decimal Classification (DDC) and Machine Readable Cataloging (MARC). Whether you're a practicing cataloger looking for a short text to update you on the application of RDA to cataloging records or a school librarian who needs a quick resource to answer cataloging questions, this guide is for you. - Thoroughly updates a best-selling, essential guide to cataloging - Addresses the new standards specifically as they apply to school libraries - Helps school librarians understand and implement the new cataloging standards in their collections - Distills the latest information and presents it in a format that is clear and accessible - Fills the need for up-to-the-minute cataloging guidance for the busy librarian who wants information in a hurry

0.0077611795 = product of:
  0.023283537 = sum of:
    0.023283537 = weight(_text_:to in 8518) [ClassicSimilarity], result of:
      0.023283537 = score(doc=8518,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28121543 = fieldWeight in 8518, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.109375 = fieldNorm(doc=8518)
  0.33333334 = coord(1/3)

Abstract

This draft standard provides guidelines and a uniform vocabulary to prepare back-of-the-book and machine generated indexes

0.0077611795 = product of:
  0.023283537 = sum of:
    0.023283537 = weight(_text_:to in 1268) [ClassicSimilarity], result of:
      0.023283537 = score(doc=1268,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28121543 = fieldWeight in 1268, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.109375 = fieldNorm(doc=1268)
  0.33333334 = coord(1/3)

0.0077611795 = product of:
  0.023283537 = sum of:
    0.023283537 = weight(_text_:to in 5015) [ClassicSimilarity], result of:
      0.023283537 = score(doc=5015,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28121543 = fieldWeight in 5015, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.109375 = fieldNorm(doc=5015)
  0.33333334 = coord(1/3)

0.0074376534 = product of:
  0.02231296 = sum of:
    0.02231296 = weight(_text_:to in 4683) [ClassicSimilarity], result of:
      0.02231296 = score(doc=4683,freq=10.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.26949292 = fieldWeight in 4683, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.046875 = fieldNorm(doc=4683)
  0.33333334 = coord(1/3)

Abstract

This description of OWL, the Web Ontology Language being designed by the W3C Web Ontology Working Group, contains a high-level abstract syntax for both OWL DL and OWL Lite, sublanguages of OWL. A model-theoretic semantics is given to provide a formal meaning for OWL ontologies written in this abstract syntax. A model-theoretic semantics in the form of an extension to the RDF semantics is also given to provide a formal meaning for OWL ontologies as RDF graphs (OWL Full). A mapping from the abstract syntax to RDF graphs is given and the two model theories are shown to have the same consequences on OWL ontologies that can be written in the abstract syntax.

0.0074376534 = product of:
  0.02231296 = sum of:
    0.02231296 = weight(_text_:to in 4689) [ClassicSimilarity], result of:
      0.02231296 = score(doc=4689,freq=10.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.26949292 = fieldWeight in 4689, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.046875 = fieldNorm(doc=4689)
  0.33333334 = coord(1/3)

Abstract

SKOS Core provides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies. The SKOS Core Vocabulary is an application of the Resource Description Framework (RDF), that can be used to express a concept scheme as an RDF graph. Using RDF allows data to be linked to and/or merged with other data, enabling data sources to be distributed across the web, but still be meaningfully composed and integrated. This document is a guide using the SKOS Core Vocabulary, for readers who already have a basic understanding of RDF concepts. This edition of the SKOS Core Guide [SKOS Core Guide] is a W3C Public Working Draft. It is the authoritative guide to recommended usage of the SKOS Core Vocabulary at the time of publication.

0.0073336246 = product of:
  0.022000873 = sum of:
    0.022000873 = weight(_text_:to in 6070) [ClassicSimilarity], result of:
      0.022000873 = score(doc=6070,freq=14.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.2657236 = fieldWeight in 6070, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0390625 = fieldNorm(doc=6070)
  0.33333334 = coord(1/3)

Abstract

This standard provides the basic terms and their definitions in the field of information and documentation for the purpose of promoting and facilitating knowledge sharing and information exchange. This International Standard presents terms and definitions of selected concepts relevant to the field of information and documentation. If a definition is from other standards, the priority of selection is TC46 technical standards, then technical standards in relevant field, and then terminology related standards. The scope of this International Standard corresponds to that of ISO/TC46, Standardization of practices relating to libraries, documentation and information centres, publishing, archives, records management, museum documentation, indexing and abstracting services, and information science. ISO 5127 was prepared by Technical Committee ISO/TC 46, Information and Documentation, WG4, Terminology of information and documentation. This second edition cancels and replaces the first edition (ISO 5127:2001), which has been technically revised to overcome problems in the practical application of ISO 5127:2001 and to take account of the new developments in the field of information and documentation.

Content

This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard.

0.006652439 = product of:
  0.019957317 = sum of:
    0.019957317 = weight(_text_:to in 8038) [ClassicSimilarity], result of:
      0.019957317 = score(doc=8038,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.24104178 = fieldWeight in 8038, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.09375 = fieldNorm(doc=8038)
  0.33333334 = coord(1/3)

Abstract

This draft standard defines almost 400 separate three-character alphabetic codes to indicate language in the interchange of information. The list is based on the US MARC list, the revision updates the first one of 1987

0.006652439 = product of:
  0.019957317 = sum of:
    0.019957317 = weight(_text_:to in 1623) [ClassicSimilarity], result of:
      0.019957317 = score(doc=1623,freq=8.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.24104178 = fieldWeight in 1623, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.046875 = fieldNorm(doc=1623)
  0.33333334 = coord(1/3)

Abstract

This specification provides a model and grammar for representing the structure of information resources used to define topics, and the associations (relationships) between topics. Names, resources, and relationships are said to be characteristics of abstract subjects, which are called topics. Topics have their characteristics within scopes: i.e. the limited contexts within which the names and resources are regarded as their name, resource, and relationship characteristics. One or more interrelated documents employing this grammar is called a topic map.TopicMaps.Org is an independent consortium of parties developing the applicability of the topic map paradigm [ISO13250] to the World Wide Web by leveraging the XML family of specifications. This specification describes version 1.0 of XML Topic Maps (XTM) 1.0 [XTM], an abstract model and XML grammar for interchanging Web-based topic maps, written by the members of the TopicMaps.Org Authoring Group. More information on XTM and TopicMaps.Org is available at http://www.topicmaps.org/about.html. All versions of the XTM Specification are permanently licensed to the public, as provided by the Charter of TopicMaps.Org.

0.006652439 = product of:
  0.019957317 = sum of:
    0.019957317 = weight(_text_:to in 4682) [ClassicSimilarity], result of:
      0.019957317 = score(doc=4682,freq=8.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.24104178 = fieldWeight in 4682, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.046875 = fieldNorm(doc=4682)
  0.33333334 = coord(1/3)

Abstract

The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. OWL facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL has three increasingly-expressive sublanguages: OWL Lite, OWL DL, and OWL Full. This document is written for readers who want a first impression of the capabilities of OWL. It provides an introduction to OWL by informally describing the features of each of the sublanguages of OWL. Some knowledge of RDF Schema is useful for understanding this document, but not essential. After this document, interested readers may turn to the OWL Guide for more detailed descriptions and extensive examples on the features of OWL. The normative formal definition of OWL can be found in the OWL Semantics and Abstract Syntax.

0.00643523 = product of:
  0.01930569 = sum of:
    0.01930569 = weight(_text_:to in 5903) [ClassicSimilarity], result of:
      0.01930569 = score(doc=5903,freq=22.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.23317151 = fieldWeight in 5903, product of:
          4.690416 = tf(freq=22.0), with freq of:
            22.0 = termFreq=22.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.02734375 = fieldNorm(doc=5903)
  0.33333334 = coord(1/3)

Abstract

RDF - the Resource Description Framework - is a foundation for processing metadata; it provides interoperability between applications that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing of Web resources. RDF metadata can be used in a variety of application areas; for example: in resource discovery to provide better search engine capabilities; in cataloging for describing the content and content relationships available at a particular Web site, page, or digital library; by intelligent software agents to facilitate knowledge sharing and exchange; in content rating; in describing collections of pages that represent a single logical "document"; for describing intellectual property rights of Web pages, and in many others. RDF with digital signatures will be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications. Metadata is "data about data" or specifically in the context of RDF "data describing web resources." The distinction between "data" and "metadata" is not an absolute one; it is a distinction created primarily by a particular application. Many times the same resource will be interpreted in both ways simultaneously. RDF encourages this view by using XML as the encoding syntax for the metadata. The resources being described by RDF are, in general, anything that can be named via a URI. The broad goal of RDF is to define a mechanism for describing resources that makes no assumptions about a particular application domain, nor defines the semantics of any application domain. The definition of the mechanism should be domain neutral, yet the mechanism should be suitable for describing information about any domain. This document introduces a model for representing RDF metadata and one syntax for expressing and transporting this metadata in a manner that maximizes the interoperability of independently developed web servers and clients. The syntax described in this document is best considered as a "serialization syntax" for the underlying RDF representation model. The serialization syntax is XML, XML being the W3C's work-in-progress to define a richer Web syntax for a variety of applications. RDF and XML are complementary; there will be alternate ways to represent the same RDF data model, some more suitable for direct human authoring. Future work may lead to including such alternatives in this document.

Content

RDF Data Model At the core of RDF is a model for representing named properties and their values. These properties serve both to represent attributes of resources (and in this sense correspond to usual attribute-value-pairs) and to represent relationships between resources. The RDF data model is a syntax-independent way of representing RDF statements. RDF statements that are syntactically very different could mean the same thing. This concept of equivalence in meaning is very important when performing queries, aggregation and a number of other tasks at which RDF is aimed. The equivalence is defined in a clean machine understandable way. Two pieces of RDF are equivalent if and only if their corresponding data model representations are the same. Table of contents 1. Introduction 2. RDF Data Model 3. RDF Grammar 4. Signed RDF 5. Examples 6. Appendix A: Brief Explanation of XML Namespaces