-
Baker, T.: ¬A grammar of Dublin Core (2000)
0.02
0.016114645 = product of:
0.03222929 = sum of:
0.03222929 = sum of:
0.0073292386 = weight(_text_:d in 1236) [ClassicSimilarity], result of:
0.0073292386 = score(doc=1236,freq=2.0), product of:
0.08729101 = queryWeight, product of:
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.045945734 = queryNorm
0.08396327 = fieldWeight in 1236, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.03125 = fieldNorm(doc=1236)
0.024900049 = weight(_text_:22 in 1236) [ClassicSimilarity], result of:
0.024900049 = score(doc=1236,freq=2.0), product of:
0.16089413 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.045945734 = queryNorm
0.15476047 = fieldWeight in 1236, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03125 = fieldNorm(doc=1236)
0.5 = coord(1/2)
- Date
- 26.12.2011 14:01:22
- Source
- D-Lib magazine. 6(2000) no.10, xx S
-
Baker, T.: Dublin Core Application Profiles : current approaches (2010)
0.01
0.009337518 = product of:
0.018675037 = sum of:
0.018675037 = product of:
0.037350073 = sum of:
0.037350073 = weight(_text_:22 in 3737) [ClassicSimilarity], result of:
0.037350073 = score(doc=3737,freq=2.0), product of:
0.16089413 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.045945734 = queryNorm
0.23214069 = fieldWeight in 3737, 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=3737)
0.5 = coord(1/2)
0.5 = coord(1/2)
- 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
-
Baker, T.; Rühle, S.: Übersetzung des Dublin Core Metadata Initiative Abstract Model (DCAM) (2009)
0.00
0.002290387 = product of:
0.004580774 = sum of:
0.004580774 = product of:
0.009161548 = sum of:
0.009161548 = weight(_text_:d in 3230) [ClassicSimilarity], result of:
0.009161548 = score(doc=3230,freq=2.0), product of:
0.08729101 = queryWeight, product of:
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.045945734 = queryNorm
0.104954086 = fieldWeight in 3230, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.0390625 = fieldNorm(doc=3230)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Language
- d
-
Baker, T.: Languages for Dublin Core (1998)
0.00
0.0022673677 = product of:
0.0045347353 = sum of:
0.0045347353 = product of:
0.009069471 = sum of:
0.009069471 = weight(_text_:d in 1257) [ClassicSimilarity], result of:
0.009069471 = score(doc=1257,freq=4.0), product of:
0.08729101 = queryWeight, product of:
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.045945734 = queryNorm
0.10389925 = fieldWeight in 1257, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
1.899872 = idf(docFreq=17979, 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.
- Source
- D-Lib magazine. 4(1998) no.12, xx S
-
Baker, T.; Dekkers, M.: Identifying metadata elements with URIs : The CORES resolution (2003)
0.00
0.0018323096 = product of:
0.0036646193 = sum of:
0.0036646193 = product of:
0.0073292386 = sum of:
0.0073292386 = weight(_text_:d in 1199) [ClassicSimilarity], result of:
0.0073292386 = score(doc=1199,freq=2.0), product of:
0.08729101 = queryWeight, product of:
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.045945734 = queryNorm
0.08396327 = fieldWeight in 1199, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.03125 = fieldNorm(doc=1199)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Source
- D-Lib magazine. 9(2003) no.7/8, x S
-
Baker, T.; Fischer, T.: Bericht von der Dublin-Core-Konferenz (DC-2005) in Madrid (2005)
0.00
0.0013742321 = product of:
0.0027484642 = sum of:
0.0027484642 = product of:
0.0054969285 = sum of:
0.0054969285 = weight(_text_:d in 4872) [ClassicSimilarity], result of:
0.0054969285 = score(doc=4872,freq=2.0), product of:
0.08729101 = queryWeight, product of:
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.045945734 = queryNorm
0.06297245 = fieldWeight in 4872, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.899872 = idf(docFreq=17979, maxDocs=44218)
0.0234375 = fieldNorm(doc=4872)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Language
- d
