Search (79 results, page 1 of 4)

0.07251909 = product of:
  0.108778626 = sum of:
    0.07516904 = product of:
      0.22550711 = sum of:
        0.22550711 = weight(_text_:3a in 400) [ClassicSimilarity], result of:
          0.22550711 = score(doc=400,freq=2.0), product of:
            0.40124533 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.047327764 = queryNorm
            0.56201804 = fieldWeight in 400, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.046875 = fieldNorm(doc=400)
      0.33333334 = coord(1/3)
    0.033609584 = product of:
      0.06721917 = sum of:
        0.06721917 = weight(_text_:group in 400) [ClassicSimilarity], result of:
          0.06721917 = score(doc=400,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.30684334 = fieldWeight in 400, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.046875 = fieldNorm(doc=400)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

On a scientific concept hierarchy, a parent concept may have a few attributes, each of which has multiple values being a group of child concepts. We call these attributes facets: classification has a few facets such as application (e.g., face recognition), model (e.g., svm, knn), and metric (e.g., precision). In this work, we aim at building faceted concept hierarchies from scientific literature. Hierarchy construction methods heavily rely on hypernym detection, however, the faceted relations are parent-to-child links but the hypernym relation is a multi-hop, i.e., ancestor-to-descendent link with a specific facet "type-of". We use information extraction techniques to find synonyms, sibling concepts, and ancestor-descendent relations from a data science corpus. And we propose a hierarchy growth algorithm to infer the parent-child links from the three types of relationships. It resolves conflicts by maintaining the acyclic structure of a hierarchy.

Content

Vgl.: https%3A%2F%2Faclanthology.org%2FD19-5317.pdf&usg=AOvVaw0ZZFyq5wWTtNTvNkrvjlGA.

0.067708746 = product of:
  0.20312622 = sum of:
    0.20312622 = sum of:
      0.16465268 = weight(_text_:group in 1652) [ClassicSimilarity], result of:
        0.16465268 = score(doc=1652,freq=12.0), product of:
          0.21906674 = queryWeight, product of:
            4.628715 = idf(docFreq=1173, maxDocs=44218)
            0.047327764 = queryNorm
          0.7516097 = fieldWeight in 1652, product of:
            3.4641016 = tf(freq=12.0), with freq of:
              12.0 = termFreq=12.0
            4.628715 = idf(docFreq=1173, maxDocs=44218)
            0.046875 = fieldNorm(doc=1652)
      0.03847355 = weight(_text_:22 in 1652) [ClassicSimilarity], result of:
        0.03847355 = score(doc=1652,freq=2.0), product of:
          0.16573377 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.047327764 = queryNorm
          0.23214069 = fieldWeight in 1652, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=1652)
  0.33333334 = coord(1/3)

Abstract

This document is the formal definition of the CIDOC Conceptual Reference Model ("CRM"), a formal ontology intended to facilitate the integration, mediation and interchange of heterogeneous cultural heritage information. The CRM is the culmination of more than a decade of standards development work by the International Committee for Documentation (CIDOC) of the International Council of Museums (ICOM). Work on the CRM itself began in 1996 under the auspices of the ICOM-CIDOC Documentation Standards Working Group. Since 2000, development of the CRM has been officially delegated by ICOM-CIDOC to the CIDOC CRM Special Interest Group, which collaborates with the ISO working group ISO/TC46/SC4/WG9 to bring the CRM to the form and status of an International Standard.

Date

6. 8.2010 14:22:28

Editor

ICOM/CIDOC Documentation Standards Group

Issue

Version 3.4.9 - 30.11.2003. Produced by the ICOM/CIDOC Documentation Standards Group, continued by the CIDOC CRM Special Interest Group.

0.059349254 = product of:
  0.17804776 = sum of:
    0.17804776 = sum of:
      0.1267497 = weight(_text_:group in 4685) [ClassicSimilarity], result of:
        0.1267497 = score(doc=4685,freq=4.0), product of:
          0.21906674 = queryWeight, product of:
            4.628715 = idf(docFreq=1173, maxDocs=44218)
            0.047327764 = queryNorm
          0.5785894 = fieldWeight in 4685, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            4.628715 = idf(docFreq=1173, maxDocs=44218)
            0.0625 = fieldNorm(doc=4685)
      0.05129807 = weight(_text_:22 in 4685) [ClassicSimilarity], result of:
        0.05129807 = score(doc=4685,freq=2.0), product of:
          0.16573377 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.047327764 = 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.33333334 = coord(1/3)

Abstract

