Search (433 results, page 22 of 22)

1.6444239E-4 = product of:
  0.0024666358 = sum of:
    0.0024666358 = product of:
      0.0049332716 = sum of:
        0.0049332716 = weight(_text_:information in 472) [ClassicSimilarity], result of:
          0.0049332716 = score(doc=472,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.09697737 = fieldWeight in 472, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0390625 = fieldNorm(doc=472)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Source

Journal of the Association for Information Science and Technology. 73(2022) no.2, S.303-316

1.6444239E-4 = product of:
  0.0024666358 = sum of:
    0.0024666358 = product of:
      0.0049332716 = sum of:
        0.0049332716 = weight(_text_:information in 654) [ClassicSimilarity], result of:
          0.0049332716 = score(doc=654,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.09697737 = fieldWeight in 654, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0390625 = fieldNorm(doc=654)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

A pidgin metadata framework based on the concept of pidgin metadata is proposed to complement the limitations of existing approaches to metadata interoperability and to achieve more reliable metadata interoperability. The framework consists of three layers, with a hierarchical structure, and reflects the semantic and structural characteristics of various metadata. Layer 1 performs both an external function, serving as an anchor for semantic association between metadata elements, and an internal function, providing semantic categories that can encompass detailed elements. Layer 2 is an arbitrary layer composed of substantial elements from existing metadata and performs a function in which different metadata elements describing the same or similar aspects of information resources are associated with the semantic categories of Layer 1. Layer 3 implements the semantic relationships between Layer 1 and Layer 2 through the Resource Description Framework syntax. With this structure, the pidgin metadata framework can establish the criteria for semantic connection between different elements and fully reflect the complexity and heterogeneity among various metadata. Additionally, it is expected to provide a bibliographic environment that can achieve more reliable metadata interoperability than existing approaches by securing the communication between metadata.

1.6444239E-4 = product of:
  0.0024666358 = sum of:
    0.0024666358 = product of:
      0.0049332716 = sum of:
        0.0049332716 = weight(_text_:information in 664) [ClassicSimilarity], result of:
          0.0049332716 = score(doc=664,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.09697737 = fieldWeight in 664, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0390625 = fieldNorm(doc=664)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Source

Journal of the Association for Information Science and Technology. 73(2022) no.10, S.1401-1417

1.6444239E-4 = product of:
  0.0024666358 = sum of:
    0.0024666358 = product of:
      0.0049332716 = sum of:
        0.0049332716 = weight(_text_:information in 1042) [ClassicSimilarity], result of:
          0.0049332716 = score(doc=1042,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.09697737 = fieldWeight in 1042, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1042)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Source

Journal of the Association for Information Science and Technology. 74(2023) no.9, S.1124-1139

1.6278966E-4 = product of:
  0.0024418447 = sum of:
    0.0024418447 = product of:
      0.0048836893 = sum of:
        0.0048836893 = weight(_text_:information in 1210) [ClassicSimilarity], result of:
          0.0048836893 = score(doc=1210,freq=4.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0960027 = fieldWeight in 1210, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.02734375 = fieldNorm(doc=1210)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

* Agencies maintaining directories of data elements in a domain area in accordance with ISO/IEC 11179 (This standard specifies good practice for data element definition as well as the registration process. Example implementations are the National Health Information Knowledgebase hosted by the Australian Institute of Health and Welfare and the Environmental Data Registry hosted by the US Environmental Protection Agency.); * The xml.org directory of the Extended Markup Language (XML) document specifications facilitating re-use of Document Type Definition (DTD), hosted by the Organization for the Advancement of Structured Information Standards (OASIS); * The MetaForm database of Dublin Core usage and mappings maintained at the State and University Library in Goettingen; * The Semantic Web Agreement Group Dictionary, a database of terms for the Semantic Web that can be referred to by humans and software agents; * LEXML, a multi-lingual and multi-jurisdictional RDF Dictionary for the legal world; * The SCHEMAS registry maintained by the European Commission funded SCHEMAS project, which indexes several metadata element sets as well as a large number of activity reports describing metadata related activities and initiatives. Metadata registries essentially provide an index of terms. Given the distributed nature of the Web, there are a number of ways this can be accomplished. For example, the registry could link to terms and definitions in schemas published by implementers and stored locally by the schema maintainer. Alternatively, the registry might harvest various metadata schemas from their maintainers. Registries provide 'added value' to users by indexing schemas relevant to a particular 'domain' or 'community of use' and by simplifying the navigation of terms by enabling multiple schemas to be accessed from one view. An important benefit of this approach is an increase in the reuse of existing terms, rather than users having to reinvent them. Merging schemas to one view leads to harmonization between applications and helps avoid duplication of effort. Additionally, the establishment of registries to index terms actively being used in local implementations facilitates the metadata standards activity by providing implementation experience transferable to the standards-making process.

1.3155391E-4 = product of:
  0.0019733086 = sum of:
    0.0019733086 = product of:
      0.0039466172 = sum of:
        0.0039466172 = weight(_text_:information in 3197) [ClassicSimilarity], result of:
          0.0039466172 = score(doc=3197,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0775819 = fieldWeight in 3197, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=3197)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Footnote

Rez.: JASIST 56(2005) no.13, S.1264 (W. Koehler: "Priscilla Caplan provides us with a sweeping but very welcome survey of the various approaches to metadata in practice or proposed in libraries and archives today. One of the key strengths of the book and paradoxically one of its key weaknesses is that the work is descriptive in nature. While relationships between one system and another may be noted, no general conclusions of a practical or theoretical nature are drawn of the relative merits of one metadata or metametadata scheure as against another. That said, let us remember that this is an American Library Association publication, published as a descriptive resource. Caplan does very well what she sets out to do. The work is divided into two parts: "Principles and Practice" and "Metadata Schemes," and is further subdivided into eighteen chapters. The book begins with short yet more than adequate chapters defining terms, vocabularies, and concepts. It discusses interoperability and the various levels of quality among systems. Perhaps Chapter 5, "Metadata and the Web" is the weakest chapter of the work. There is a brief discussion of how search engines work and some of the more recent initiatives (e.g., the Semantic Web) to develop better retrieval agents. The chapter is weck not in its description but in what it fails to discuss. The second section, "Metadata Schemes," which encompasses chapters six through eighteen, is particularly rich. Thirteen different metadata or metametadata schema are described to provide the interested librarian with a better than adequate introduction to the purpose, application, and operability of each metadata scheme. These are: library cataloging (chiefly MARC), TEI, Dublin Core, Archival Description and EAD, Art and Architecture, GILS, Education, ONIX, Geospatial, Data Documentation Initiative, Administrative Metadata, Structural Metadata, and Rights Metadata. The last three chapters introduce concepts heretofore "foreign" to the realm of the catalog or metadata. Descriptive metadata was . . . intended to help in finding, discovering, and identifying an information resource." (p. 151) Administrative metadata is an aid to ". . . the owners or caretakers of the resource." Structural metadata describe the relationships of data elements. Rights metadata describe (or as Caplan points out, may describe, as definition is still as yet ambiguous) end user rights to use and reproduce material in digital format. Keeping in mind that the work is intended for the general practitioner librarian, the book has a particularly useful glossary and index. Caplan also provides useful suggestions for additional reading at the end of each chapter. 1 intend to adopt Metadata Fundamentals for All Librarians when next I teach a digital cataloging course. Caplan's book provides an excellent introduction to the basic concepts. It is, however, not a "cookbook" nor a guidebook into the complexities of the application of any metadata scheme."

1.3155391E-4 = product of:
  0.0019733086 = sum of:
    0.0019733086 = product of:
      0.0039466172 = sum of:
        0.0039466172 = weight(_text_:information in 5732) [ClassicSimilarity], result of:
          0.0039466172 = score(doc=5732,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0775819 = fieldWeight in 5732, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=5732)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

The speed with change takes place is startling and has left the information community with little time to consider how the development of electronic resources and the metadata schemas created to describe them effect how we view a work and its components. In terms of the attribution of authorship in the context of electronic works, this is a salient point. How does one determine authorship of a complex electronic resource, which is the culmination of the work of a myriad of entities? How does one determine the authorship when the content of the electronic resource may change at any moment without warning? What is the semantic content of the element that denotes authorship or responsibility for an electronic resource and how does the term used determine the element's meaning? The conceptual difficulty in the definition of the Creator element is deciphering what exactly the metadata schema should be describing. We also need to establish what purpose the element is intended to serve. In essence, we are at a crossroads. It is clear that once a work is digitized it exists in a significantly different medium, but how do we provide access to it? It is necessary to critically assess the accuracy of digital surrogates and to note that webmasters have a significant amount of intellectual responsibility invested in the sites they create. The solution to the problem in the Creator element may lie in moving from the concept of "authorship" and "origination" to a concept of intellectual responsibility. Perhaps the problematic nature of the Creator element allows us to move forward in our assessment and treatment of knowledge. One solution may be to standardize the definitions within various element sets. As the semantic web continues to grow and librarians strive to catalog electronic resources, the establishment of standard definitions for elements is becoming more relevant and important.

1.3155391E-4 = product of:
  0.0019733086 = sum of:
    0.0019733086 = product of:
      0.0039466172 = sum of:
        0.0039466172 = weight(_text_:information in 125) [ClassicSimilarity], result of:
          0.0039466172 = score(doc=125,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0775819 = fieldWeight in 125, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=125)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

This paper describes the work of the MARC Content Designation Utilization (MCDU) Project, funded by a National Leadership Grant from the U.S. Federal Institute of Museum and Library Services (IMLS). The MCDU Project is analyzing approximately 56 million MARC 21 Format for Bibliographic Data records from OCLC's WorldCat database to identify actual use of the content designation available in the MARC bibliographic record. We consider bibliographic records as artifacts resulting from the overall cataloging enterprise, of which the encoding of the bibliographic data into MARC is only one part. Concepts from the Functional Requirements for Bibliographic Records (FRBR) can be used to examine and critically assess the availability of bibliographic data in these records, data meant to assist end users in finding, identifying, selecting, and obtaining relevant information resources. Overall, the MCDU Project will provide empirical data reflecting the actual use of MARC content designation structures in this set of records. Specifically, the data can be used to demonstrate how catalogers' coding of bibliographic data may or may not assist end users in these four tasks. The project is using the mapping by Delsey of MARC data elements to FRBR user tasks in this analysis. These data are crucial for making decisions about the future of MARC and may inform current work on bibliographic rules reflected in the development of the next version of cataloging rules (i.e., Resource Description and Access) by the Joint Steering Committee for the Revision of the Anglo-American Cataloguing Rules.

1.3155391E-4 = product of:
  0.0019733086 = sum of:
    0.0019733086 = product of:
      0.0039466172 = sum of:
        0.0039466172 = weight(_text_:information in 1199) [ClassicSimilarity], result of:
          0.0039466172 = score(doc=1199,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0775819 = fieldWeight in 1199, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=1199)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

On 18 November 2002, at a meeting organised by the CORES Project (Information Society Technologies Programme, European Union), several organisations regarded as maintenance authorities for metadata elements achieved consensus on a resolution to assign Uniform Resource Identifiers (URIs) to metadata elements as a useful first step towards the development of mapping infrastructures and interoperability services. The signatories of the CORES Resolution agreed to promote this consensus in their communities and beyond and to implement an action plan in the following six months. Six months having passed, the maintainers of GILS, ONIX, MARC 21, CERIF, DOI, IEEE/LOM, and Dublin Core report on their implementations of the resolution and highlight issues of relevance to establishing good-practice conventions for declaring, identifying, and maintaining metadata elements more generally. In June 2003, the resolution was also endorsed by the maintainers of UNIMARC. The "Resolution on Metadata Element Identifiers", or CORES Resolution, is an agreement among the maintenance organisations for several major metadata standards - GILS, ONIX, MARC 21, UNIMARC, CERIF, DOI®, IEEE/LOM, and Dublin Core - to identify their metadata elements using Uniform Resource Identifiers (URIs). The Uniform Resource Identifier, defined in the IETF RFC 2396 as "a compact string of characters for identifying an abstract or physical resource", has been promoted for use as a universal form of identification by the World Wide Web Consortium. The CORES Resolution, formulated at a meeting organised by the European project CORES in November 2002, included a commitment to publicise the consensus statement to a wider audience of metadata standards initiatives and to implement key points of the agreement within the following six months - specifically, to define URI assignment mechanisms, assign URIs to elements, and formulate policies for the persistence of those URIs. This article marks the passage of six months by reporting on progress made in implementing this common action plan. After presenting the text of the CORES Resolution and its three "clarifications", the article summarises the position of each signatory organisation towards assigning URIs to its metadata elements, noting any practical or strategic problems that may have emerged. These progress reports were based on input from Thomas Baker, José Borbinha, Eliot Christian, Erik Duval, Keith Jeffery, Rebecca Guenther, and Norman Paskin. The article closes with a few general observations about these first steps towards the clarification of shared conventions for the identification of metadata elements and perhaps, one can hope, towards the ultimate goal of improving interoperability among a diversity of metadata communities.

1.3155391E-4 = product of:
  0.0019733086 = sum of:
    0.0019733086 = product of:
      0.0039466172 = sum of:
        0.0039466172 = weight(_text_:information in 2320) [ClassicSimilarity], result of:
          0.0039466172 = score(doc=2320,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0775819 = fieldWeight in 2320, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=2320)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

Purpose - The purpose of this paper is to describe a new approach to a well-known problem for digital libraries, how to search across multiple unrelated libraries with a single query. Design/methodology/approach - The approach involves creating new Dewey Decimal Classification terms and numbers from existing Dublin Core records. In total, 263,550 records were harvested from three digital libraries. Weighted key terms were extracted from the title, description and subject fields of each record. Ranked DDC classes were automatically generated from these key terms by considering DDC hierarchies via a series of filtering and aggregation stages. A mean reciprocal ranking evaluation compared a sample of 49 generated classes against DDC classes created by a trained librarian for the same records. Findings - The best results combined weighted key terms from the title, description and subject fields. Performance declines with increased specificity of DDC level. The results compare favorably with similar studies. Research limitations/implications - The metadata harvest required manual intervention and the evaluation was resource intensive. Future research will look at evaluation methodologies that take account of issues of consistency and ecological validity. Practical implications - The method does not require training data and is easily scalable. The pipeline can be customized for individual use cases, for example, recall or precision enhancing. Social implications - The approach can provide centralized access to information from multiple domains currently provided by individual digital libraries. Originality/value - The approach addresses metadata normalization in the context of web resources. The automatic classification approach accounts for matches within hierarchies, aggregating lower level matches to broader parents and thus approximates the practices of a human cataloger.

1.3155391E-4 = product of:
  0.0019733086 = sum of:
    0.0019733086 = product of:
      0.0039466172 = sum of:
        0.0039466172 = weight(_text_:information in 3336) [ClassicSimilarity], result of:
          0.0039466172 = score(doc=3336,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0775819 = fieldWeight in 3336, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=3336)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Abstract

This book shows you how to harness the power of linked data and web-scale discovery systems to manage and link widely varied content across your library collection. Libraries are increasingly using web-scale discovery systems to help clients find a wide assortment of library materials, including books, journal articles, special collections, archival collections, videos, music and open access collections. Depending on the library material catalogued, the discovery system might need to negotiate different metadata standards, such as AACR, RDA, RAD, FOAF, VRA Core, METS, MODS, RDF and more. In Managing Metadata in Web-Scale Discovery Systems, editor Louise Spiteri and a range of international experts show you how to: * maximize the effectiveness of web-scale discovery systems * provide a smooth and seamless discovery experience to your users * help users conduct searches that yield relevant results * manage the sheer volume of items to which you can provide access, so your users can actually find what they need * maintain shared records that reflect the needs, languages, and identities of culturally and ethnically varied communities * manage metadata both within, across, and outside, library discovery tools by converting your library metadata to linked open data that all systems can access * manage user generated metadata from external services such as Goodreads and LibraryThing * mine user generated metadata to better serve your users in areas such as collection development or readers' advisory. The book will be essential reading for cataloguers, technical services and systems librarians and library and information science students studying modules on metadata, cataloguing, systems design, data management, and digital libraries. The book will also be of interest to those managing metadata in archives, museums and other cultural heritage institutions.

1.3155391E-4 = product of:
  0.0019733086 = sum of:
    0.0019733086 = product of:
      0.0039466172 = sum of:
        0.0039466172 = weight(_text_:information in 5046) [ClassicSimilarity], result of:
          0.0039466172 = score(doc=5046,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.0775819 = fieldWeight in 5046, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.03125 = fieldNorm(doc=5046)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

Source

Information processing and management. 54(2018) no.6, S.985-1001

1.1510967E-4 = product of:
  0.001726645 = sum of:
    0.001726645 = product of:
      0.00345329 = sum of:
        0.00345329 = weight(_text_:information in 1257) [ClassicSimilarity], result of:
          0.00345329 = score(doc=1257,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.06788416 = fieldWeight in 1257, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.02734375 = fieldNorm(doc=1257)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)

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.