Search (89 results, page 1 of 5)

0.08863184 = product of:
  0.17726368 = sum of:
    0.17726368 = sum of:
      0.14120916 = weight(_text_:translation in 2649) [ClassicSimilarity], result of:
        0.14120916 = score(doc=2649,freq=4.0), product of:
          0.31015858 = queryWeight, product of:
            5.8275905 = idf(docFreq=353, maxDocs=44218)
            0.05322244 = queryNorm
          0.4552805 = fieldWeight in 2649, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            5.8275905 = idf(docFreq=353, maxDocs=44218)
            0.0390625 = fieldNorm(doc=2649)
      0.03605453 = weight(_text_:22 in 2649) [ClassicSimilarity], result of:
        0.03605453 = score(doc=2649,freq=2.0), product of:
          0.18637592 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.05322244 = queryNorm
          0.19345059 = fieldWeight in 2649, 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=2649)
  0.5 = coord(1/2)

Abstract

OCLC's Crosswalk Web Service (Godby, Smith and Childress, 2008) formalizes the notion of crosswalk, as defined in Gill,et al. (n.d.), by hiding technical details and permitting the semantic equivalences to emerge as the centerpiece. One outcome is that metadata experts, who are typically not programmers, can enter the translation logic into a spreadsheet that can be automatically converted into executable code. In this paper, we describe the implementation of the Dublin Core Terms application profile in the management of crosswalks involving MARC. A crosswalk that encodes an application profile extends the typical format with two columns: one that annotates the namespace to which an element belongs, and one that annotates a 'broader-narrower' relation between a pair of elements, such as Dublin Core coverage and Dublin Core Terms spatial. This information is sufficient to produce scripts written in OCLC's Semantic Equivalence Expression Language (or Seel), which are called from the Crosswalk Web Service to generate production-grade translations. With its focus on elements that can be mixed, matched, added, and redefined, the application profile (Heery and Patel, 2000) is a natural fit with the translation model of the Crosswalk Web Service, which attempts to achieve interoperability by mapping one pair of elements at a time.

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.081542686 = product of:
  0.16308537 = sum of:
    0.16308537 = sum of:
      0.11981993 = weight(_text_:translation in 4752) [ClassicSimilarity], result of:
        0.11981993 = score(doc=4752,freq=2.0), product of:
          0.31015858 = queryWeight, product of:
            5.8275905 = idf(docFreq=353, maxDocs=44218)
            0.05322244 = queryNorm
          0.3863183 = fieldWeight in 4752, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.8275905 = idf(docFreq=353, maxDocs=44218)
            0.046875 = fieldNorm(doc=4752)
      0.043265432 = weight(_text_:22 in 4752) [ClassicSimilarity], result of:
        0.043265432 = score(doc=4752,freq=2.0), product of:
          0.18637592 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.05322244 = queryNorm
          0.23214069 = fieldWeight in 4752, 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=4752)
  0.5 = coord(1/2)

Abstract

As educational technology becomes pervasive, demand will grow for library content to be incorporated into courseware. Among the barriers impeding interoperability between libraries and educational tools is the difference in specifications commonly used for the exchange of digital objects and metadata. Among libraries, Metadata Encoding and Transmission Standard (METS) is a new but increasingly popular standard; the IMS content-package (IMS-CP) plays a parallel role in educational technology. This article describes how METS-encoded library content can be converted into digital objects for IMS-compliant systems through an XSLT-based crosswalk. The conceptual models behind METS and IMS-CP are compared, the design and limitations of an XSLT-based translation are described, and the crosswalks are related to other techniques to enhance interoperability.

Source

Library hi tech. 22(2004) no.1, S.69-81

