Search (159 results, page 1 of 8)

0.027828163 = product of:
  0.11131265 = sum of:
    0.11131265 = sum of:
      0.037015475 = weight(_text_:web in 1694) [ClassicSimilarity], result of:
        0.037015475 = score(doc=1694,freq=4.0), product of:
          0.12098375 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.03707166 = queryNorm
          0.3059541 = fieldWeight in 1694, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.046875 = fieldNorm(doc=1694)
      0.074297175 = weight(_text_:seiten in 1694) [ClassicSimilarity], result of:
        0.074297175 = score(doc=1694,freq=2.0), product of:
          0.20383513 = queryWeight, product of:
            5.4984083 = idf(docFreq=491, maxDocs=44218)
            0.03707166 = queryNorm
          0.3644964 = fieldWeight in 1694, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.4984083 = idf(docFreq=491, maxDocs=44218)
            0.046875 = fieldNorm(doc=1694)
  0.25 = coord(1/4)

Abstract

Barry Budd erklärt, wie XML in Verbindung mit Java optimal funktionieren und Daten zwischen Anwendungen transferieren kann. Das Buch ist nicht nur für Anfänger interessant. Insbesondere Javabewanderte Web-Entwickler finden hier einen geradlinigen und lockeren Einstieg in die Zusammenarbeit von Java und XML. Die ersten 30 Seiten widmen sich der Programmiertheorie, der Installation von Java und den zusätzlich nötigen XMLrelevanten Klassen. Im zweiten Teil erfährt der Leser alles über die lineare Untersuchung von XML-Dateien und die Programmierung mit SAX. Es folgt der holistische Ansatz mit DOM und dessen Java-optimierter, eleganterer Alternative JDOM. XSL, die Anzeige von XML-Daten im Web und Java API for XML-Binding (JAXB) mit der man aus XML-Dokumenten maßgeschneiderte Java-Klassen dateien erstellen kann. Teil drei zeigt Spezialwerkzeuge für Webservices Soap, UDDI, WSDL, Java API for XML Messaging (JAXM) und die Arbeit mit XML-Registraren. Zu den Techniken erfährt der Leser sinnvolle Einsatzszenarien. Der Autor verdeutlicht die Theorie mit Code-Beispielen, die in Teilen für eigene Projekte verwendbar sind.

