Search (626 results, page 1 of 32)

  • × theme_ss:"Metadaten"
  1. Baker, T.: Dublin Core Application Profiles : current approaches (2010) 0.08 
    0.0752621 = sum of:
  0.03016988 = product of:
    0.18101928 = sum of:
      0.18101928 = weight(_text_:baker in 3737) [ClassicSimilarity], result of:
        0.18101928 = score(doc=3737,freq=2.0), product of:
          0.34308222 = queryWeight, product of:
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.043105017 = queryNorm
          0.5276265 = fieldWeight in 3737, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.046875 = fieldNorm(doc=3737)
    0.16666667 = coord(1/6)
  0.04509222 = sum of:
    0.010051413 = weight(_text_:a in 3737) [ClassicSimilarity], result of:
      0.010051413 = score(doc=3737,freq=14.0), product of:
        0.049702108 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.043105017 = queryNorm
        0.20223314 = fieldWeight in 3737, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=3737)
    0.035040807 = weight(_text_:22 in 3737) [ClassicSimilarity], result of:
      0.035040807 = score(doc=3737,freq=2.0), product of:
        0.15094642 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.043105017 = 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)
    Abstract
    The Dublin Core Metadata Initiative currently defines a Dublin Core Application Profile as a set of specifications about the metadata design of a particular application or for a particular domain or community of users. The current approach to application profiles is summarized in the Singapore Framework for Application Profiles [SINGAPORE-FRAMEWORK] (see Figure 1). While the approach originally developed as a means of specifying customized applications based on the fifteen elements of the Dublin Core Element Set (e.g., Title, Date, Subject), it has evolved into a generic approach to creating metadata that meets specific local requirements while integrating coherently with other RDF-based metadata.
    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
    Type
    a
  2. Baker, T.; Dekkers, M.; Heery, R.; Patel, M.; Salokhe, G.: What Terms Does Your Metadata Use? : Application Profiles as Machine-Understandable Narratives (2002) 0.07 
    0.074277 = sum of:
  0.0711111 = product of:
    0.4266666 = sum of:
      0.4266666 = weight(_text_:baker in 1279) [ClassicSimilarity], result of:
        0.4266666 = score(doc=1279,freq=4.0), product of:
          0.34308222 = queryWeight, product of:
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.043105017 = queryNorm
          1.2436278 = fieldWeight in 1279, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.078125 = fieldNorm(doc=1279)
    0.16666667 = coord(1/6)
  0.0031658972 = product of:
    0.0063317944 = sum of:
      0.0063317944 = weight(_text_:a in 1279) [ClassicSimilarity], result of:
        0.0063317944 = score(doc=1279,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.12739488 = fieldWeight in 1279, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.078125 = fieldNorm(doc=1279)
    0.5 = coord(1/2)
    Footnote
    http://jodi.ecs.soton.ac.uk/Articles/v02/i02/Baker/
    Type
    a
  3. Baker, T.: ¬A grammar of Dublin Core (2000) 0.06 
    0.06313164 = sum of:
  0.028444437 = product of:
    0.17066662 = sum of:
      0.17066662 = weight(_text_:baker in 1236) [ClassicSimilarity], result of:
        0.17066662 = score(doc=1236,freq=4.0), product of:
          0.34308222 = queryWeight, product of:
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.043105017 = queryNorm
          0.4974511 = fieldWeight in 1236, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.03125 = fieldNorm(doc=1236)
    0.16666667 = coord(1/6)
  0.0346872 = sum of:
    0.0113266595 = weight(_text_:a in 1236) [ClassicSimilarity], result of:
      0.0113266595 = score(doc=1236,freq=40.0), product of:
        0.049702108 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.043105017 = queryNorm
        0.22789092 = fieldWeight in 1236, product of:
          6.3245554 = tf(freq=40.0), with freq of:
            40.0 = termFreq=40.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03125 = fieldNorm(doc=1236)
    0.02336054 = weight(_text_:22 in 1236) [ClassicSimilarity], result of:
      0.02336054 = score(doc=1236,freq=2.0), product of:
        0.15094642 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.043105017 = 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)
    Abstract
    Dublin Core is often presented as a modern form of catalog card -- a set of elements (and now qualifiers) that describe resources in a complete package. Sometimes it is proposed as an exchange format for sharing records among multiple collections. The founding principle that "every element is optional and repeatable" reinforces the notion that a Dublin Core description is to be taken as a whole. This paper, in contrast, is based on a much different premise: Dublin Core is a language. More precisely, it is a small language for making a particular class of statements about resources. Like natural languages, it has a vocabulary of word-like terms, the two classes of which -- elements and qualifiers -- function within statements like nouns and adjectives; and it has a syntax for arranging elements and qualifiers into statements according to a simple pattern. Whenever tourists order a meal or ask directions in an unfamiliar language, considerate native speakers will spontaneously limit themselves to basic words and simple sentence patterns along the lines of "I am so-and-so" or "This is such-and-such". Linguists call this pidginization. In such situations, a small phrase book or translated menu can be most helpful. By analogy, today's Web has been called an Internet Commons where users and information providers from a wide range of scientific, commercial, and social domains present their information in a variety of incompatible data models and description languages. In this context, Dublin Core presents itself as a metadata pidgin for digital tourists who must find their way in this linguistically diverse landscape. Its vocabulary is small enough to learn quickly, and its basic pattern is easily grasped. It is well-suited to serve as an auxiliary language for digital libraries. This grammar starts by defining terms. It then follows a 200-year-old tradition of English grammar teaching by focusing on the structure of single statements. It concludes by looking at the growing dictionary of Dublin Core vocabulary terms -- its registry, and at how statements can be used to build the metadata equivalent of paragraphs and compositions -- the application profile.
    Date
    26.12.2011 14:01:22
    Footnote
    Vgl.: http://dlib.ukoln.ac.uk/dlib/october00/baker/10baker.html.
    Type
    a
  4. Wessel, C.: "Publishing and sharing your metadata application profile" : 2. SCHEMAS-Workshop in Bonn (2001) 0.05 
    0.054337695 = sum of:
  0.028444437 = product of:
    0.17066662 = sum of:
      0.17066662 = weight(_text_:baker in 5650) [ClassicSimilarity], result of:
        0.17066662 = score(doc=5650,freq=4.0), product of:
          0.34308222 = queryWeight, product of:
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.043105017 = queryNorm
          0.4974511 = fieldWeight in 5650, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.03125 = fieldNorm(doc=5650)
    0.16666667 = coord(1/6)
  0.025893256 = sum of:
    0.0025327178 = weight(_text_:a in 5650) [ClassicSimilarity], result of:
      0.0025327178 = score(doc=5650,freq=2.0), product of:
        0.049702108 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.043105017 = queryNorm
        0.050957955 = fieldWeight in 5650, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03125 = fieldNorm(doc=5650)
    0.02336054 = weight(_text_:22 in 5650) [ClassicSimilarity], result of:
      0.02336054 = score(doc=5650,freq=2.0), product of:
        0.15094642 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.043105017 = queryNorm
        0.15476047 = fieldWeight in 5650, 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=5650)
    Abstract
    Immer mehr Institutionen erkennen die Bedeutung von Metadaten für die Auffindung elektronischer Dokumente und entwickeln ihr eigenes, domain-spezifisches Application Profile. Sie wählen aus einem bereits existierenden Set von Metadaten ein für ihre Bedürfnisse passendes Subset aus, fügen lokale Ergänzungen hinzu und passen die Definitionen an. Um andere über die eigenen Anwendungen zu informieren, ist es sinnvoll, die jeweiligen Application Profiles zu veröffentlichen. Dadurch wird eine Nachnutzung ermöglicht und neuen Anwendern die Entwicklung eigener Profile erleichtert. Weitere Vorteile wären eine Standardisierung der Metadatenelemente und -formate und Erhöhung der Interoperabilität. In diesem Kontext entstehende Fragen wurden auf dem 2. SCHEMAS-Workshop diskutiert, der vom 23. bis 24. November 2000 in Bonn stattfand. Die einzelnen Vorträge finden sich unter <http://lwww. schemas-forum.org/workshops/ws2/Programme.htm/>. SCHEMAS1 ist die Bezeichnung für ein "Forum for Metadata Schema Implementors". Dieses EU-Projekt wird getragen von Makx Dekkers (PricewaterhouseCoopers), Tom Baker (GMD) und Rachel Heery (UKOLN). In seiner Einführung erläuterte Makx Dekkers die Ziele von SCHEMAS: Da es viele verschiedene Schemes zur Beschreibung von Internet-Ressourcen gibt, wächst die Notwendigkeit der Entwicklung von Standards zur Vermeidung von Doppelarbeit und Konfusion. SCHEMAS stellt Informationen bereit (Metadata Watch Reports, Standards Framework Reports, Guidelines), veranstaltet Workshops und entwickelt ein Registry, in dem Metadatenprofile gesammelt werden sollen. Dadurch sollen Anwender von Metadatenformaten über den Status und neue Entwicklungen im Bereich Metadaten informiert werden. Über die Definition des Begriffs Application Profile war bereits beim 8. Workshop der Dublin Core Metadata Initiative in Ottawa im Oktober2 diskutiert worden. Rachel Heery legte nun folgende Definition vor: In einem "Namespace Schema" werden neue Elemente genannt und definiert, so dass ein standardisiertes Set entsteht. Ein "Application Profile" nutzt bereits vorhandene Elemente aus einem oder mehreren Namespace Schemas nach und optimiert diese für eine bestimmte Anwendung. Da die Zahl der Namespaces und Application Profiles ständig zunimmt, ist es sinnvoll, sie an einer zentralen Stelle zu registrieren. Diese Zentralstelle will das SCHEMAS Registry werden. Tom Baker beschrieb dessen Funktion mit einem Vergleich aus der Linguistik: Metadaten sind eine Sprache, Registries das Wörterbuch. Wie ein Wörterbuch, so hat auch ein Registry zwei Aufgaben: Es beschreibt Sprache anhand von Gebrauchsbeispielen und schreibt diesen Gebrauch vor, indem es Empfehlungen gibt (describe and prescribe). Dadurch entsteht ein Standard für diese Sprache
    Date
    11. 3.2001 17:10:22
    Type
    a
  5. Jimenez, V.O.R.: Nuevas perspectivas para la catalogacion : metadatos ver MARC (1999) 0.05 
    0.053354267 = product of:
  0.106708534 = sum of:
    0.106708534 = sum of:
      0.007598154 = weight(_text_:a in 5743) [ClassicSimilarity], result of:
        0.007598154 = score(doc=5743,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.15287387 = fieldWeight in 5743, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.09375 = fieldNorm(doc=5743)
      0.09911038 = weight(_text_:22 in 5743) [ClassicSimilarity], result of:
        0.09911038 = score(doc=5743,freq=4.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Date
    30. 3.2002 19:45:22
    Source
    Revista Española de Documentaçion Cientifica. 22(1999) no.2, S.198-219
    Type
    a
  6. Andresen, L.: Metadata in Denmark (2000) 0.05 
    0.051786512 = product of:
  0.103573024 = sum of:
    0.103573024 = sum of:
      0.010130871 = weight(_text_:a in 4899) [ClassicSimilarity], result of:
        0.010130871 = score(doc=4899,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.20383182 = fieldWeight in 4899, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.125 = fieldNorm(doc=4899)
      0.09344216 = weight(_text_:22 in 4899) [ClassicSimilarity], result of:
        0.09344216 = score(doc=4899,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Date
    16. 7.2000 20:58:22
    Type
    a
  7. Moen, W.E.: ¬The metadata approach to accessing government information (2001) 0.05 
    0.045313198 = product of:
  0.090626396 = sum of:
    0.090626396 = sum of:
      0.008864513 = weight(_text_:a in 4407) [ClassicSimilarity], result of:
        0.008864513 = score(doc=4407,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.17835285 = fieldWeight in 4407, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.109375 = fieldNorm(doc=4407)
      0.08176188 = weight(_text_:22 in 4407) [ClassicSimilarity], result of:
        0.08176188 = score(doc=4407,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Date
    28. 3.2002 9:22:34
    Type
    a
  8. Baker, T.: ¬A multilingual registry for Dublin Core elements and qualifiers (2000) 0.04 
    0.039630454 = sum of:
  0.035198197 = product of:
    0.21118917 = sum of:
      0.21118917 = weight(_text_:baker in 4447) [ClassicSimilarity], result of:
        0.21118917 = score(doc=4447,freq=2.0), product of:
          0.34308222 = queryWeight, product of:
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.043105017 = queryNorm
          0.6155643 = fieldWeight in 4447, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.0546875 = fieldNorm(doc=4447)
    0.16666667 = coord(1/6)
  0.0044322563 = product of:
    0.008864513 = sum of:
      0.008864513 = weight(_text_:a in 4447) [ClassicSimilarity], result of:
        0.008864513 = score(doc=4447,freq=8.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.17835285 = fieldWeight in 4447, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.0546875 = fieldNorm(doc=4447)
    0.5 = coord(1/2)
    Abstract
    The Dublin Core Metadata Element Set (DCMES) provides 15 high-level, generic concepts for describing a broad range of resources. In actual implementations, these generic concepts must often be made more precise to meet the needs of a specific discipline or application. To support this, the Dublin Core Metadata Initiative has defined standard ways to refine or contextualize an element with 'qualifiers' - for example, to distinguish between Author, Illustrator, and Editor as types of Creator. As other articles in this issue have discussed, the DCMI is currently focusing much of its attention on standardizing qualifiers that have been found to be useful to implementors
    Type
    a
  9. Tennant, R.: ¬A bibliographic metadata infrastructure for the twenty-first century (2004) 0.04 
    0.03924066 = product of:
  0.07848132 = sum of:
    0.07848132 = sum of:
      0.012407733 = weight(_text_:a in 2845) [ClassicSimilarity], result of:
        0.012407733 = score(doc=2845,freq=12.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.24964198 = fieldWeight in 2845, product of:
            3.4641016 = tf(freq=12.0), with freq of:
              12.0 = termFreq=12.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.0625 = fieldNorm(doc=2845)
      0.06607358 = weight(_text_:22 in 2845) [ClassicSimilarity], result of:
        0.06607358 = score(doc=2845,freq=4.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Abstract
    The current library bibliographic infrastructure was constructed in the early days of computers - before the Web, XML, and a variety of other technological advances that now offer new opportunities. General requirements of a modern metadata infrastructure for libraries are identified, including such qualities as versatility, extensibility, granularity, and openness. A new kind of metadata infrastructure is then proposed that exhibits at least some of those qualities. Some key challenges that must be overcome to implement a change of this magnitude are identified.
    Date
    9.12.2005 19:22:38
    Source
    Library hi tech. 22(2004) no.2, S.175-181
    Type
    a
  10. Baker, T.; Dekkers, M.: Identifying metadata elements with URIs : The CORES resolution (2003) 0.04 
    0.03903722 = sum of:
  0.034837183 = product of:
    0.20902309 = sum of:
      0.20902309 = weight(_text_:baker in 1199) [ClassicSimilarity], result of:
        0.20902309 = score(doc=1199,freq=6.0), product of:
          0.34308222 = queryWeight, product of:
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.043105017 = queryNorm
          0.6092507 = fieldWeight in 1199, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            7.9592175 = idf(docFreq=41, maxDocs=44218)
            0.03125 = fieldNorm(doc=1199)
    0.16666667 = coord(1/6)
  0.0042000376 = product of:
    0.008400075 = sum of:
      0.008400075 = weight(_text_:a in 1199) [ClassicSimilarity], result of:
        0.008400075 = score(doc=1199,freq=22.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.16900843 = fieldWeight in 1199, product of:
            4.690416 = tf(freq=22.0), with freq of:
              22.0 = termFreq=22.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.03125 = fieldNorm(doc=1199)
    0.5 = coord(1/2)
    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.
    Footnote
    Vgl.: http://dlib.ukoln.ac.uk/dlib/july03/baker/07baker.html.
    Type
    a
  11. Caplan, P.; Guenther, R.: Metadata for Internet resources : the Dublin Core Metadata Elements Set and its mapping to USMARC (1996) 0.04 
    0.035569508 = product of:
  0.071139015 = sum of:
    0.071139015 = sum of:
      0.0050654355 = weight(_text_:a in 2408) [ClassicSimilarity], result of:
        0.0050654355 = score(doc=2408,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.10191591 = fieldWeight in 2408, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.0625 = fieldNorm(doc=2408)
      0.06607358 = weight(_text_:22 in 2408) [ClassicSimilarity], result of:
        0.06607358 = score(doc=2408,freq=4.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Date
    13. 1.2007 18:31:22
    Source
    Cataloging and classification quarterly. 22(1996) nos.3/4, S.43-58
    Type
    a
  12. Kopácsi, S. et al.: Development of a classification server to support metadata harmonization in a long term preservation system (2016) 0.03 
    0.03468417 = product of:
  0.06936834 = sum of:
    0.06936834 = sum of:
      0.010966991 = weight(_text_:a in 3280) [ClassicSimilarity], result of:
        0.010966991 = score(doc=3280,freq=6.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.22065444 = fieldWeight in 3280, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.078125 = fieldNorm(doc=3280)
      0.058401346 = weight(_text_:22 in 3280) [ClassicSimilarity], result of:
        0.058401346 = score(doc=3280,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Source
    Metadata and semantics research: 10th International Conference, MTSR 2016, Göttingen, Germany, November 22-25, 2016, Proceedings. Eds.: E. Garoufallou
    Type
    a
  13. Hajra, A. et al.: Enriching scientific publications from LOD repositories through word embeddings approach (2016) 0.03 
    0.03367793 = product of:
  0.06735586 = sum of:
    0.06735586 = sum of:
      0.00895451 = weight(_text_:a in 3281) [ClassicSimilarity], result of:
        0.00895451 = score(doc=3281,freq=4.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.18016359 = fieldWeight in 3281, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.078125 = fieldNorm(doc=3281)
      0.058401346 = weight(_text_:22 in 3281) [ClassicSimilarity], result of:
        0.058401346 = score(doc=3281,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Source
    Metadata and semantics research: 10th International Conference, MTSR 2016, Göttingen, Germany, November 22-25, 2016, Proceedings. Eds.: E. Garoufallou
    Type
    a
  14. Hoffmann, L.: Metadaten von Internetressourcen und ihre Integrierung in Bibliothekskataloge (1998) 0.03 
    0.03236657 = product of:
  0.06473314 = sum of:
    0.06473314 = sum of:
      0.0063317944 = weight(_text_:a in 1032) [ClassicSimilarity], result of:
        0.0063317944 = score(doc=1032,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.12739488 = fieldWeight in 1032, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.078125 = fieldNorm(doc=1032)
      0.058401346 = weight(_text_:22 in 1032) [ClassicSimilarity], result of:
        0.058401346 = score(doc=1032,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Date
    22. 5.1998 18:45:36
    Type
    a
  15. Essen, F. von: Metadaten - neue Perspektiven für die Erschließung von Netzpublikationen in Bibliotheken : Erster META-LIB-Workshop in Göttingen (1998) 0.03 
    0.03236657 = product of:
  0.06473314 = sum of:
    0.06473314 = sum of:
      0.0063317944 = weight(_text_:a in 2275) [ClassicSimilarity], result of:
        0.0063317944 = score(doc=2275,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.12739488 = fieldWeight in 2275, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.078125 = fieldNorm(doc=2275)
      0.058401346 = weight(_text_:22 in 2275) [ClassicSimilarity], result of:
        0.058401346 = score(doc=2275,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Content
    Bericht über den Workshop, der am 22. u. 23.6.98 in der SUB Göttingen stattfand
    Type
    a
  16. Mora-Mcginity, M. et al.: MusicWeb: music discovery with open linked semantic metadata (2016) 0.03 
    0.03236657 = product of:
  0.06473314 = sum of:
    0.06473314 = sum of:
      0.0063317944 = weight(_text_:a in 3282) [ClassicSimilarity], result of:
        0.0063317944 = score(doc=3282,freq=2.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.12739488 = fieldWeight in 3282, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.078125 = fieldNorm(doc=3282)
      0.058401346 = weight(_text_:22 in 3282) [ClassicSimilarity], result of:
        0.058401346 = score(doc=3282,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = 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)
    Source
    Metadata and semantics research: 10th International Conference, MTSR 2016, Göttingen, Germany, November 22-25, 2016, Proceedings. Eds.: E. Garoufallou
    Type
    a
  17. Wu, C.-J.: Metadata and future developments in cataloguing (1997) 0.03 
    0.029524416 = sum of:
  0.025092158 = product of:
    0.15055294 = sum of:
      0.15055294 = weight(_text_:author's in 2826) [ClassicSimilarity], result of:
        0.15055294 = score(doc=2826,freq=2.0), product of:
          0.28967232 = queryWeight, product of:
            6.7201533 = idf(docFreq=144, maxDocs=44218)
            0.043105017 = queryNorm
          0.51973534 = fieldWeight in 2826, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            6.7201533 = idf(docFreq=144, maxDocs=44218)
            0.0546875 = fieldNorm(doc=2826)
    0.16666667 = coord(1/6)
  0.0044322563 = product of:
    0.008864513 = sum of:
      0.008864513 = weight(_text_:a in 2826) [ClassicSimilarity], result of:
        0.008864513 = score(doc=2826,freq=8.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.17835285 = fieldWeight in 2826, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.0546875 = fieldNorm(doc=2826)
    0.5 = coord(1/2)
    Abstract
    Metadata is a resource which can assist the information retrieval of digital documents on the Internet. In designing a metadata system, it is necessary to consider the characteristics of digital documents, such as the variety of file formats, frequent format transformation and the difficulty of distinguishing between the different versions. Provides a brief analysis of some existing metadata formats, and introduces several pronciples for the future development of cataloguing on the Internet. Briefly describes the Metadata Experimental System (MES) currently under development, and located at the author's homepage
    Type
    a
  18. Peereboom, M.: DutchESS : Dutch Electronic Subject Service - a Dutch national collaborative effort (2000) 0.03 
    0.029023869 = product of:
  0.058047738 = sum of:
    0.058047738 = sum of:
      0.0113266595 = weight(_text_:a in 4869) [ClassicSimilarity], result of:
        0.0113266595 = score(doc=4869,freq=10.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.22789092 = fieldWeight in 4869, product of:
            3.1622777 = tf(freq=10.0), with freq of:
              10.0 = termFreq=10.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.0625 = fieldNorm(doc=4869)
      0.04672108 = weight(_text_:22 in 4869) [ClassicSimilarity], result of:
        0.04672108 = score(doc=4869,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = queryNorm
          0.30952093 = fieldWeight in 4869, 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=4869)
  0.5 = coord(1/2)
    Abstract
    This article gives an overview of the design and organisation of DutchESS, a Dutch information subject gateway created as a national collaborative effort of the National Library and a number of academic libraries. The combined centralised and distributed model of DutchESS is discussed, as well as its selection policy, its metadata format, classification scheme and retrieval options. Also some options for future collaboration on an international level are explored
    Date
    22. 6.2002 19:39:23
    Type
    a
  19. Proffitt, M.: Pulling it all together : use of METS in RLG cultural materials service (2004) 0.03 
    0.028425975 = product of:
  0.05685195 = sum of:
    0.05685195 = sum of:
      0.010130871 = weight(_text_:a in 767) [ClassicSimilarity], result of:
        0.010130871 = score(doc=767,freq=8.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.20383182 = fieldWeight in 767, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.0625 = fieldNorm(doc=767)
      0.04672108 = weight(_text_:22 in 767) [ClassicSimilarity], result of:
        0.04672108 = score(doc=767,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = queryNorm
          0.30952093 = fieldWeight in 767, 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=767)
  0.5 = coord(1/2)
    Abstract
    RLG has used METS for a particular application, that is as a wrapper for structural metadata. When RLG cultural materials was launched, there was no single way to deal with "complex digital objects". METS provides a standard means of encoding metadata regarding the digital objects represented in RCM, and METS has now been fully integrated into the workflow for this service.
    Source
    Library hi tech. 22(2004) no.1, S.65-68
    Type
    a
  20. Waugh, A.: Specifying metadata standards for metadata tool configuration (1998) 0.03 
    0.028425975 = product of:
  0.05685195 = sum of:
    0.05685195 = sum of:
      0.010130871 = weight(_text_:a in 3596) [ClassicSimilarity], result of:
        0.010130871 = score(doc=3596,freq=8.0), product of:
          0.049702108 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.043105017 = queryNorm
          0.20383182 = fieldWeight in 3596, product of:
            2.828427 = tf(freq=8.0), with freq of:
              8.0 = termFreq=8.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.0625 = fieldNorm(doc=3596)
      0.04672108 = weight(_text_:22 in 3596) [ClassicSimilarity], result of:
        0.04672108 = score(doc=3596,freq=2.0), product of:
          0.15094642 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.043105017 = queryNorm
          0.30952093 = fieldWeight in 3596, 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=3596)
  0.5 = coord(1/2)
    Abstract
    Describes a metadata specification designed to support dynamic configuration of metadata software by capturing features of metadata standards. The specification comprises 3 components: the classification of the metadata standard, the metadata schema, and the metadata expression
    Date
    1. 8.1996 22:08:06
    Footnote
    Contribution to a special issue devoted to the Proceedings of the 7th International World Wide Web Conference, held 14-18 April 1998, Brisbane, Australia
    Type
    a

Authors

Years

Languages

Types

  • a 573
  • el 78
  • m 22
  • s 15
  • n 4
  • x 3
  • b 2
  • More… Less…

Themes

Subjects

Classifications