0.049423203 = product of:
  0.098846406 = sum of:
    0.098846406 = product of:
      0.19769281 = sum of:
        0.19769281 = weight(_text_:translation in 3595) [ClassicSimilarity], result of:
          0.19769281 = score(doc=3595,freq=4.0), product of:
            0.31015858 = queryWeight, product of:
              5.8275905 = idf(docFreq=353, maxDocs=44218)
              0.05322244 = queryNorm
            0.6373927 = fieldWeight in 3595, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.8275905 = idf(docFreq=353, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3595)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The project CARMEN ("Content Analysis, Retrieval and Metadata: Effective Networking") aimed - among other goals - at improving the expansion of searches in bibliographic databases into Internet searches. We pursued a set of different approaches to the treatment of semantic heterogeneity (meta-data extraction, query translation using statistic relations and Cross-concordances). This paper describes the concepts and implementation of these approaches and the evaluation of the impact for the retrieval result.

0.03530229 = product of:
  0.07060458 = sum of:
    0.07060458 = product of:
      0.14120916 = sum of:
        0.14120916 = weight(_text_:translation in 3707) [ClassicSimilarity], result of:
          0.14120916 = score(doc=3707,freq=4.0), product of:
            0.31015858 = queryWeight, product of:
              5.8275905 = idf(docFreq=353, maxDocs=44218)
              0.05322244 = queryNorm
            0.4552805 = fieldWeight in 3707, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.8275905 = idf(docFreq=353, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3707)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Purpose The purpose of this paper is threefold: to focus on the process of multilingual concept scheme construction and the challenges involved; to addresses concrete challenges faced in the construction process and especially those related to equivalence between terms and concepts; and to briefly outlines the translation strategies developed during the process of concept scheme construction. Design/methodology/approach The analysis is based on experience acquired during the establishment of the Finnish thesaurus and ontology service Finto as well as the trilingual General Finnish Ontology YSO, both of which are being maintained and further developed at the National Library of Finland. Findings Although uniform resource identifiers can be considered language-independent, they do not render concept schemes and their construction free of language-related challenges. The fundamental issue with all the challenges faced is how to maintain consistency and predictability when the nature of language requires each concept to be treated individually. The key to such challenges is to recognise the function of the vocabulary and the needs of its intended users. Social implications Open science increases the transparency of not only research products, but also metadata tools. Gaining a deeper understanding of the challenges involved in their construction is important for a great variety of users - e.g. indexers, vocabulary builders and information seekers. Today, multilingualism is an essential aspect at both the national and international information society level. Originality/value This paper draws on the practical challenges faced in concept scheme construction in a trilingual environment, with a focus on "concept scheme" as a translation and mapping unit.

0.030593283 = product of:
  0.061186567 = sum of:
    0.061186567 = product of:
      0.122373134 = sum of:
        0.122373134 = weight(_text_:22 in 5743) [ClassicSimilarity], result of:
          0.122373134 = score(doc=5743,freq=4.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.6565931 = fieldWeight in 5743, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=5743)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

30. 3.2002 19:45:22

Source

Revista Española de Documentaçion Cientifica. 22(1999) no.2, S.198-219