0.019394243 = product of:
  0.038788486 = sum of:
    0.026173891 = product of:
      0.052347783 = sum of:
        0.052347783 = weight(_text_:web in 6020) [ClassicSimilarity], result of:
          0.052347783 = score(doc=6020,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.43268442 = fieldWeight in 6020, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.09375 = fieldNorm(doc=6020)
      0.5 = coord(1/2)
    0.012614595 = product of:
      0.06307297 = sum of:
        0.06307297 = weight(_text_:28 in 6020) [ClassicSimilarity], result of:
          0.06307297 = score(doc=6020,freq=2.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.4749455 = fieldWeight in 6020, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.09375 = fieldNorm(doc=6020)
      0.2 = coord(1/5)
  0.5 = coord(2/4)

Source

International cataloguing and bibliographic control. 28(1999) no.2, S.47-48

0.015999436 = product of:
  0.031998873 = sum of:
    0.021592362 = product of:
      0.043184724 = sum of:
        0.043184724 = weight(_text_:web in 5423) [ClassicSimilarity], result of:
          0.043184724 = score(doc=5423,freq=4.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.35694647 = fieldWeight in 5423, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5423)
      0.5 = coord(1/2)
    0.010406509 = product of:
      0.052032545 = sum of:
        0.052032545 = weight(_text_:28 in 5423) [ClassicSimilarity], result of:
          0.052032545 = score(doc=5423,freq=4.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.39181003 = fieldWeight in 5423, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5423)
      0.2 = coord(1/5)
  0.5 = coord(2/4)

Abstract

This article explores recent discussions about appropriate mark-up conventions for library information intended for use on the World Wide Web. In particular, the question of whether the MARC 21 format will continue to be useful and whether the time is right for a full-fledged conversion effort to XML is explored. The author concludes that the MARC format will be relevant well into the future, and its use will not hamper access to bibliographic information via the web. Early XML exploratory efforts carried out at the Stanford University's Lane Medical Library are reported on. Although these efforts are a promising start, much more consultation and investigation is needed to arrive at broadly acceptable standards for XML library information encoding and retrieval.

Date

5. 6.2001 12:21:28
28. 7.2006 9:58:00

0.014407165 = product of:
  0.02881433 = sum of:
    0.017449262 = product of:
      0.034898523 = sum of:
        0.034898523 = weight(_text_:web in 2845) [ClassicSimilarity], result of:
          0.034898523 = score(doc=2845,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.2884563 = fieldWeight in 2845, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=2845)
      0.5 = coord(1/2)
    0.011365069 = product of:
      0.056825344 = sum of:
        0.056825344 = weight(_text_:22 in 2845) [ClassicSimilarity], result of:
          0.056825344 = score(doc=2845,freq=4.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = 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.2 = coord(1/5)
  0.5 = coord(2/4)

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

0.012558883 = product of:
  0.050235532 = sum of:
    0.050235532 = sum of:
      0.013086946 = weight(_text_:web in 414) [ClassicSimilarity], result of:
        0.013086946 = score(doc=414,freq=2.0), product of:
          0.12098375 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.03707166 = queryNorm
          0.108171105 = fieldWeight in 414, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0234375 = fieldNorm(doc=414)
      0.037148587 = weight(_text_:seiten in 414) [ClassicSimilarity], result of:
        0.037148587 = score(doc=414,freq=2.0), product of:
          0.20383513 = queryWeight, product of:
            5.4984083 = idf(docFreq=491, maxDocs=44218)
            0.03707166 = queryNorm
          0.1822482 = fieldWeight in 414, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.4984083 = idf(docFreq=491, maxDocs=44218)
            0.0234375 = fieldNorm(doc=414)
  0.25 = coord(1/4)

Content

Als Vortragender zur RDA (Ressource Description Access) war wieder Gordon Dunsire eingeladen. Er gab wieder einen kurzen historischen Rückblick und eine Auflistung allgemeiner Kritikpunkte an der RDA. Von seiten Dunsires wurde klar dargestellt, dass Katalogregeln unabhängig vom Format sein müssen: RDA = nicht MARC21. Bei der RDA gehe es um Inhalte und nicht um Struktur. RDA basiert auf dem FRBR-Entitäten-Modell; eine deutsche Übersetzung der FRBR liegt vor und kann kostenfrei von der Homepage der Deutschen Nationalbibliothek runtergeladen werden. Die RDA soll 2009 fertiggestellt sein. Im Anschluss daran sprach Gudrun Henze zur "Internationalisierung des Deutschen Regelwerkes": AfS (Arbeitsstelle für Standardisierung) und AGV (Arbeitsgemeinschaft der Verbundsysteme) haben mittlerweile Ziele und Maßnahmen beschlossen: - Deutsch wird zur Ansetzungssprache - Entitäten sollen internationalen Standards entsprechen - Künftig soll es ein einheitliches Regelwerk geben, das die Sonderregeln bereits enthält - Individualisierung von Normdaten - flache Hierarchien - Anpassung der Splitregeln an die ISBD - Ansetzung der Einheitssachtitel hat hohe Priorität
In weiterer Folge berichtet sie über die Stellungnahmen zu Part 1 - hier werden keine Hindernisse für eine Umsetzung gesehen. Bei Chapter 6-7 wurde festgehalten, dass die Angaben für Verweisungen zu allgemein gehalten wären und Verbünde schwer mit Kann-Bestimmungen umgehen könnten. Eine Begrenzung auf drei Autoren sei außerdem nicht mehr zeitgemäß. Die RDA-Deutsch soll wie folgt aussehen: - modularer Aufbau - Web-Produkt - Regeln für formale und inhaltliche Erschließung - verbundübergreifende Anwendungsrichtlinien Als vierte Vortragende gab Frau Christine Hengel einen Bericht zu den "Neuen Wegen" der Normdaten. Basis für die RDA ist ein konzeptionelles Modell für Normdaten, das von der IFLA-Arbeitsgruppe FRANAR erarbeitet wird. Dieses soll 2007 abgeschlossen sein. - Es wird gemeinsame Regeln für die Ansetzung von Personen und Körperschaften geben - sie beschäftigen sich mit: Normieren, Identifizieren, Anreichern, Sucheinstiegen. - Die neuen Regeln für die Ansetzung von Personen in den PND und SWD werden in die RDA einfließen - Es soll zu einer einheitliche Anwendung von kompatiblen Datenmodellen für die Bereiche Bibliotheken, Archive, Dokumentationen und Museen kommen - Forderung einer Online-Kommunikation mit Normdaten: dazu muss sich der Teilnehmerkreis von den Redaktionen bis hin zum Katalog stark erweitern. Das neue Redaktionsverfahren soll ab Mitte 2007 für die PND zum Einsatz kommen. Im Anschluss daran für die GKD. In der zweiten Hälfte des Jahres 2007 ist der Umstieg auf MARC21 geplant. Insgesamt war die Veranstaltung zu Recht schwach besucht; es gab wenig Neues, kaum Überraschendes und daher auch keine wirklich anregende Diskussion."

0.012389246 = product of:
  0.049556985 = sum of:
    0.049556985 = product of:
      0.123892464 = sum of:
        0.06307297 = weight(_text_:28 in 4335) [ClassicSimilarity], result of:
          0.06307297 = score(doc=4335,freq=2.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.4749455 = fieldWeight in 4335, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.09375 = fieldNorm(doc=4335)
        0.06081949 = weight(_text_:29 in 4335) [ClassicSimilarity], result of:
          0.06081949 = score(doc=4335,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.46638384 = fieldWeight in 4335, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.09375 = fieldNorm(doc=4335)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Date

28. 6.1996 14:29:37

0.0111818565 = product of:
  0.022363713 = sum of:
    0.015268105 = product of:
      0.03053621 = sum of:
        0.03053621 = weight(_text_:web in 892) [ClassicSimilarity], result of:
          0.03053621 = score(doc=892,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.25239927 = fieldWeight in 892, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0546875 = fieldNorm(doc=892)
      0.5 = coord(1/2)
    0.0070956075 = product of:
      0.035478037 = sum of:
        0.035478037 = weight(_text_:29 in 892) [ClassicSimilarity], result of:
          0.035478037 = score(doc=892,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.27205724 = fieldWeight in 892, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0546875 = fieldNorm(doc=892)
      0.2 = coord(1/5)
  0.5 = coord(2/4)

Abstract

Secondary information, e.g. MARC based bibliographic records, comprises structured data for identifying, tagging, retrieving and management of primary documents. SGML, the standard format for coding content and structure of primary documents, was introduced in 1986 as a publishing tool but is now being applied to bibliographic records. SGML now comprises standard definitions (DTD) for books, serials, articles and mathematical formulae. A simplified version (HTML) is used for Web pages. Pilot projects to develop SGML as a standard for bibliographic exchange include the Dublin Core, listing 13 descriptive elements for Internet documents; the French GRISELI programme using SGML for exchanging grey literature and US experiments on reformatting USMARC for use with SGML-based records

Date

29. 1.1996 16:50:24

0.011149941 = product of:
  0.022299882 = sum of:
    0.015268105 = product of:
      0.03053621 = sum of:
        0.03053621 = weight(_text_:web in 2837) [ClassicSimilarity], result of:
          0.03053621 = score(doc=2837,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.25239927 = fieldWeight in 2837, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2837)
      0.5 = coord(1/2)
    0.007031777 = product of:
      0.035158884 = sum of:
        0.035158884 = weight(_text_:22 in 2837) [ClassicSimilarity], result of:
          0.035158884 = score(doc=2837,freq=2.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = queryNorm
            0.2708308 = fieldWeight in 2837, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2837)
      0.2 = coord(1/5)
  0.5 = coord(2/4)

Abstract

This paper describes the Metadata Object Description Schema (MODS), its accompanying documentation and some of its applications. It reviews the MODS user guidelines provided by the Library of Congress and how they enable a user of the schema to consistently apply MODS as a metadata scheme. Because the schema itself could not fully document appropriate usage, the guidelines provide element definitions, history, relationships with other elements, usage conventions, and examples. Short descriptions of some MODS applications are given and a more detailed discussion of its use in the Library of Congress's Minerva project for Web archiving is given.

Source

Library hi tech. 22(2004) no.1, S.89-98

0.010090989 = product of:
  0.040363956 = sum of:
    0.040363956 = product of:
      0.10090989 = sum of:
        0.05068291 = weight(_text_:29 in 5228) [ClassicSimilarity], result of:
          0.05068291 = score(doc=5228,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.38865322 = fieldWeight in 5228, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.078125 = fieldNorm(doc=5228)
        0.050226983 = weight(_text_:22 in 5228) [ClassicSimilarity], result of:
          0.050226983 = score(doc=5228,freq=2.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = queryNorm
            0.38690117 = fieldWeight in 5228, 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=5228)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Date

29. 9.1996 18:58:22

0.009584447 = product of:
  0.019168895 = sum of:
    0.013086946 = product of:
      0.026173891 = sum of:
        0.026173891 = weight(_text_:web in 2773) [ClassicSimilarity], result of:
          0.026173891 = score(doc=2773,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.21634221 = fieldWeight in 2773, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.046875 = fieldNorm(doc=2773)
      0.5 = coord(1/2)
    0.0060819495 = product of:
      0.030409746 = sum of:
        0.030409746 = weight(_text_:29 in 2773) [ClassicSimilarity], result of:
          0.030409746 = score(doc=2773,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.23319192 = fieldWeight in 2773, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.046875 = fieldNorm(doc=2773)
      0.2 = coord(1/5)
  0.5 = coord(2/4)

Abstract

In response to libraries' frustration over their rich resources being invisible on the web, Zepheira, at the request of the Library of Congress, created BIBFRAME, a bibliographic metadata framework for cataloging. The model replaces MARC records with linked data, promoting resource visibility through a rich network of links. In place of formal taxonomies, a small but extensible vocabulary streamlines metadata efforts. Rather than using a unique bibliographic record to describe one item, BIBFRAME draws on the Dublin Core and the Functional Requirements for Bibliographic Records (FRBR) to generate formalized descriptions of Work, Instance, Authority and Annotation as well as associations between items. Zepheira trains librarians to transform MARC records to BIBFRAME resources and adapt the vocabulary for specialized needs, while subject matter experts and technical experts manage content, site design and usability. With a different approach toward data modeling and metadata, previously invisible resources gain visibility through linking.

Source

Bulletin of the Association for Information Science and Technology. 41(2015) no.4, S.23-29

0.009557092 = product of:
  0.019114183 = sum of:
    0.013086946 = product of:
      0.026173891 = sum of:
        0.026173891 = weight(_text_:web in 3841) [ClassicSimilarity], result of:
          0.026173891 = score(doc=3841,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.21634221 = fieldWeight in 3841, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.046875 = fieldNorm(doc=3841)
      0.5 = coord(1/2)
    0.0060272375 = product of:
      0.030136187 = sum of:
        0.030136187 = weight(_text_:22 in 3841) [ClassicSimilarity], result of:
          0.030136187 = score(doc=3841,freq=2.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = queryNorm
            0.23214069 = fieldWeight in 3841, 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=3841)
      0.2 = coord(1/5)
  0.5 = coord(2/4)

Abstract

This entry describes the development of the MARC Communications format. After a brief overview of the initial 10 years it describes the succeeding phases of development up to the present. This takes the reader through the expansion of the format for all types of bibliographic data and for a multiple character scripts. At the same time a large business community was developing that offered products based on the format to the library community. The introduction of the Internet in the 1990s and the Web technology brought new opportunities and challenges and the format was adapted to this new environment. There has been a great deal of international adoption of the format that has continued into the 2000s. More recently new syntaxes for MARC 21 and models are being explored.

Date

27. 8.2011 14:22:38

0.008259498 = product of:
  0.03303799 = sum of:
    0.03303799 = product of:
      0.082594976 = sum of:
        0.042048648 = weight(_text_:28 in 3865) [ClassicSimilarity], result of:
          0.042048648 = score(doc=3865,freq=2.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.31663033 = fieldWeight in 3865, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.0625 = fieldNorm(doc=3865)
        0.040546328 = weight(_text_:29 in 3865) [ClassicSimilarity], result of:
          0.040546328 = score(doc=3865,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.31092256 = fieldWeight in 3865, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0625 = fieldNorm(doc=3865)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Date

30. 7.2004 14:20:29

Series

IFLA series on bibliographic control; vol. 28

0.008072792 = product of:
  0.032291166 = sum of:
    0.032291166 = product of:
      0.08072791 = sum of:
        0.040546328 = weight(_text_:29 in 2830) [ClassicSimilarity], result of:
          0.040546328 = score(doc=2830,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.31092256 = fieldWeight in 2830, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0625 = fieldNorm(doc=2830)
        0.040181585 = weight(_text_:22 in 2830) [ClassicSimilarity], result of:
          0.040181585 = score(doc=2830,freq=2.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = queryNorm
            0.30952093 = fieldWeight in 2830, 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=2830)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Date

9.12.2005 19:29:32

Source

Library hi tech. 22(2004) no.1, S.18-27

0.008072792 = product of:
  0.032291166 = sum of:
    0.032291166 = product of:
      0.08072791 = sum of:
        0.040546328 = weight(_text_:29 in 562) [ClassicSimilarity], result of:
          0.040546328 = score(doc=562,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.31092256 = fieldWeight in 562, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0625 = fieldNorm(doc=562)
        0.040181585 = weight(_text_:22 in 562) [ClassicSimilarity], result of:
          0.040181585 = score(doc=562,freq=2.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = queryNorm
            0.30952093 = fieldWeight in 562, 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=562)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Date

9.12.2005 19:21:29

Source

Library hi tech. 22(2004) no.2, S.166-174

0.0072270604 = product of:
  0.028908242 = sum of:
    0.028908242 = product of:
      0.0722706 = sum of:
        0.03679257 = weight(_text_:28 in 4716) [ClassicSimilarity], result of:
          0.03679257 = score(doc=4716,freq=2.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.27705154 = fieldWeight in 4716, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4716)
        0.035478037 = weight(_text_:29 in 4716) [ClassicSimilarity], result of:
          0.035478037 = score(doc=4716,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.27205724 = fieldWeight in 4716, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4716)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Date

4. 6.2012 13:28:29

0.007195145 = product of:
  0.02878058 = sum of:
    0.02878058 = product of:
      0.07195145 = sum of:
        0.03679257 = weight(_text_:28 in 2844) [ClassicSimilarity], result of:
          0.03679257 = score(doc=2844,freq=2.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.27705154 = fieldWeight in 2844, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2844)
        0.035158884 = weight(_text_:22 in 2844) [ClassicSimilarity], result of:
          0.035158884 = score(doc=2844,freq=2.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = queryNorm
            0.2708308 = fieldWeight in 2844, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2844)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Source

Library hi tech. 22(2004) no.1, S.28-39

0.007195145 = product of:
  0.02878058 = sum of:
    0.02878058 = product of:
      0.07195145 = sum of:
        0.03679257 = weight(_text_:28 in 4750) [ClassicSimilarity], result of:
          0.03679257 = score(doc=4750,freq=2.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.27705154 = fieldWeight in 4750, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4750)
        0.035158884 = weight(_text_:22 in 4750) [ClassicSimilarity], result of:
          0.035158884 = score(doc=4750,freq=2.0), product of:
            0.12981863 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03707166 = queryNorm
            0.2708308 = fieldWeight in 4750, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4750)
      0.4 = coord(2/5)
  0.25 = coord(1/4)

Date

9.12.2005 19:24:28

Source

Library hi tech. 22(2004) no.1, S.6-7

0.0066784043 = product of:
  0.026713617 = sum of:
    0.026713617 = product of:
      0.053427234 = sum of:
        0.053427234 = weight(_text_:web in 1467) [ClassicSimilarity], result of:
          0.053427234 = score(doc=1467,freq=12.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.4416067 = fieldWeight in 1467, product of:
              3.4641016 = tf(freq=12.0), with freq of:
                12.0 = termFreq=12.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1467)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

XML (eXtensible Markup Language) is fast gaining favor as the universal format for data and document exchange -- in effect becoming the lingua franca of the Information Age. Currently, "library information" is at a particular disadvantage on the rapidly evolving World Wide Web. Why? Despite libraries'explorations of web catalogs, scanning projects, digital data repositories, and creation of web pages galore, there remains a digital divide. The core of libraries' data troves are stored in proprietary formats of integrated library systems (ILS) and in the complex and arcane MARC formats -- both restricted chiefly to the province of technical services and systems librarians. Even they are hard-pressed to extract and integrate this wealth of data with resources from outside this rarefied environment. Segregation of library information underlies many difficulties: producing standard bibliographic citations from MARC data, automatically creating new materials lists (including new web resources) on a particular topic, exchanging data with our vendors, and even migrating from one ILS to another. Why do we continue to hobble our potential by embracing these self-imposed limitations? Most ILSs began in libraries, which soon recognized the pitfalls of do-it-yourself solutions. Thus, we wisely anticipated the necessity for standards. However, with the advent of the web, we soon found "our" collections and a flood of new resources appearing in digital format on opposite sides of the divide. If we do not act quickly to integrate library resources with mainstream web resources, we are in grave danger of becoming marginalized

0.006543473 = product of:
  0.026173891 = sum of:
    0.026173891 = product of:
      0.052347783 = sum of:
        0.052347783 = weight(_text_:web in 3918) [ClassicSimilarity], result of:
          0.052347783 = score(doc=3918,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.43268442 = fieldWeight in 3918, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.09375 = fieldNorm(doc=3918)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

0.0063109063 = product of:
  0.0126218125 = sum of:
    0.0043623154 = product of:
      0.008724631 = sum of:
        0.008724631 = weight(_text_:web in 2312) [ClassicSimilarity], result of:
          0.008724631 = score(doc=2312,freq=2.0), product of:
            0.12098375 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03707166 = queryNorm
            0.07211407 = fieldWeight in 2312, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.015625 = fieldNorm(doc=2312)
      0.5 = coord(1/2)
    0.008259498 = product of:
      0.020648744 = sum of:
        0.010512162 = weight(_text_:28 in 2312) [ClassicSimilarity], result of:
          0.010512162 = score(doc=2312,freq=2.0), product of:
            0.13280044 = queryWeight, product of:
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.03707166 = queryNorm
            0.07915758 = fieldWeight in 2312, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5822632 = idf(docFreq=3342, maxDocs=44218)
              0.015625 = fieldNorm(doc=2312)
        0.010136582 = weight(_text_:29 in 2312) [ClassicSimilarity], result of:
          0.010136582 = score(doc=2312,freq=2.0), product of:
            0.13040651 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03707166 = queryNorm
            0.07773064 = fieldWeight in 2312, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.015625 = fieldNorm(doc=2312)
      0.4 = coord(2/5)
  0.5 = coord(2/4)

Date

30. 7.2004 14:20:29

Footnote

Rez. in: KO 31(2004) no.4, S.255-257: (P. Riva): "Cataloguing standardization at the international level can be viewed as proceeding in a series of milestone conferences. This meeting, the first in a series which will cover different regions of the world, will take its place in that progression. The first IFLA Meeting of Experts an an International Cataloguing Code (IME ICC), held July 28-30, 2003 at Die Deutsche Bibliothek in Frankfurt, gathered representatives of almost all European countries as well as three of the four AACR author countries. As explained in the introduction by Barbara Tillett, chair of the IME ICC planning committee, the plan is for five meetings in total. Subsequent meetings are to take place in Buenos Aires, Argentina (held August 17-18, 2004) for Latin America and the Carribean, to be followed by Alexandria, Egypt (2005) for the Middle East, Seoul, South Korea (2006) for Asia, and Durban, South Africa (2007) for Africa. The impetus for planning these meetings was triggered by the 40th anniversary of the Paris Principles, approved at the International Conference an Cataloguing Principles held in 1961. Many will welcome the timely publication of the reports and papers from this important conference in book form. The original conference website (details given an p. 176) which includes most of the same material, is still extant, but the reports and papers gathered into this volume will be referred to by cataloguing rule makers long after the web as we know it has transformed itself into a new (and quite possibly not backwards compatible) environment.