This document contains and presents test cases for the Web Ontology Language (OWL) approved by the Web Ontology Working Group. Many of the test cases illustrate the correct usage of the Web Ontology Language (OWL), and the formal meaning of its constructs. Other test cases illustrate the resolution of issues considered by the Working Group. Conformance for OWL documents and OWL document checkers is specified.

Date

14. 8.2011 13:33:22

0.035230905 = product of:
  0.105692714 = sum of:
    0.105692714 = sum of:
      0.06721917 = weight(_text_:group in 2024) [ClassicSimilarity], result of:
        0.06721917 = score(doc=2024,freq=2.0), product of:
          0.21906674 = queryWeight, product of:
            4.628715 = idf(docFreq=1173, maxDocs=44218)
            0.047327764 = queryNorm
          0.30684334 = fieldWeight in 2024, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.628715 = idf(docFreq=1173, maxDocs=44218)
            0.046875 = fieldNorm(doc=2024)
      0.03847355 = weight(_text_:22 in 2024) [ClassicSimilarity], result of:
        0.03847355 = score(doc=2024,freq=2.0), product of:
          0.16573377 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.047327764 = queryNorm
          0.23214069 = fieldWeight in 2024, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=2024)
  0.33333334 = coord(1/3)

Abstract

Defined in 1999 and paired with XML, the Resource Description Framework (RDF) has been cast as an RDF Schema, producing data that is well-structured but not validated, permitting certain illogical relationships. When stakeholders convened in 2014 to consider solutions to the data validation challenge, a W3C working group proposed Resource Shapes and Shape Expressions to describe the properties expected for an RDF node. Resistance rose from concerns about data and schema reuse, key principles in RDF. Ideally data types and properties are designed for broad use, but they are increasingly adopted with local restrictions for specific purposes. Resource Shapes are commonly treated as record classes, standing in for data structures but losing flexibility for later reuse. Of various solutions to the resulting tensions, the concept of record classes may be the most reasonable basis for agreement, satisfying stakeholders' objectives while allowing for variations with constraints.

Source

Bulletin of the Association for Information Science and Technology. 41(2015) no.4, S.18-22