0.028843623 = product of:
  0.057687245 = sum of:
    0.057687245 = product of:
      0.11537449 = sum of:
        0.11537449 = weight(_text_:22 in 4899) [ClassicSimilarity], result of:
          0.11537449 = score(doc=4899,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.61904186 = fieldWeight in 4899, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.125 = fieldNorm(doc=4899)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

16. 7.2000 20:58:22

0.028843623 = product of:
  0.057687245 = sum of:
    0.057687245 = product of:
      0.11537449 = sum of:
        0.11537449 = weight(_text_:22 in 2840) [ClassicSimilarity], result of:
          0.11537449 = score(doc=2840,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.61904186 = fieldWeight in 2840, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.125 = fieldNorm(doc=2840)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Library hi tech. 22(2004) no.1

0.02523817 = product of:
  0.05047634 = sum of:
    0.05047634 = product of:
      0.10095268 = sum of:
        0.10095268 = weight(_text_:22 in 4407) [ClassicSimilarity], result of:
          0.10095268 = score(doc=4407,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.5416616 = fieldWeight in 4407, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=4407)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

28. 3.2002 9:22:34

0.02523817 = product of:
  0.05047634 = sum of:
    0.05047634 = product of:
      0.10095268 = sum of:
        0.10095268 = weight(_text_:22 in 7196) [ClassicSimilarity], result of:
          0.10095268 = score(doc=7196,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.5416616 = fieldWeight in 7196, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=7196)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Library hi tech. 22(2004) no.1

0.02523817 = product of:
  0.05047634 = sum of:
    0.05047634 = product of:
      0.10095268 = sum of:
        0.10095268 = weight(_text_:22 in 2841) [ClassicSimilarity], result of:
          0.10095268 = score(doc=2841,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.5416616 = fieldWeight in 2841, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=2841)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Library hi tech. 22(2004) no.2

0.021632716 = product of:
  0.043265432 = sum of:
    0.043265432 = product of:
      0.086530864 = sum of:
        0.086530864 = weight(_text_:22 in 6048) [ClassicSimilarity], result of:
          0.086530864 = score(doc=6048,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.46428138 = fieldWeight in 6048, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=6048)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 9.2007 15:41:14

0.020395521 = product of:
  0.040791042 = sum of:
    0.040791042 = product of:
      0.081582084 = sum of:
        0.081582084 = weight(_text_:22 in 2408) [ClassicSimilarity], result of:
          0.081582084 = score(doc=2408,freq=4.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.4377287 = fieldWeight in 2408, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2408)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

13. 1.2007 18:31:22

Source

Cataloging and classification quarterly. 22(1996) nos.3/4, S.43-58

0.020395521 = product of:
  0.040791042 = sum of:
    0.040791042 = product of:
      0.081582084 = sum of:
        0.081582084 = weight(_text_:22 in 2845) [ClassicSimilarity], result of:
          0.081582084 = score(doc=2845,freq=4.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.4377287 = fieldWeight in 2845, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2845)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

9.12.2005 19:22:38

Source

Library hi tech. 22(2004) no.2, S.175-181

0.018027265 = product of:
  0.03605453 = sum of:
    0.03605453 = product of:
      0.07210906 = sum of:
        0.07210906 = weight(_text_:22 in 1032) [ClassicSimilarity], result of:
          0.07210906 = score(doc=1032,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.38690117 = fieldWeight in 1032, 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=1032)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 5.1998 18:45:36

0.018027265 = product of:
  0.03605453 = sum of:
    0.03605453 = product of:
      0.07210906 = sum of:
        0.07210906 = weight(_text_:22 in 2275) [ClassicSimilarity], result of:
          0.07210906 = score(doc=2275,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.38690117 = fieldWeight in 2275, 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=2275)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

Bericht über den Workshop, der am 22. u. 23.6.98 in der SUB Göttingen stattfand

0.018027265 = product of:
  0.03605453 = sum of:
    0.03605453 = product of:
      0.07210906 = sum of:
        0.07210906 = weight(_text_:22 in 3280) [ClassicSimilarity], result of:
          0.07210906 = score(doc=3280,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.38690117 = fieldWeight in 3280, 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=3280)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Metadata and semantics research: 10th International Conference, MTSR 2016, Göttingen, Germany, November 22-25, 2016, Proceedings. Eds.: E. Garoufallou

0.018027265 = product of:
  0.03605453 = sum of:
    0.03605453 = product of:
      0.07210906 = sum of:
        0.07210906 = weight(_text_:22 in 3281) [ClassicSimilarity], result of:
          0.07210906 = score(doc=3281,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.38690117 = fieldWeight in 3281, 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=3281)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Metadata and semantics research: 10th International Conference, MTSR 2016, Göttingen, Germany, November 22-25, 2016, Proceedings. Eds.: E. Garoufallou

0.018027265 = product of:
  0.03605453 = sum of:
    0.03605453 = product of:
      0.07210906 = sum of:
        0.07210906 = weight(_text_:22 in 3282) [ClassicSimilarity], result of:
          0.07210906 = score(doc=3282,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.38690117 = fieldWeight in 3282, 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=3282)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Metadata and semantics research: 10th International Conference, MTSR 2016, Göttingen, Germany, November 22-25, 2016, Proceedings. Eds.: E. Garoufallou

0.01747374 = product of:
  0.03494748 = sum of:
    0.03494748 = product of:
      0.06989496 = sum of:
        0.06989496 = weight(_text_:translation in 1257) [ClassicSimilarity], result of:
          0.06989496 = score(doc=1257,freq=2.0), product of:
            0.31015858 = queryWeight, product of:
              5.8275905 = idf(docFreq=353, maxDocs=44218)
              0.05322244 = queryNorm
            0.22535235 = fieldWeight in 1257, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.8275905 = idf(docFreq=353, maxDocs=44218)
              0.02734375 = fieldNorm(doc=1257)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Over the past three years, the Dublin Core Metadata Initiative has achieved a broad international consensus on the semantics of a simple element set for describing electronic resources. Since the first workshop in March 1995, which was reported in the very first issue of D-Lib Magazine, Dublin Core has been the topic of perhaps a dozen articles here. Originally intended to be simple and intuitive enough for authors to tag Web pages without special training, Dublin Core is being adapted now for more specialized uses, from government information and legal deposit to museum informatics and electronic commerce. To meet such specialized requirements, Dublin Core can be customized with additional elements or qualifiers. However, these refinements can compromise interoperability across applications. There are tradeoffs between using specific terms that precisely meet local needs versus general terms that are understood more widely. We can better understand this inevitable tension between simplicity and complexity if we recognize that metadata is a form of human language. With Dublin Core, as with a natural language, people are inclined to stretch definitions, make general terms more specific, specific terms more general, misunderstand intended meanings, and coin new terms. One goal of this paper, therefore, will be to examine the experience of some related ways to seek semantic interoperability through simplicity: planned languages, interlingua constructs, and pidgins. The problem of semantic interoperability is compounded when we consider Dublin Core in translation. All of the workshops, documents, mailing lists, user guides, and working group outputs of the Dublin Core Initiative have been in English. But in many countries and for many applications, people need a metadata standard in their own language. In principle, the broad elements of Dublin Core can be defined equally well in Bulgarian or Hindi. Since Dublin Core is a controlled standard, however, any parallel definitions need to be kept in sync as the standard evolves. Another goal of the paper, then, will be to define the conceptual and organizational problem of maintaining a metadata standard in multiple languages. In addition to a name and definition, which are meant for human consumption, each Dublin Core element has a label, or indexing token, meant for harvesting by search engines. For practical reasons, these machine-readable tokens are English-looking strings such as Creator and Subject (just as HTML tags are called HEAD, BODY, or TITLE). These tokens, which are shared by Dublin Cores in every language, ensure that metadata fields created in any particular language are indexed together across repositories. As symbols of underlying universal semantics, these tokens form the basis of semantic interoperability among the multiple Dublin Cores. As long as we limit ourselves to sharing these indexing tokens among exact translations of a simple set of fifteen broad elements, the definitions of which fit easily onto two pages, the problem of Dublin Core in multiple languages is straightforward. But nothing having to do with human language is ever so simple. Just as speakers of various languages must learn the language of Dublin Core in their own tongues, we must find the right words to talk about a metadata language that is expressable in many discipline-specific jargons and natural languages and that inevitably will evolve and change over time.

0.014421811 = product of:
  0.028843623 = sum of:
    0.028843623 = product of:
      0.057687245 = sum of:
        0.057687245 = weight(_text_:22 in 3689) [ClassicSimilarity], result of:
          0.057687245 = score(doc=3689,freq=2.0), product of:
            0.18637592 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05322244 = queryNorm
            0.30952093 = fieldWeight in 3689, 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=3689)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Cataloging and classification quarterly. 22(1996) nos.3/4, S.59-73