Search (18 results, page 1 of 1)

  • × theme_ss:"Auszeichnungssprachen"
  1. Trotman, A.: Searching structured documents (2004) 0.04 
    0.039718952 = product of:
  0.079437904 = sum of:
    0.079437904 = sum of:
      0.029805588 = weight(_text_:4 in 2538) [ClassicSimilarity], result of:
        0.029805588 = score(doc=2538,freq=2.0), product of:
          0.14201462 = queryWeight, product of:
            2.7136984 = idf(docFreq=7967, maxDocs=44218)
            0.0523325 = queryNorm
          0.2098769 = fieldWeight in 2538, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            2.7136984 = idf(docFreq=7967, maxDocs=44218)
            0.0546875 = fieldNorm(doc=2538)
      0.04963232 = weight(_text_:22 in 2538) [ClassicSimilarity], result of:
        0.04963232 = score(doc=2538,freq=2.0), product of:
          0.1832595 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0523325 = 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)
    Date
    14. 8.2004 10:39:22
    Source
    Information processing and management. 40(2004) no.4, S.619-632
  2. Vonhoegen, H.: Einstieg in XML (2002) 0.02 
    0.019859476 = product of:
  0.039718952 = sum of:
    0.039718952 = sum of:
      0.014902794 = weight(_text_:4 in 4002) [ClassicSimilarity], result of:
        0.014902794 = score(doc=4002,freq=2.0), product of:
          0.14201462 = queryWeight, product of:
            2.7136984 = idf(docFreq=7967, maxDocs=44218)
            0.0523325 = queryNorm
          0.10493845 = fieldWeight in 4002, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            2.7136984 = idf(docFreq=7967, maxDocs=44218)
            0.02734375 = fieldNorm(doc=4002)
      0.02481616 = weight(_text_:22 in 4002) [ClassicSimilarity], result of:
        0.02481616 = score(doc=4002,freq=2.0), product of:
          0.1832595 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0523325 = 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)
    Date
    4. 4.2003 9:00:35
    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."
  3. as: XML: Extensible Markup Language : I: Was ist XML? (2001) 0.02 
    0.017725829 = product of:
  0.035451658 = sum of:
    0.035451658 = product of:
      0.070903316 = sum of:
        0.070903316 = weight(_text_:22 in 4950) [ClassicSimilarity], result of:
          0.070903316 = score(doc=4950,freq=2.0), product of:
            0.1832595 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0523325 = 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.5 = coord(1/2)
    Date
    30. 3.2003 11:06:22
  4. Thuraisingham, B.: XML databases and the semantic Web (2002) 0.01 
    0.014902794 = product of:
  0.029805588 = sum of:
    0.029805588 = product of:
      0.059611175 = sum of:
        0.059611175 = weight(_text_:4 in 3754) [ClassicSimilarity], result of:
          0.059611175 = score(doc=3754,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.4197538 = fieldWeight in 3754, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.109375 = fieldNorm(doc=3754)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Date
    4. 7.2006 17:06:14
  5. Schröder, A.: Web der Zukunft : RDF - Der erste Schritt zum semantischen Web 0.01 
    0.014180663 = product of:
  0.028361326 = sum of:
    0.028361326 = product of:
      0.056722652 = sum of:
        0.056722652 = weight(_text_:22 in 1457) [ClassicSimilarity], result of:
          0.056722652 = score(doc=1457,freq=2.0), product of:
            0.1832595 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0523325 = 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.5 = coord(1/2)
    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.
  6. Patrick, D.A.: XML in der Praxis : Unternehmensübergreifende Vorteile durch Enterprise Content Management (1999) 0.01 
    0.01240808 = product of:
  0.02481616 = sum of:
    0.02481616 = product of:
      0.04963232 = sum of:
        0.04963232 = weight(_text_:22 in 1461) [ClassicSimilarity], result of:
          0.04963232 = score(doc=1461,freq=2.0), product of:
            0.1832595 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0523325 = 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.5 = coord(1/2)
    Date
    30. 3.2003 10:50:22
  7. Bold, M.: ¬Die Zukunft des Web : Standards für das Web der Zukunft (2004) 0.01 
    0.010644853 = product of:
  0.021289706 = sum of:
    0.021289706 = product of:
      0.042579412 = sum of:
        0.042579412 = weight(_text_:4 in 1725) [ClassicSimilarity], result of:
          0.042579412 = score(doc=1725,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.29982415 = fieldWeight in 1725, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.078125 = fieldNorm(doc=1725)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Source
    Internet Professionell. 2004, H.4, S.32-36
  8. Ioannides, D.: XML schema languages : beyond DTD (2000) 0.01 
    0.010635497 = product of:
  0.021270994 = sum of:
    0.021270994 = product of:
      0.04254199 = sum of:
        0.04254199 = weight(_text_:22 in 720) [ClassicSimilarity], result of:
          0.04254199 = score(doc=720,freq=2.0), product of:
            0.1832595 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0523325 = 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.5 = coord(1/2)
    Date
    28. 1.2006 19:01:22
  9. Peis, E.; Moya, F. de; Fernández-Molina, J.C.: Encoded archival description (EAD) conversion : a methodological proposal (2000) 0.01 
    0.007451397 = product of:
  0.014902794 = sum of:
    0.014902794 = product of:
      0.029805588 = sum of:
        0.029805588 = weight(_text_:4 in 4899) [ClassicSimilarity], result of:
          0.029805588 = score(doc=4899,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.2098769 = fieldWeight in 4899, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4899)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Source
    Library hi tech. 18(2000) no.4, S.360-368
  10. Christophides, V.; Plexousakis, D.; Scholl, M.; Tourtounis, S.: On labeling schemes for the Semantic Web (2003) 0.01 
    0.0063869115 = product of:
  0.012773823 = sum of:
    0.012773823 = product of:
      0.025547646 = sum of:
        0.025547646 = weight(_text_:4 in 3393) [ClassicSimilarity], result of:
          0.025547646 = score(doc=3393,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.17989448 = fieldWeight in 3393, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.046875 = fieldNorm(doc=3393)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Date
    4. 7.1997 18:38:23
  11. Jackenkroll, M.: Sprache mit Potenzial : XML als Grundlage des Cross-Media-Publishing (2006) 0.01 
    0.0053224266 = product of:
  0.010644853 = sum of:
    0.010644853 = product of:
      0.021289706 = sum of:
        0.021289706 = weight(_text_:4 in 1629) [ClassicSimilarity], result of:
          0.021289706 = score(doc=1629,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.14991207 = fieldWeight in 1629, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1629)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Isbn
    978-3-86550-267-4
  12. 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.0053177485 = product of:
  0.010635497 = sum of:
    0.010635497 = product of:
      0.021270994 = sum of:
        0.021270994 = weight(_text_:22 in 729) [ClassicSimilarity], result of:
          0.021270994 = score(doc=729,freq=2.0), product of:
            0.1832595 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0523325 = 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.5 = coord(1/2)
    Date
    22. 6.2005 15:12:11
  13. Learning XML : [creating self describing data] (2001) 0.00 
    0.004257941 = product of:
  0.008515882 = sum of:
    0.008515882 = product of:
      0.017031765 = sum of:
        0.017031765 = weight(_text_:4 in 1744) [ClassicSimilarity], result of:
          0.017031765 = score(doc=1744,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.11992966 = fieldWeight in 1744, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.03125 = fieldNorm(doc=1744)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Isbn
    0-596-00046-4
  14. Miller, E.; Schloss. B.; Lassila, O.; Swick, R.R.: Resource Description Framework (RDF) : model and syntax (1997) 0.00 
    0.0037256985 = product of:
  0.007451397 = sum of:
    0.007451397 = product of:
      0.014902794 = sum of:
        0.014902794 = weight(_text_:4 in 5903) [ClassicSimilarity], result of:
          0.014902794 = score(doc=5903,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.10493845 = fieldWeight in 5903, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.02734375 = fieldNorm(doc=5903)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    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
  15. Jackenkroll, M.: Nutzen von XML für die Herstellung verschiedener medialer Varianten von Informationsmitteln : dargestellt am Beispiel eines geografischen Lexikonartikels (2002) 0.00 
    0.0031934557 = product of:
  0.0063869115 = sum of:
    0.0063869115 = product of:
      0.012773823 = sum of:
        0.012773823 = weight(_text_:4 in 4804) [ClassicSimilarity], result of:
          0.012773823 = score(doc=4804,freq=2.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.08994724 = fieldWeight in 4804, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0234375 = fieldNorm(doc=4804)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Content
    Das folgende Kapitel (Kapitel 3) der Arbeit beschäftigt sich mit dem Themenkomplex der Informationsmittel. Hier soll herausgearbeitet werden, welche Typen von Informationsmitteln es gibt und inwieweit sich elektronische und gedruckte Informationsmittel unterscheiden. Schwerpunktmäßig soll in diesem Teil aber dargestellt werden, wie XML und die ihr verwandte, aber komplexere Metaauszeichnungssprache SGML in Verlagen zur Publikation von Informationsmitteln eingesetzt werden, welche Vorteile eine derartige Auszeichnung der Daten mit sich bringt und an welchen Stellen Probleme auftauchen. Nach dem theoretischen Teil soll im weiteren Verlauf der Arbeit (Kapitel 4) die zuvor erläuterte Vorgehensweise an einem Beispiel demonstriert und in die Praxis umgesetzt werden. Anhand eines geografischen Lexikonartikels soll gezeigt werden, wie sich eine DTD entwickeln lässt, welche die Charakteristika dieses Dokumenttyps widerspiegelt und wie verschiedene Stylesheets eingesetzt werden können, um aus dem einmal erfassten Inhalt verschiedene Ausgabeprodukte zu erzeugen. Das entworfene XML-Dokument soll in diesem Fall als HTML-Dokument, als PDF-Dokument und als leicht verändertes XML-Dokument ausgegeben werden."
  16. XML in libraries (2002) 0.00 
    0.0030108192 = product of:
  0.0060216384 = sum of:
    0.0060216384 = product of:
      0.012043277 = sum of:
        0.012043277 = weight(_text_:4 in 3100) [ClassicSimilarity], result of:
          0.012043277 = score(doc=3100,freq=4.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.084803075 = fieldWeight in 3100, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.015625 = fieldNorm(doc=3100)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Footnote
    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. Learning XML (2003) 0.00 
    0.0030108192 = product of:
  0.0060216384 = sum of:
    0.0060216384 = product of:
      0.012043277 = sum of:
        0.012043277 = weight(_text_:4 in 3101) [ClassicSimilarity], result of:
          0.012043277 = score(doc=3101,freq=4.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.084803075 = fieldWeight in 3101, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.015625 = fieldNorm(doc=3101)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Footnote
    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. ¬The ABCs of XML : the librarian's guide to the eXtensible Markup Language (2000) 0.00 
    0.0030108192 = product of:
  0.0060216384 = sum of:
    0.0060216384 = product of:
      0.012043277 = sum of:
        0.012043277 = weight(_text_:4 in 3102) [ClassicSimilarity], result of:
          0.012043277 = score(doc=3102,freq=4.0), product of:
            0.14201462 = queryWeight, product of:
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.0523325 = queryNorm
            0.084803075 = fieldWeight in 3102, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              2.7136984 = idf(docFreq=7967, maxDocs=44218)
              0.015625 = fieldNorm(doc=3102)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Footnote
    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."

Authors

Years

Languages

  • e 10
  • d 8

Types

Themes

Subjects

Classifications