Search (42 results, page 1 of 3)

  • × theme_ss:"Auszeichnungssprachen"
  1. Pott, O.; Wielage, G.: XML Praxis und Referenz (2000) 0.01 
    0.014517997 = product of:
  0.05081299 = sum of:
    0.028870367 = weight(_text_:g in 6985) [ClassicSimilarity], result of:
      0.028870367 = score(doc=6985,freq=2.0), product of:
        0.13914184 = queryWeight, product of:
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.03704574 = queryNorm
        0.20748875 = fieldWeight in 6985, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.0390625 = fieldNorm(doc=6985)
    0.021942623 = weight(_text_:u in 6985) [ClassicSimilarity], result of:
      0.021942623 = score(doc=6985,freq=2.0), product of:
        0.121304214 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03704574 = queryNorm
        0.1808892 = fieldWeight in 6985, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.0390625 = fieldNorm(doc=6985)
  0.2857143 = coord(2/7)
    Issue
    2., erw. u. aktual. Aufl.
  2. Anderson, R.; Birbeck, M.; Kay, M.; Livingstone, S.; Loesgen, B.; Martin, D.; Mohr, S.; Ozu, N.; Peat, B.; Pinnock, J.; Stark, P.; Williams, K.: XML professionell : behandelt W3C DOM, SAX, CSS, XSLT, DTDs, XML Schemas, XLink, XPointer, XPath, E-Commerce, BizTalk, B2B, SOAP, WAP, WML (2000) 0.01 
    0.012270578 = product of:
  0.028631348 = sum of:
    0.007936996 = product of:
      0.015873993 = sum of:
        0.015873993 = weight(_text_:p in 729) [ClassicSimilarity], result of:
          0.015873993 = score(doc=729,freq=2.0), product of:
            0.13319843 = queryWeight, product of:
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.03704574 = queryNorm
            0.11917553 = fieldWeight in 729, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.0234375 = fieldNorm(doc=729)
      0.5 = coord(1/2)
    0.013165573 = weight(_text_:u in 729) [ClassicSimilarity], result of:
      0.013165573 = score(doc=729,freq=2.0), product of:
        0.121304214 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03704574 = queryNorm
        0.10853352 = fieldWeight in 729, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.0234375 = fieldNorm(doc=729)
    0.007528779 = product of:
      0.015057558 = sum of:
        0.015057558 = weight(_text_:22 in 729) [ClassicSimilarity], result of:
          0.015057558 = score(doc=729,freq=2.0), product of:
            0.12972787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03704574 = queryNorm
            0.116070345 = fieldWeight in 729, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0234375 = fieldNorm(doc=729)
      0.5 = coord(1/2)
  0.42857143 = coord(3/7)
    Date
    22. 6.2005 15:12:11
    Theme
    Grundlagen u. Einführungen: Allgemeine Literatur
  3. Pepper, S.; Moore, G.; TopicMaps.Org Authoring Group: XML Topic Maps (XTM) 1.0 : TopicMaps.Org Specification (2001) 0.01 
    0.011217687 = product of:
  0.039261904 = sum of:
    0.03464444 = weight(_text_:g in 1623) [ClassicSimilarity], result of:
      0.03464444 = score(doc=1623,freq=2.0), product of:
        0.13914184 = queryWeight, product of:
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.03704574 = queryNorm
        0.24898648 = fieldWeight in 1623, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.046875 = fieldNorm(doc=1623)
    0.0046174643 = weight(_text_:a in 1623) [ClassicSimilarity], result of:
      0.0046174643 = score(doc=1623,freq=4.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.10809815 = fieldWeight in 1623, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=1623)
  0.2857143 = coord(2/7)
    Abstract
    This specification provides a model and grammar for representing the structure of information resources used to define topics, and the associations (relationships) between topics. Names, resources, and relationships are said to be characteristics of abstract subjects, which are called topics. Topics have their characteristics within scopes: i.e. the limited contexts within which the names and resources are regarded as their name, resource, and relationship characteristics. One or more interrelated documents employing this grammar is called a topic map.TopicMaps.Org is an independent consortium of parties developing the applicability of the topic map paradigm [ISO13250] to the World Wide Web by leveraging the XML family of specifications. This specification describes version 1.0 of XML Topic Maps (XTM) 1.0 [XTM], an abstract model and XML grammar for interchanging Web-based topic maps, written by the members of the TopicMaps.Org Authoring Group. More information on XTM and TopicMaps.Org is available at http://www.topicmaps.org/about.html. All versions of the XTM Specification are permanently licensed to the public, as provided by the Charter of TopicMaps.Org.
  4. Pott, O.; Wielage, G.: XML Praxis und Referenz (2000) 0.01 
    0.009898412 = product of:
  0.06928888 = sum of:
    0.06928888 = weight(_text_:g in 5156) [ClassicSimilarity], result of:
      0.06928888 = score(doc=5156,freq=2.0), product of:
        0.13914184 = queryWeight, product of:
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.03704574 = queryNorm
        0.49797297 = fieldWeight in 5156, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.09375 = fieldNorm(doc=5156)
  0.14285715 = coord(1/7)
  5. as: XML: Extensible Markup Language : I: Was ist XML? (2001) 0.01 
    0.008725047 = product of:
  0.030537665 = sum of:
    0.0054417336 = weight(_text_:a in 4950) [ClassicSimilarity], result of:
      0.0054417336 = score(doc=4950,freq=2.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.12739488 = fieldWeight in 4950, 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=4950)
    0.025095932 = product of:
      0.050191864 = sum of:
        0.050191864 = weight(_text_:22 in 4950) [ClassicSimilarity], result of:
          0.050191864 = score(doc=4950,freq=2.0), product of:
            0.12972787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03704574 = queryNorm
            0.38690117 = fieldWeight in 4950, 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=4950)
      0.5 = coord(1/2)
  0.2857143 = coord(2/7)
    Date
    30. 3.2003 11:06:22
    Type
    a
  6. Trotman, A.: Searching structured documents (2004) 0.01 
    0.0076850806 = product of:
  0.02689778 = sum of:
    0.009330629 = weight(_text_:a in 2538) [ClassicSimilarity], result of:
      0.009330629 = score(doc=2538,freq=12.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.21843673 = fieldWeight in 2538, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2538)
    0.017567152 = product of:
      0.035134304 = sum of:
        0.035134304 = weight(_text_:22 in 2538) [ClassicSimilarity], result of:
          0.035134304 = score(doc=2538,freq=2.0), product of:
            0.12972787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03704574 = queryNorm
            0.2708308 = fieldWeight in 2538, 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=2538)
      0.5 = coord(1/2)
  0.2857143 = coord(2/7)
    Abstract
    Structured document interchange formats such as XML and SGML are ubiquitous, however, information retrieval systems supporting structured searching are not. Structured searching can result in increased precision. A search for the author "Smith" in an unstructured corpus of documents specializing in iron-working could have a lower precision than a structured search for "Smith as author" in the same corpus. Analysis of XML retrieval languages identifies additional functionality that must be supported including searching at, and broken across multiple nodes in the document tree. A data structure is developed to support structured document searching. Application of this structure to information retrieval is then demonstrated. Document ranking is examined and adapted specifically for structured searching.
    Date
    14. 8.2004 10:39:22
    Type
    a
  7. Berliner XMLTage 2004 : 11.-13. Oktober 2004 in Berlin. Proceedings (2004) 0.01 
    0.0075231846 = product of:
  0.05266229 = sum of:
    0.05266229 = weight(_text_:u in 4284) [ClassicSimilarity], result of:
      0.05266229 = score(doc=4284,freq=2.0), product of:
        0.121304214 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03704574 = queryNorm
        0.43413407 = fieldWeight in 4284, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.09375 = fieldNorm(doc=4284)
  0.14285715 = coord(1/7)
    Editor
    Tolksdorf, R. u. R. Eckstein
  8. Schröder, A.: Web der Zukunft : RDF - Der erste Schritt zum semantischen Web 0.01 
    0.0074952478 = product of:
  0.026233366 = sum of:
    0.006156619 = weight(_text_:a in 1457) [ClassicSimilarity], result of:
      0.006156619 = score(doc=1457,freq=4.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.14413087 = fieldWeight in 1457, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=1457)
    0.020076746 = product of:
      0.040153492 = sum of:
        0.040153492 = weight(_text_:22 in 1457) [ClassicSimilarity], result of:
          0.040153492 = score(doc=1457,freq=2.0), product of:
            0.12972787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03704574 = queryNorm
            0.30952093 = fieldWeight in 1457, 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=1457)
      0.5 = coord(1/2)
  0.2857143 = coord(2/7)
    Abstract
    Seit dem 22. Februar 1999 ist das Resource Description Framework (RDF) als W3C-Empfehlung verfügbar. Doch was steckt hinter diesem Standard, der das Zeitalter des Semantischen Webs einläuten soll? Was RDF bedeutet, wozu man es einsetzt, welche Vorteile es gegenüber XML hat und wie man RDF anwendet, soll in diesem Artikel erläutert werden.
    Type
    a
  9. Vonhoegen, H.: Einstieg in XML (2002) 0.01 
    0.006898118 = product of:
  0.024143413 = sum of:
    0.015359836 = weight(_text_:u in 4002) [ClassicSimilarity], result of:
      0.015359836 = score(doc=4002,freq=2.0), product of:
        0.121304214 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03704574 = queryNorm
        0.12662244 = fieldWeight in 4002, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.02734375 = fieldNorm(doc=4002)
    0.008783576 = product of:
      0.017567152 = sum of:
        0.017567152 = weight(_text_:22 in 4002) [ClassicSimilarity], result of:
          0.017567152 = score(doc=4002,freq=2.0), product of:
            0.12972787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03704574 = queryNorm
            0.1354154 = fieldWeight in 4002, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.02734375 = fieldNorm(doc=4002)
      0.5 = coord(1/2)
  0.2857143 = coord(2/7)
    Footnote
    Rez. in: XML Magazin und Web Services 2003, H.1, S.14 (S. Meyen): "Seit dem 22. Februar 1999 ist das Resource Description Framework (RDF) als W3C-Empfehlung verfügbar. Doch was steckt hinter diesem Standard, der das Zeitalter des Semantischen Webs einläuten soll? Was RDF bedeutet, wozu man es einsetzt, welche Vorteile es gegenüber XML hat und wie man RDF anwendet, soll in diesem Artikel erläutert werden. Schlägt man das Buch auf und beginnt, im EinleitungsKapitel zu schmökern, fällt sogleich ins Auge, dass der Leser nicht mit Lektionen im Stile von "bei XML sind die spitzen Klammern ganz wichtig" belehrt wird, obgleich es sich um ein Buch für Anfänger handelt. Im Gegenteil: Es geht gleich zur Sache und eine gesunde Mischung an Vorkenntnissen wird vorausgesetzt. Wer sich heute für XML interessiert, der hat ja mit 99-prozentiger Wahrscheinlichkeit schon seine einschlägigen Erfahrungen mit HTML und dem Web gemacht und ist kein Newbie in dem Reich der spitzen Klammern und der (einigermaßen) wohlformatierten Dokumente. Und hier liegt eine deutliche Stärke des Werkes Helmut Vonhoegens, der seinen Einsteiger-Leser recht gut einzuschätzen weiß und ihn daher praxisnah und verständlich ans Thema heranführt. Das dritte Kapitel beschäftigt sich mit der Document Type Definition (DTD) und beschreibt deren Einsatzziele und Verwendungsweisen. Doch betont der Autor hier unablässig die Begrenztheit dieses Ansatzes, welche den Ruf nach einem neuen Konzept deutlich macht: XML Schema, welches er im folgenden Kapitel darstellt. Ein recht ausführliches Kapitel widmet sich dann dem relativ aktuellen XML Schema-Konzept und erläutert dessen Vorzüge gegenüber der DTD (Modellierung komplexer Datenstrukturen, Unterstützung zahlreicher Datentypen, Zeichenbegrenzungen u.v.m.). XML Schema legt, so erfährt der Leser, wie die alte DTD, das Vokabular und die zulässige Grammatik eines XML-Dokuments fest, ist aber seinerseits ebenfalls ein XML-Dokument und kann (bzw. sollte) wie jedes andere XML auf Wohlgeformtheit überprüft werden. Weitere Kapitel behandeln die Navigations-Standards XPath, XLink und XPointer, Transformationen mit XSLT und XSL und natürlich die XML-Programmierschnittstellen DOM und SAX. Dabei kommen verschiedene Implementierungen zum Einsatz und erfreulicherweise werden Microsoft-Ansätze auf der einen und Java/Apache-Projekte auf der anderen Seite in ungefähr vergleichbarem Umfang vorgestellt. Im letzten Kapitel schließlich behandelt Vonhoegen die obligatorischen Web Services ("Webdienste") als Anwendungsfall von XML und demonstriert ein kleines C#- und ASP-basiertes Beispiel (das Java-Äquivalent mit Apache Axis fehlt leider). "Einstieg in XML" präsentiert seinen Stoff in klar verständlicher Form und versteht es, seine Leser auf einem guten Niveau "abzuholen". Es bietet einen guten Überblick über die Grundlagen von XML und kann - zumindest derzeit noch - mit recht hoher Aktualität aufwarten."
    Theme
    Grundlagen u. Einführungen: Allgemeine Literatur
  10. Patrick, D.A.: XML in der Praxis : Unternehmensübergreifende Vorteile durch Enterprise Content Management (1999) 0.01 
    0.0061075334 = product of:
  0.021376366 = sum of:
    0.0038092136 = weight(_text_:a in 1461) [ClassicSimilarity], result of:
      0.0038092136 = score(doc=1461,freq=2.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.089176424 = fieldWeight in 1461, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1461)
    0.017567152 = product of:
      0.035134304 = sum of:
        0.035134304 = weight(_text_:22 in 1461) [ClassicSimilarity], result of:
          0.035134304 = score(doc=1461,freq=2.0), product of:
            0.12972787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03704574 = queryNorm
            0.2708308 = fieldWeight in 1461, 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=1461)
      0.5 = coord(1/2)
  0.2857143 = coord(2/7)
    Date
    30. 3.2003 10:50:22
    Type
    a
  11. Ioannides, D.: XML schema languages : beyond DTD (2000) 0.01 
    0.0059179356 = product of:
  0.020712774 = sum of:
    0.005655216 = weight(_text_:a in 720) [ClassicSimilarity], result of:
      0.005655216 = score(doc=720,freq=6.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.13239266 = fieldWeight in 720, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=720)
    0.015057558 = product of:
      0.030115116 = sum of:
        0.030115116 = weight(_text_:22 in 720) [ClassicSimilarity], result of:
          0.030115116 = score(doc=720,freq=2.0), product of:
            0.12972787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03704574 = queryNorm
            0.23214069 = fieldWeight in 720, 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=720)
      0.5 = coord(1/2)
  0.2857143 = coord(2/7)
    Abstract
    The flexibility and extensibility of XML have largely contributed to its wide acceptance beyond the traditional realm of SGML. Yet, there is still one more obstacle to be overcome before XML is able to become the evangelized universal data/document format. The obstacle is posed by the limitations of the legacy standard for constraining the contents of an XML document. The traditionally used DTD (document type definition) format does not lend itself to be used in the wide variety of applications XML is capable of handling. The World Wide Web Consortium (W3C) has charged the XML schema working group with the task of developing a schema language to replace DTD. This XML schema language is evolving based on early drafts of XML schema languages. Each one of these early efforts adopted a slightly different approach, but all of them were moving in the same direction.
    Date
    28. 1.2006 19:01:22
    Type
    a
  12. Holzheid, G.: Dublin Core, SGML und die Zukunft der Erschließung am Beispiel einer Studie zur Optimierung des Dokumentenmanagements einer großen Nichtregierungsorganisation (2005) 0.01 
    0.005774074 = product of:
  0.040418513 = sum of:
    0.040418513 = weight(_text_:g in 2192) [ClassicSimilarity], result of:
      0.040418513 = score(doc=2192,freq=2.0), product of:
        0.13914184 = queryWeight, product of:
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.03704574 = queryNorm
        0.29048425 = fieldWeight in 2192, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.7559474 = idf(docFreq=2809, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2192)
  0.14285715 = coord(1/7)
  13. Michel, T.F.: XML kompakt : Eine praktische Einführung (1999) 0.01 
    0.005015457 = product of:
  0.035108197 = sum of:
    0.035108197 = weight(_text_:u in 1462) [ClassicSimilarity], result of:
      0.035108197 = score(doc=1462,freq=2.0), product of:
        0.121304214 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03704574 = queryNorm
        0.28942272 = fieldWeight in 1462, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.0625 = fieldNorm(doc=1462)
  0.14285715 = coord(1/7)
    Theme
    Grundlagen u. Einführungen: Allgemeine Literatur
  14. Stein, M.: Workshop XML (2001) 0.00 
    0.0043885247 = product of:
  0.030719671 = sum of:
    0.030719671 = weight(_text_:u in 1463) [ClassicSimilarity], result of:
      0.030719671 = score(doc=1463,freq=2.0), product of:
        0.121304214 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03704574 = queryNorm
        0.25324488 = fieldWeight in 1463, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1463)
  0.14285715 = coord(1/7)
    Theme
    Grundlagen u. Einführungen: Allgemeine Literatur
  15. XML in libraries (2002) 0.00 
    0.003692802 = product of:
  0.012924806 = sum of:
    0.007483072 = product of:
      0.014966144 = sum of:
        0.014966144 = weight(_text_:p in 3100) [ClassicSimilarity], result of:
          0.014966144 = score(doc=3100,freq=4.0), product of:
            0.13319843 = queryWeight, product of:
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.03704574 = queryNorm
            0.11235977 = fieldWeight in 3100, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.015625 = fieldNorm(doc=3100)
      0.5 = coord(1/2)
    0.005441734 = weight(_text_:a in 3100) [ClassicSimilarity], result of:
      0.005441734 = score(doc=3100,freq=50.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.1273949 = fieldWeight in 3100, product of:
          7.071068 = tf(freq=50.0), with freq of:
            50.0 = termFreq=50.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.015625 = fieldNorm(doc=3100)
  0.2857143 = coord(2/7)
    Footnote
    Rez. in: JASIST 55(2004) no.14, S.1304-1305 (Z. Holbrooks):"The eXtensible Markup Language (XML) and its family of enabling technologies (XPath, XPointer, XLink, XSLT, et al.) were the new "new thing" only a couple of years ago. Happily, XML is now a W3C standard, and its enabling technologies are rapidly proliferating and maturing. Together, they are changing the way data is handled an the Web, how legacy data is accessed and leveraged in corporate archives, and offering the Semantic Web community a powerful toolset. Library and information professionals need a basic understanding of what XML is, and what its impacts will be an the library community as content vendors and publishers convert to the new standards. Norman Desmarais aims to provide librarians with an overview of XML and some potential library applications. The ABCs of XML contains the useful basic information that most general XML works cover. It is addressed to librarians, as evidenced by the occasional reference to periodical vendors, MARC, and OPACs. However, librarians without SGML, HTML, database, or programming experience may find the work daunting. The snippets of code-most incomplete and unattended by screenshots to illustrate the result of the code's execution-obscure more often than they enlighten. A single code sample (p. 91, a book purchase order) is immediately recognizable and sensible. There are no figures, illustrations, or screenshots. Subsection headings are used conservatively. Readers are confronted with page after page of unbroken technical text, and occasionally oddly formatted text (in some of the code samples). The author concentrates an commercial products and projects. Library and agency initiatives-for example, the National Institutes of Health HL-7 and U.S. Department of Education's GEM project-are notable for their absence. The Library of Congress USMARC to SGML effort is discussed in chapter 1, which covers the relationship of XML to its parent SGML, the XML processor, and data type definitions, using MARC as its illustrative example. Chapter 3 addresses the stylesheet options for XML, including DSSSL, CSS, and XSL. The Document Style Semantics and Specification Language (DSSSL) was created for use with SGML, and pruned into DSSSL-Lite and further (DSSSL-online). Cascading Style Sheets (CSS) were created for use with HTML. Extensible Style Language (XSL) is a further revision (and extension) of DSSSL-o specifically for use with XML. Discussion of aural stylesheets and Synchronized Multimedia Integration Language (SMIL) round out the chapter.
    Chapter 4 introduces XML internal and external pointing and linking technologies. XML Link Language (XLL, now XLink) provides unidirectional, multi-ended, and typed linking. XPointer, used with XLink, provides addressing into the interior of XML documents. XPath operates an the logical structure of an XML document, creating a tree of nodes. Used with both XPointer and XSLT, it permits operations an strings, numbers, and Boolean expressions in the document. The final chapter, "Getting Started" argues for the adoption of a tool for XML production. The features and functionality of various tools for content development, application development, databases, and schema development provide an introduction to some of the available options. Roy Tennant is weIl known in the library community as an author (bis column "Digital Libraries" has appeared in Library Journal since 1997 and he has published Current Cites each month for more than a decade), an electronic discussion list manager (Web4Lib and XML4Lib), and as the creator and manager of UC/Berkeley's Digital Library SunSITE. Librarians have wondered what use they might make of XML since its beginnings. Tennant suggests one answer: "The Extensible Markup Language (XML) has the potential to exceed the impact of MARC an librarianship. While MARC is limited to bibliographic descriptionand arguably a subset at that, as any archivist will tell you-XML provides a highly-effective framework for encoding anything from a bibliographic record for a book to the book itself." (Tennant, p. vii) This slim paperback volume offers librarians and library managers concerned with automation projects "show and teIl" examples of XML technologies used as solutions to everyday tasks and challenges. What distinguishes this work is the editor and contributors' commitment to providing messy details. This book's target audience is technically savvy. While not a "cookbook" per se, the information provided an each project serves as a draft blueprint complete with acronyms and jargon. The inclusion of "lessons learned" (including failures as well as successes) is refreshing and commendable. Experienced IT and automation project veterans will appreciate the technical specifics more fully than the general reader.
    Tennant's collection covers a variety of well- and lesser-known XML-based pilot and prototype projects undertaken by libraries around the world. Some of the projects included are: Stanford's XMLMARC conversion, Oregon State's use of XML in interlibrary loaning, e-books (California Digital Library) and electronic scholarly publishing (University of Michigan), the Washington Research Library Consortium's XML-based Web Services, and using TEI Lite to support indexing (Halton Hills Public Library). Of the 13 projects presented, nine are sited in academe, three are state library endeavors, and one is an American public library initiative. The projects are gathered into sections grouped by seven library applications: the use of XML in library catalog records, interlibrary loan, cataloging and indexing, collection building, databases, data migration, and systems interoperability. Each project is introduced with a few paragraphs of background information. The project reports-averaging about 13 pages each-include project goals and justification, project description, challenges and lessons learned (successes and failures), future plans, implications of the work, contact information for individual(s) responsible for the project, and relevant Web links and resources. The clear strengths of this collection are in the details and the consistency of presentation. The concise project write-ups flow well and encourage interested readers to follow-up via personal contacts and URLs. The sole weakness is the price. XML in Libraries will excite and inspire institutions and organizations with technically adept staff resources and visionary leaders. Erik Ray has written a how-to book. Unlike most, Learning XML is not aimed at the professional programming community. The intended audience is readers familiar with a structured markup (HTML, TEX, etc.) and Web concepts (hypertext links, data representation). In the first six chapters, Ray introduces XMUs main concepts and tools for writing, viewing, testing, and transforming XML (chapter 1), describes basic syntax (chapter 2), discusses linking with XLink and XPointer (chapter 3), introduces Cascading Style Sheets for use with XML (chapter 4), explains document type definitions (DTDs) and schemas (chapter 5), and covers XSLT stylesheets and XPath (chapter 6). Chapter 7 introduces Unicode, internationalization and language support, including CSS and XSLT encoding. Chapter 8 is an overview of writing software for processing XML, and includes the Perl code for an XML syntax checker. This work is written very accessibly for nonprogrammers. Writers, designers, and students just starting to acquire Web technology skills will find Ray's style approachable. Concepts are introduced in a logical flow, and explained clearly. Code samples (130+), illustrations and screen shots (50+), and numerous tables are distributed throughout the text. Ray uses a modified DocBook DTD and a checkbook example throughout, introducing concepts in early chapters and adding new concepts to them. Readers become familiar with the code and its evolution through repeated exposure. The code for converting the "barebones DocBook" DTD (10 pages of code) to HTML via XSLT stylesheet occupies 19 pages. Both code examples allow the learner to sec an accumulation of snippets incorporated into a sensible whole. While experienced programmers might not need this type of support, nonprogrammers certainly do. Using the checkbook example is an inspired choice: Most of us are familiar with personal checking, even if few of us world build an XML application for it. Learning XML is an excellent textbook. I've used it for several years as a recommended text for adult continuing education courses and workshops."
  16. Learning XML (2003) 0.00 
    0.003692802 = product of:
  0.012924806 = sum of:
    0.007483072 = product of:
      0.014966144 = sum of:
        0.014966144 = weight(_text_:p in 3101) [ClassicSimilarity], result of:
          0.014966144 = score(doc=3101,freq=4.0), product of:
            0.13319843 = queryWeight, product of:
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.03704574 = queryNorm
            0.11235977 = fieldWeight in 3101, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.015625 = fieldNorm(doc=3101)
      0.5 = coord(1/2)
    0.005441734 = weight(_text_:a in 3101) [ClassicSimilarity], result of:
      0.005441734 = score(doc=3101,freq=50.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.1273949 = fieldWeight in 3101, product of:
          7.071068 = tf(freq=50.0), with freq of:
            50.0 = termFreq=50.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.015625 = fieldNorm(doc=3101)
  0.2857143 = coord(2/7)
    Footnote
    Rez. in: JASIST 55(2004) no.14, S.1304-1305 (Z. Holbrooks):"The eXtensible Markup Language (XML) and its family of enabling technologies (XPath, XPointer, XLink, XSLT, et al.) were the new "new thing" only a couple of years ago. Happily, XML is now a W3C standard, and its enabling technologies are rapidly proliferating and maturing. Together, they are changing the way data is handled an the Web, how legacy data is accessed and leveraged in corporate archives, and offering the Semantic Web community a powerful toolset. Library and information professionals need a basic understanding of what XML is, and what its impacts will be an the library community as content vendors and publishers convert to the new standards. Norman Desmarais aims to provide librarians with an overview of XML and some potential library applications. The ABCs of XML contains the useful basic information that most general XML works cover. It is addressed to librarians, as evidenced by the occasional reference to periodical vendors, MARC, and OPACs. However, librarians without SGML, HTML, database, or programming experience may find the work daunting. The snippets of code-most incomplete and unattended by screenshots to illustrate the result of the code's execution-obscure more often than they enlighten. A single code sample (p. 91, a book purchase order) is immediately recognizable and sensible. There are no figures, illustrations, or screenshots. Subsection headings are used conservatively. Readers are confronted with page after page of unbroken technical text, and occasionally oddly formatted text (in some of the code samples). The author concentrates an commercial products and projects. Library and agency initiatives-for example, the National Institutes of Health HL-7 and U.S. Department of Education's GEM project-are notable for their absence. The Library of Congress USMARC to SGML effort is discussed in chapter 1, which covers the relationship of XML to its parent SGML, the XML processor, and data type definitions, using MARC as its illustrative example. Chapter 3 addresses the stylesheet options for XML, including DSSSL, CSS, and XSL. The Document Style Semantics and Specification Language (DSSSL) was created for use with SGML, and pruned into DSSSL-Lite and further (DSSSL-online). Cascading Style Sheets (CSS) were created for use with HTML. Extensible Style Language (XSL) is a further revision (and extension) of DSSSL-o specifically for use with XML. Discussion of aural stylesheets and Synchronized Multimedia Integration Language (SMIL) round out the chapter.
    Chapter 4 introduces XML internal and external pointing and linking technologies. XML Link Language (XLL, now XLink) provides unidirectional, multi-ended, and typed linking. XPointer, used with XLink, provides addressing into the interior of XML documents. XPath operates an the logical structure of an XML document, creating a tree of nodes. Used with both XPointer and XSLT, it permits operations an strings, numbers, and Boolean expressions in the document. The final chapter, "Getting Started" argues for the adoption of a tool for XML production. The features and functionality of various tools for content development, application development, databases, and schema development provide an introduction to some of the available options. Roy Tennant is weIl known in the library community as an author (bis column "Digital Libraries" has appeared in Library Journal since 1997 and he has published Current Cites each month for more than a decade), an electronic discussion list manager (Web4Lib and XML4Lib), and as the creator and manager of UC/Berkeley's Digital Library SunSITE. Librarians have wondered what use they might make of XML since its beginnings. Tennant suggests one answer: "The Extensible Markup Language (XML) has the potential to exceed the impact of MARC an librarianship. While MARC is limited to bibliographic descriptionand arguably a subset at that, as any archivist will tell you-XML provides a highly-effective framework for encoding anything from a bibliographic record for a book to the book itself." (Tennant, p. vii) This slim paperback volume offers librarians and library managers concerned with automation projects "show and teIl" examples of XML technologies used as solutions to everyday tasks and challenges. What distinguishes this work is the editor and contributors' commitment to providing messy details. This book's target audience is technically savvy. While not a "cookbook" per se, the information provided an each project serves as a draft blueprint complete with acronyms and jargon. The inclusion of "lessons learned" (including failures as well as successes) is refreshing and commendable. Experienced IT and automation project veterans will appreciate the technical specifics more fully than the general reader.
    Tennant's collection covers a variety of well- and lesser-known XML-based pilot and prototype projects undertaken by libraries around the world. Some of the projects included are: Stanford's XMLMARC conversion, Oregon State's use of XML in interlibrary loaning, e-books (California Digital Library) and electronic scholarly publishing (University of Michigan), the Washington Research Library Consortium's XML-based Web Services, and using TEI Lite to support indexing (Halton Hills Public Library). Of the 13 projects presented, nine are sited in academe, three are state library endeavors, and one is an American public library initiative. The projects are gathered into sections grouped by seven library applications: the use of XML in library catalog records, interlibrary loan, cataloging and indexing, collection building, databases, data migration, and systems interoperability. Each project is introduced with a few paragraphs of background information. The project reports-averaging about 13 pages each-include project goals and justification, project description, challenges and lessons learned (successes and failures), future plans, implications of the work, contact information for individual(s) responsible for the project, and relevant Web links and resources. The clear strengths of this collection are in the details and the consistency of presentation. The concise project write-ups flow well and encourage interested readers to follow-up via personal contacts and URLs. The sole weakness is the price. XML in Libraries will excite and inspire institutions and organizations with technically adept staff resources and visionary leaders. Erik Ray has written a how-to book. Unlike most, Learning XML is not aimed at the professional programming community. The intended audience is readers familiar with a structured markup (HTML, TEX, etc.) and Web concepts (hypertext links, data representation). In the first six chapters, Ray introduces XMUs main concepts and tools for writing, viewing, testing, and transforming XML (chapter 1), describes basic syntax (chapter 2), discusses linking with XLink and XPointer (chapter 3), introduces Cascading Style Sheets for use with XML (chapter 4), explains document type definitions (DTDs) and schemas (chapter 5), and covers XSLT stylesheets and XPath (chapter 6). Chapter 7 introduces Unicode, internationalization and language support, including CSS and XSLT encoding. Chapter 8 is an overview of writing software for processing XML, and includes the Perl code for an XML syntax checker. This work is written very accessibly for nonprogrammers. Writers, designers, and students just starting to acquire Web technology skills will find Ray's style approachable. Concepts are introduced in a logical flow, and explained clearly. Code samples (130+), illustrations and screen shots (50+), and numerous tables are distributed throughout the text. Ray uses a modified DocBook DTD and a checkbook example throughout, introducing concepts in early chapters and adding new concepts to them. Readers become familiar with the code and its evolution through repeated exposure. The code for converting the "barebones DocBook" DTD (10 pages of code) to HTML via XSLT stylesheet occupies 19 pages. Both code examples allow the learner to sec an accumulation of snippets incorporated into a sensible whole. While experienced programmers might not need this type of support, nonprogrammers certainly do. Using the checkbook example is an inspired choice: Most of us are familiar with personal checking, even if few of us world build an XML application for it. Learning XML is an excellent textbook. I've used it for several years as a recommended text for adult continuing education courses and workshops."
  17. ¬The ABCs of XML : the librarian's guide to the eXtensible Markup Language (2000) 0.00 
    0.003692802 = product of:
  0.012924806 = sum of:
    0.007483072 = product of:
      0.014966144 = sum of:
        0.014966144 = weight(_text_:p in 3102) [ClassicSimilarity], result of:
          0.014966144 = score(doc=3102,freq=4.0), product of:
            0.13319843 = queryWeight, product of:
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.03704574 = queryNorm
            0.11235977 = fieldWeight in 3102, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.015625 = fieldNorm(doc=3102)
      0.5 = coord(1/2)
    0.005441734 = weight(_text_:a in 3102) [ClassicSimilarity], result of:
      0.005441734 = score(doc=3102,freq=50.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.1273949 = fieldWeight in 3102, product of:
          7.071068 = tf(freq=50.0), with freq of:
            50.0 = termFreq=50.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.015625 = fieldNorm(doc=3102)
  0.2857143 = coord(2/7)
    Footnote
    Rez. in: JASIST 55(2004) no.14, S.1304-1305 (Z. Holbrooks):"The eXtensible Markup Language (XML) and its family of enabling technologies (XPath, XPointer, XLink, XSLT, et al.) were the new "new thing" only a couple of years ago. Happily, XML is now a W3C standard, and its enabling technologies are rapidly proliferating and maturing. Together, they are changing the way data is handled an the Web, how legacy data is accessed and leveraged in corporate archives, and offering the Semantic Web community a powerful toolset. Library and information professionals need a basic understanding of what XML is, and what its impacts will be an the library community as content vendors and publishers convert to the new standards. Norman Desmarais aims to provide librarians with an overview of XML and some potential library applications. The ABCs of XML contains the useful basic information that most general XML works cover. It is addressed to librarians, as evidenced by the occasional reference to periodical vendors, MARC, and OPACs. However, librarians without SGML, HTML, database, or programming experience may find the work daunting. The snippets of code-most incomplete and unattended by screenshots to illustrate the result of the code's execution-obscure more often than they enlighten. A single code sample (p. 91, a book purchase order) is immediately recognizable and sensible. There are no figures, illustrations, or screenshots. Subsection headings are used conservatively. Readers are confronted with page after page of unbroken technical text, and occasionally oddly formatted text (in some of the code samples). The author concentrates an commercial products and projects. Library and agency initiatives-for example, the National Institutes of Health HL-7 and U.S. Department of Education's GEM project-are notable for their absence. The Library of Congress USMARC to SGML effort is discussed in chapter 1, which covers the relationship of XML to its parent SGML, the XML processor, and data type definitions, using MARC as its illustrative example. Chapter 3 addresses the stylesheet options for XML, including DSSSL, CSS, and XSL. The Document Style Semantics and Specification Language (DSSSL) was created for use with SGML, and pruned into DSSSL-Lite and further (DSSSL-online). Cascading Style Sheets (CSS) were created for use with HTML. Extensible Style Language (XSL) is a further revision (and extension) of DSSSL-o specifically for use with XML. Discussion of aural stylesheets and Synchronized Multimedia Integration Language (SMIL) round out the chapter.
    Chapter 4 introduces XML internal and external pointing and linking technologies. XML Link Language (XLL, now XLink) provides unidirectional, multi-ended, and typed linking. XPointer, used with XLink, provides addressing into the interior of XML documents. XPath operates an the logical structure of an XML document, creating a tree of nodes. Used with both XPointer and XSLT, it permits operations an strings, numbers, and Boolean expressions in the document. The final chapter, "Getting Started" argues for the adoption of a tool for XML production. The features and functionality of various tools for content development, application development, databases, and schema development provide an introduction to some of the available options. Roy Tennant is weIl known in the library community as an author (bis column "Digital Libraries" has appeared in Library Journal since 1997 and he has published Current Cites each month for more than a decade), an electronic discussion list manager (Web4Lib and XML4Lib), and as the creator and manager of UC/Berkeley's Digital Library SunSITE. Librarians have wondered what use they might make of XML since its beginnings. Tennant suggests one answer: "The Extensible Markup Language (XML) has the potential to exceed the impact of MARC an librarianship. While MARC is limited to bibliographic descriptionand arguably a subset at that, as any archivist will tell you-XML provides a highly-effective framework for encoding anything from a bibliographic record for a book to the book itself." (Tennant, p. vii) This slim paperback volume offers librarians and library managers concerned with automation projects "show and teIl" examples of XML technologies used as solutions to everyday tasks and challenges. What distinguishes this work is the editor and contributors' commitment to providing messy details. This book's target audience is technically savvy. While not a "cookbook" per se, the information provided an each project serves as a draft blueprint complete with acronyms and jargon. The inclusion of "lessons learned" (including failures as well as successes) is refreshing and commendable. Experienced IT and automation project veterans will appreciate the technical specifics more fully than the general reader.
    Tennant's collection covers a variety of well- and lesser-known XML-based pilot and prototype projects undertaken by libraries around the world. Some of the projects included are: Stanford's XMLMARC conversion, Oregon State's use of XML in interlibrary loaning, e-books (California Digital Library) and electronic scholarly publishing (University of Michigan), the Washington Research Library Consortium's XML-based Web Services, and using TEI Lite to support indexing (Halton Hills Public Library). Of the 13 projects presented, nine are sited in academe, three are state library endeavors, and one is an American public library initiative. The projects are gathered into sections grouped by seven library applications: the use of XML in library catalog records, interlibrary loan, cataloging and indexing, collection building, databases, data migration, and systems interoperability. Each project is introduced with a few paragraphs of background information. The project reports-averaging about 13 pages each-include project goals and justification, project description, challenges and lessons learned (successes and failures), future plans, implications of the work, contact information for individual(s) responsible for the project, and relevant Web links and resources. The clear strengths of this collection are in the details and the consistency of presentation. The concise project write-ups flow well and encourage interested readers to follow-up via personal contacts and URLs. The sole weakness is the price. XML in Libraries will excite and inspire institutions and organizations with technically adept staff resources and visionary leaders. Erik Ray has written a how-to book. Unlike most, Learning XML is not aimed at the professional programming community. The intended audience is readers familiar with a structured markup (HTML, TEX, etc.) and Web concepts (hypertext links, data representation). In the first six chapters, Ray introduces XMUs main concepts and tools for writing, viewing, testing, and transforming XML (chapter 1), describes basic syntax (chapter 2), discusses linking with XLink and XPointer (chapter 3), introduces Cascading Style Sheets for use with XML (chapter 4), explains document type definitions (DTDs) and schemas (chapter 5), and covers XSLT stylesheets and XPath (chapter 6). Chapter 7 introduces Unicode, internationalization and language support, including CSS and XSLT encoding. Chapter 8 is an overview of writing software for processing XML, and includes the Perl code for an XML syntax checker. This work is written very accessibly for nonprogrammers. Writers, designers, and students just starting to acquire Web technology skills will find Ray's style approachable. Concepts are introduced in a logical flow, and explained clearly. Code samples (130+), illustrations and screen shots (50+), and numerous tables are distributed throughout the text. Ray uses a modified DocBook DTD and a checkbook example throughout, introducing concepts in early chapters and adding new concepts to them. Readers become familiar with the code and its evolution through repeated exposure. The code for converting the "barebones DocBook" DTD (10 pages of code) to HTML via XSLT stylesheet occupies 19 pages. Both code examples allow the learner to sec an accumulation of snippets incorporated into a sensible whole. While experienced programmers might not need this type of support, nonprogrammers certainly do. Using the checkbook example is an inspired choice: Most of us are familiar with personal checking, even if few of us world build an XML application for it. Learning XML is an excellent textbook. I've used it for several years as a recommended text for adult continuing education courses and workshops."
  18. Lee, M.; Baillie, S.; Dell'Oro, J.: TML: a Thesaural Markpup Language (200?) 0.00 
    0.0013993031 = product of:
  0.009795121 = sum of:
    0.009795121 = weight(_text_:a in 1622) [ClassicSimilarity], result of:
      0.009795121 = score(doc=1622,freq=18.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.22931081 = fieldWeight in 1622, product of:
          4.2426405 = tf(freq=18.0), with freq of:
            18.0 = termFreq=18.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=1622)
  0.14285715 = coord(1/7)
    Abstract
    Thesauri are used to provide controlled vocabularies for resource classification. Their use can greatly assist document discovery because thesauri man date a consistent shared terminology for describing documents. A particular thesauras classifies documents according to an information community's needs. As a result, there are many different thesaural schemas. This has led to a proliferation of schema-specific thesaural systems. In our research, we exploit schematic regularities to design a generic thesaural ontology and specfiy it as a markup language. The language provides a common representational framework in which to encode the idiosyncrasies of specific thesauri. This approach has several advantages: it offers consistent syntax and semantics in which to express thesauri; it allows general purpose thesaural applications to leverage many thesauri; and it supports a single thesaural user interface by which information communities can consistently organise, score and retrieve electronic documents.
  19. Chang, M.: ¬An electronic finding aid using extensible markup language (XML) and encoded archival description (EAD) (2000) 0.00 
    0.0012168088 = product of:
  0.008517661 = sum of:
    0.008517661 = weight(_text_:a in 4886) [ClassicSimilarity], result of:
      0.008517661 = score(doc=4886,freq=10.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.19940455 = fieldWeight in 4886, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4886)
  0.14285715 = coord(1/7)
    Abstract
    Increasingly, XML applications are appearing on the World Wide Web, from e-commerce to information management. In the case of libraries and archives, XML enables more flexible information management and retrieval than using MARC or a relational database management system. Describes a project to explore the use of XML and the EAD, and the development of a prototype electronic finding aid. It focuses on the technical aspects, and reviews the options available and the choices made. This is done within the setting of a small- to medium-sized archive with minimal tools and resources.
    Type
    a
  20. Miller, E.; Schloss. B.; Lassila, O.; Swick, R.R.: Resource Description Framework (RDF) : model and syntax (1997) 0.00 
    0.0011859986 = product of:
  0.008301989 = sum of:
    0.008301989 = weight(_text_:a in 5903) [ClassicSimilarity], result of:
      0.008301989 = score(doc=5903,freq=38.0), product of:
        0.04271548 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03704574 = queryNorm
        0.19435552 = fieldWeight in 5903, product of:
          6.164414 = tf(freq=38.0), with freq of:
            38.0 = termFreq=38.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.02734375 = fieldNorm(doc=5903)
  0.14285715 = coord(1/7)
    Abstract
    RDF - the Resource Description Framework - is a foundation for processing metadata; it provides interoperability between applications that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing of Web resources. RDF metadata can be used in a variety of application areas; for example: in resource discovery to provide better search engine capabilities; in cataloging for describing the content and content relationships available at a particular Web site, page, or digital library; by intelligent software agents to facilitate knowledge sharing and exchange; in content rating; in describing collections of pages that represent a single logical "document"; for describing intellectual property rights of Web pages, and in many others. RDF with digital signatures will be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications. Metadata is "data about data" or specifically in the context of RDF "data describing web resources." The distinction between "data" and "metadata" is not an absolute one; it is a distinction created primarily by a particular application. Many times the same resource will be interpreted in both ways simultaneously. RDF encourages this view by using XML as the encoding syntax for the metadata. The resources being described by RDF are, in general, anything that can be named via a URI. The broad goal of RDF is to define a mechanism for describing resources that makes no assumptions about a particular application domain, nor defines the semantics of any application domain. The definition of the mechanism should be domain neutral, yet the mechanism should be suitable for describing information about any domain. This document introduces a model for representing RDF metadata and one syntax for expressing and transporting this metadata in a manner that maximizes the interoperability of independently developed web servers and clients. The syntax described in this document is best considered as a "serialization syntax" for the underlying RDF representation model. The serialization syntax is XML, XML being the W3C's work-in-progress to define a richer Web syntax for a variety of applications. RDF and XML are complementary; there will be alternate ways to represent the same RDF data model, some more suitable for direct human authoring. Future work may lead to including such alternatives in this document.
    Content
    RDF Data Model At the core of RDF is a model for representing named properties and their values. These properties serve both to represent attributes of resources (and in this sense correspond to usual attribute-value-pairs) and to represent relationships between resources. The RDF data model is a syntax-independent way of representing RDF statements. RDF statements that are syntactically very different could mean the same thing. This concept of equivalence in meaning is very important when performing queries, aggregation and a number of other tasks at which RDF is aimed. The equivalence is defined in a clean machine understandable way. Two pieces of RDF are equivalent if and only if their corresponding data model representations are the same. Table of contents 1. Introduction 2. RDF Data Model 3. RDF Grammar 4. Signed RDF 5. Examples 6. Appendix A: Brief Explanation of XML Namespaces

Authors

Years

Languages

  • e 27
  • d 15

Types

  • a 24
  • m 12
  • el 7
  • n 2
  • s 2
  • x 1
  • More… Less…

Themes

Subjects

Classifications