Lagoze, C.: Keeping Dublin Core simple : Cross-domain discovery or resource description? (2001)
0.01
0.007163494 = product of:
0.028653976 = sum of:
0.028653976 = weight(_text_:evolution in 1216) [ClassicSimilarity], result of:
0.028653976 = score(doc=1216,freq=2.0), product of:
0.19585751 = queryWeight, product of:
5.29663 = idf(docFreq=601, maxDocs=44218)
0.03697776 = queryNorm
0.1463001 = fieldWeight in 1216, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
5.29663 = idf(docFreq=601, maxDocs=44218)
0.01953125 = fieldNorm(doc=1216)
0.25 = coord(1/4)
- Abstract
- Metadata is not monolithic. Instead, it is helpful to think of metadata as multiple views that can be projected from a single information object. Such views can form the basis of customized information services, such as search engines. Multiple views -- different types of metadata associated with a Web resource -- can facilitate a "drill-down" search paradigm, whereby people start their searches at a high level and later narrow their focus using domain-specific search categories. In Figure 1, for example, Mona Lisa may be viewed from the perspective of non-specialized searchers, with categories that are valid across domains (who painted it and when?); in the context of a museum (when and how was it acquired?); in the geo-spatial context of a walking tour using mobile devices (where is it in the gallery?); and in a legal framework (who owns the rights to its reproduction?). Multiple descriptive views imply a modular approach to metadata. Modularity is the basis of metadata architectures such as the Resource Description Framework (RDF), which permit different communities of expertise to associate and maintain multiple metadata packages for Web resources. As noted elsewhere, static association of multiple metadata packages with resources is but one way of achieving modularity. Another method is to computationally derive order-making views customized to the current needs of a client. This paper examines the evolution and scope of the Dublin Core from this perspective of metadata modularization. Dublin Core began in 1995 with a specific goal and scope -- as an easy-to-create and maintain descriptive format to facilitate cross-domain resource discovery on the Web. Over the years, this goal of "simple metadata for coarse-granularity discovery" came to mix with another goal -- that of community and domain-specific resource description and its attendant complexity. A notion of "qualified Dublin Core" evolved whereby the model for simple resource discovery -- a set of simple metadata elements in a flat, document-centric model -- would form the basis of more complex descriptions by treating the values of its elements as entities with properties ("component elements") in their own right.