0.019760583 = product of:
  0.059281744 = sum of:
    0.059281744 = product of:
      0.11856349 = sum of:
        0.11856349 = weight(_text_:group in 4796) [ClassicSimilarity], result of:
          0.11856349 = score(doc=4796,freq=14.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.54122084 = fieldWeight in 4796, product of:
              3.7416575 = tf(freq=14.0), with freq of:
                14.0 = termFreq=14.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.03125 = fieldNorm(doc=4796)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

The mission of the W3C Library Linked Data Incubator Group, chartered from May 2010 through August 2011, has been "to help increase global interoperability of library data on the Web, by bringing together people involved in Semantic Web activities - focusing on Linked Data - in the library community and beyond, building on existing initiatives, and identifying collaboration tracks for the future." In Linked Data [LINKEDDATA], data is expressed using standards such as Resource Description Framework (RDF) [RDF], which specifies relationships between things, and Uniform Resource Identifiers (URIs, or "Web addresses") [URI]. This final report of the Incubator Group examines how Semantic Web standards and Linked Data principles can be used to make the valuable information assets that library create and curate - resources such as bibliographic data, authorities, and concept schemes - more visible and re-usable outside of their original library context on the wider Web. The Incubator Group began by eliciting reports on relevant activities from parties ranging from small, independent projects to national library initiatives (see the separate report, Library Linked Data Incubator Group: Use Cases) [USECASE]. These use cases provided the starting point for the work summarized in the report: an analysis of the benefits of library Linked Data, a discussion of current issues with regard to traditional library data, existing library Linked Data initiatives, and legal rights over library data; and recommendations for next steps. The report also summarizes the results of a survey of current Linked Data technologies and an inventory of library Linked Data resources available today (see also the more detailed report, Library Linked Data Incubator Group: Datasets, Value Vocabularies, and Metadata Element Sets) [VOCABDATASET].

Issue

W3C Incubator Group Report 25 October 2011.

0.019404506 = product of:
  0.058213517 = sum of:
    0.058213517 = product of:
      0.116427034 = sum of:
        0.116427034 = weight(_text_:group in 3150) [ClassicSimilarity], result of:
          0.116427034 = score(doc=3150,freq=6.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.53146833 = fieldWeight in 3150, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.046875 = fieldNorm(doc=3150)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

The Functional Requirements for Subject Authority Records (FRSAR) Working Group was formed in 2005 as the third IFLA working group of the FRBR family to address subject authority data issues and to investigate the direct and indirect uses of subject authority data by a wide range of users. This paper introduces the Functional Requirements for Subject Authority Data (FRSAD), the model developed by the FRSAR Working Group, and discusses it in the context of other related conceptual models defined in the specifications during recent years, including the British Standard BS8723-5: Structured vocabularies for information retrieval - Guide Part 5: Exchange formats and protocols for interoperability, W3C's SKOS Simple Knowledge Organization System Reference, and OWL Web Ontology Language Reference. These models enable the consideration of the functions of subject authority data and concept schemes at a higher level that is independent of any implementation, system, or specific context, while allowing us to focus on the semantics, structures, and interoperability of subject authority data.

0.016704232 = product of:
  0.050112695 = sum of:
    0.050112695 = product of:
      0.15033808 = sum of:
        0.15033808 = weight(_text_:3a in 701) [ClassicSimilarity], result of:
          0.15033808 = score(doc=701,freq=2.0), product of:
            0.40124533 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.047327764 = queryNorm
            0.3746787 = fieldWeight in 701, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.03125 = fieldNorm(doc=701)
      0.33333334 = coord(1/3)
  0.33333334 = coord(1/3)

Content

Vgl.: http%3A%2F%2Fdigbib.ubka.uni-karlsruhe.de%2Fvolltexte%2Fdocuments%2F1627&ei=tAtYUYrBNoHKtQb3l4GYBw&usg=AFQjCNHeaxKkKU3-u54LWxMNYGXaaDLCGw&sig2=8WykXWQoDKjDSdGtAakH2Q&bvm=bv.44442042,d.Yms.

0.016704232 = product of:
  0.050112695 = sum of:
    0.050112695 = product of:
      0.15033808 = sum of:
        0.15033808 = weight(_text_:3a in 5820) [ClassicSimilarity], result of:
          0.15033808 = score(doc=5820,freq=2.0), product of:
            0.40124533 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.047327764 = queryNorm
            0.3746787 = fieldWeight in 5820, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.03125 = fieldNorm(doc=5820)
      0.33333334 = coord(1/3)
  0.33333334 = coord(1/3)

Content

Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Language and Information Technologies. Vgl.: https%3A%2F%2Fwww.cs.cmu.edu%2F~cx%2Fpapers%2Fknowledge_based_text_representation.pdf&usg=AOvVaw0SaTSvhWLTh__Uz_HtOtl3.

0.015843712 = product of:
  0.04753113 = sum of:
    0.04753113 = product of:
      0.09506226 = sum of:
        0.09506226 = weight(_text_:group in 1623) [ClassicSimilarity], result of:
          0.09506226 = score(doc=1623,freq=4.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.43394202 = fieldWeight in 1623, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.046875 = fieldNorm(doc=1623)
      0.5 = coord(1/2)
  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.014937594 = product of:
  0.04481278 = sum of:
    0.04481278 = product of:
      0.08962556 = sum of:
        0.08962556 = weight(_text_:group in 3056) [ClassicSimilarity], result of:
          0.08962556 = score(doc=3056,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.40912446 = fieldWeight in 3056, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.0625 = fieldNorm(doc=3056)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Imprint

Leiden : University of Leiden, IFIP WG 8.1 Task Group FRISCO

0.014937594 = product of:
  0.04481278 = sum of:
    0.04481278 = product of:
      0.08962556 = sum of:
        0.08962556 = weight(_text_:group in 3063) [ClassicSimilarity], result of:
          0.08962556 = score(doc=3063,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.40912446 = fieldWeight in 3063, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.0625 = fieldNorm(doc=3063)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

The Resource Description Framework (RDF) integrates a variety of applications from library catalogs and world-wide directories to syndication and aggregation of news, software, and content to personal collections of music, photos, and events using XML as an interchange syntax. The RDF specifications provide a lightweight ontology system to support the exchange of knowledge on the Web. The W3C Semantic Web Activity Statement explains W3C's plans for RDF, including the RDF Core WG, Web Ontology and the RDF Interest Group.

0.013203094 = product of:
  0.03960928 = sum of:
    0.03960928 = product of:
      0.07921856 = sum of:
        0.07921856 = weight(_text_:group in 3743) [ClassicSimilarity], result of:
          0.07921856 = score(doc=3743,freq=4.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.36161837 = fieldWeight in 3743, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3743)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

In 2008 the FRBR/CRM Harmonisation Working Group has achieved a major milestone: a complete version of the object-oriented definition of FRBR (FRBRoo) was released for comment. After a brief overview of the history and context of the Working Group, this paper focuses on the primary contributions resulting from this work. - FRBRoo is a self-contained document which expresses the concepts of FRBR using the objectoriented methodology and framework of CIDOC CRM. It is an alternative view on library conceptualisation for a different purpose, not a replacement for FRBR. - This 'translation' process presented an opportunity to verify and confirm FRBR's internal consistency. - FRBRoo offers a common view of library and museum documentation as two kinds of information from memory institutions. Such a common view is necessary to provide interoperable information systems for all users interested in accessing common or related content. - The analysis provided an opportunity for mutual enrichment of FRBR and CIDOC CRM. Examples include: - - Addition of the modelling of time and events to FRBR, which can be seen in its application to the publishing process - - Clarification of the manifestation entity - - Explicit modelling of performances and recordings in FRBR - - Adding the work entity to CRM - - Adding the identifier assignment process to CRM. - Producing a formalisation which is more suited for implementation with object-oriented tools, and which facilitates the testing and adoption of FRBR concepts in implementations with different functional specifications and in different environments.

0.013070395 = product of:
  0.039211184 = sum of:
    0.039211184 = product of:
      0.07842237 = sum of:
        0.07842237 = weight(_text_:group in 3060) [ClassicSimilarity], result of:
          0.07842237 = score(doc=3060,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.35798392 = fieldWeight in 3060, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3060)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Editor

W3C OWL Working Group

0.013070395 = product of:
  0.039211184 = sum of:
    0.039211184 = product of:
      0.07842237 = sum of:
        0.07842237 = weight(_text_:group in 4471) [ClassicSimilarity], result of:
          0.07842237 = score(doc=4471,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.35798392 = fieldWeight in 4471, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4471)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Issue

W3C Working Group Note 28 August 2008.

0.011203195 = product of:
  0.033609584 = sum of:
    0.033609584 = product of:
      0.06721917 = sum of:
        0.06721917 = weight(_text_:group in 4642) [ClassicSimilarity], result of:
          0.06721917 = score(doc=4642,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.30684334 = fieldWeight in 4642, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.046875 = fieldNorm(doc=4642)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

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.011203195 = product of:
  0.033609584 = sum of:
    0.033609584 = product of:
      0.06721917 = sum of:
        0.06721917 = weight(_text_:group in 4683) [ClassicSimilarity], result of:
          0.06721917 = score(doc=4683,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.30684334 = fieldWeight in 4683, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.046875 = fieldNorm(doc=4683)
      0.5 = coord(1/2)
  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.011203195 = product of:
  0.033609584 = sum of:
    0.033609584 = product of:
      0.06721917 = sum of:
        0.06721917 = weight(_text_:group in 4795) [ClassicSimilarity], result of:
          0.06721917 = score(doc=4795,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.30684334 = fieldWeight in 4795, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.046875 = fieldNorm(doc=4795)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Issue

W3C Working Group Note 18 August 2009.

0.011203195 = product of:
  0.033609584 = sum of:
    0.033609584 = product of:
      0.06721917 = sum of:
        0.06721917 = weight(_text_:group in 1526) [ClassicSimilarity], result of:
          0.06721917 = score(doc=1526,freq=2.0), product of:
            0.21906674 = queryWeight, product of:
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.047327764 = queryNorm
            0.30684334 = fieldWeight in 1526, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.628715 = idf(docFreq=1173, maxDocs=44218)
              0.046875 = fieldNorm(doc=1526)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

How information resources can be meaningfully related has been addressed in contexts from bibliographic entries to hyperlinks and, more recently, linked data. The genre structure and relationships among genre structure constituents shed new light on organizing information by purpose or function. This study examines the relationships among a set of functional units previously constructed in a taxonomy, each of which is a chunk of information embedded in a document and is distinct in terms of its communicative function. Through a card-sort study, relationships among functional units were identified with regard to their occurrence and function. The findings suggest that a group of functional units can be identified, collocated, and navigated by particular relationships. Understanding how functional units are related to each other is significant in linking information pieces in documents to support finding, aggregating, and navigating information in a distributed information environment.

0.010687098 = product of:
  0.032061294 = sum of:
    0.032061294 = product of:
      0.06412259 = sum of:
        0.06412259 = weight(_text_:22 in 6089) [ClassicSimilarity], result of:
          0.06412259 = score(doc=6089,freq=2.0), product of:
            0.16573377 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.047327764 = queryNorm
            0.38690117 = fieldWeight in 6089, 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=6089)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Pages

S.11-22

0.010687098 = product of:
  0.032061294 = sum of:
    0.032061294 = product of:
      0.06412259 = sum of:
        0.06412259 = weight(_text_:22 in 5576) [ClassicSimilarity], result of:
          0.06412259 = score(doc=5576,freq=2.0), product of:
            0.16573377 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.047327764 = queryNorm
            0.38690117 = fieldWeight in 5576, 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=5576)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

13.12.2017 14:17:22