Search (17 results, page 1 of 1)

  • × theme_ss:"Auszeichnungssprachen"
  1. Schröder, A.: Web der Zukunft : RDF - Der erste Schritt zum semantischen Web 0.03
    0.033915933 = product of:
      0.084789835 = sum of:
        0.02796361 = weight(_text_:1 in 1457) [ClassicSimilarity], result of:
          0.02796361 = score(doc=1457,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.2171262 = fieldWeight in 1457, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0625 = fieldNorm(doc=1457)
        0.056826223 = weight(_text_:22 in 1457) [ClassicSimilarity], result of:
          0.056826223 = score(doc=1457,freq=2.0), product of:
            0.18359412 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052428056 = 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.4 = coord(2/5)
    
    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.
    Source
    XML Magazin und Web Services. 2003, H.1, S.40-43
  2. Patrick, D.A.: XML in der Praxis : Unternehmensübergreifende Vorteile durch Enterprise Content Management (1999) 0.03
    0.029676441 = product of:
      0.0741911 = sum of:
        0.02446816 = weight(_text_:1 in 1461) [ClassicSimilarity], result of:
          0.02446816 = score(doc=1461,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.18998542 = fieldWeight in 1461, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1461)
        0.049722943 = weight(_text_:22 in 1461) [ClassicSimilarity], result of:
          0.049722943 = score(doc=1461,freq=2.0), product of:
            0.18359412 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052428056 = 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.4 = coord(2/5)
    
    Date
    30. 3.2003 10:50:22
    Source
    nfd Information - Wissenschaft und Praxis. 50(1999) H.1, S.5-12
  3. Ioannides, D.: XML schema languages : beyond DTD (2000) 0.03
    0.02543695 = product of:
      0.063592374 = sum of:
        0.020972708 = weight(_text_:1 in 720) [ClassicSimilarity], result of:
          0.020972708 = score(doc=720,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.16284466 = fieldWeight in 720, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=720)
        0.042619668 = weight(_text_:22 in 720) [ClassicSimilarity], result of:
          0.042619668 = score(doc=720,freq=2.0), product of:
            0.18359412 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052428056 = 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.4 = coord(2/5)
    
    Date
    28. 1.2006 19:01:22
    Source
    Library hi tech. 18(2000) no.1, S.9-15
  4. Vonhoegen, H.: Einstieg in XML (2002) 0.01
    0.014838221 = product of:
      0.03709555 = sum of:
        0.01223408 = weight(_text_:1 in 4002) [ClassicSimilarity], result of:
          0.01223408 = score(doc=4002,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.09499271 = fieldWeight in 4002, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.02734375 = fieldNorm(doc=4002)
        0.024861472 = weight(_text_:22 in 4002) [ClassicSimilarity], result of:
          0.024861472 = score(doc=4002,freq=2.0), product of:
            0.18359412 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052428056 = 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.4 = coord(2/5)
    
    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."
  5. as: XML: Extensible Markup Language : I: Was ist XML? (2001) 0.01
    0.014206556 = product of:
      0.07103278 = sum of:
        0.07103278 = weight(_text_:22 in 4950) [ClassicSimilarity], result of:
          0.07103278 = score(doc=4950,freq=2.0), product of:
            0.18359412 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052428056 = 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.2 = coord(1/5)
    
    Date
    30. 3.2003 11:06:22
  6. 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.012718475 = product of:
      0.031796187 = sum of:
        0.010486354 = weight(_text_:1 in 729) [ClassicSimilarity], result of:
          0.010486354 = score(doc=729,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.08142233 = fieldWeight in 729, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0234375 = fieldNorm(doc=729)
        0.021309834 = weight(_text_:22 in 729) [ClassicSimilarity], result of:
          0.021309834 = score(doc=729,freq=2.0), product of:
            0.18359412 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052428056 = 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.4 = coord(2/5)
    
    Abstract
    Das erworbene Wissen sollte sich dann auch auf jedem anderen Betriebssystem umsetzen lassen. Jedes einzelne Kapitel wird sich mit einem bestimmten XML Thema beschäftigen. Kapitel 1 bietet eine Einführung in die Konzepte von XML. Kapitel 2 und 3 sind eng verknüpft, da sie fundamentale Grundlagen behandeln. Kapitel 2 startet mit der Syntax und den grundlegenden Regeln von XML. Kapitel 3 führt dann weiter und stellt Werkzeuge zur Erstellung eigener, problembezogener XML-DTDs vor. Die verbleibenden Kapitel jedoch sind weitestgehend, im Bezug auf die vorgestellten Techniken und Technologien, in sich abgeschlossen. Die wichtigsten Kapitel werden durch ein verbindendes Beispiel zusammengehalten. Das Beispiel geht davon aus, dass ein Verleger seinen Bücher-Katalog mittels XML präsentieren will. Wir werden damit beginnen, Regeln für die Beschreibung von Büchern in einem Katalog festzulegen. Auf der Grundlage dieser Regeln werden wir dann zeigen, wie jede einzelne Technik uns dabei hilft, XML-Anwendungen zu erstellen. Sie werden sehen, wie dieser Katalog sich in ein Dokument umwandeln lässt, wie solche Dokumente manipuliert werden können und wie man aus Programmen heraus auf sie zugreifen kann. Wir werden auch zeigen, wie man die Inhalte der Dokumente für den Leser aufbereitet. Da solche Anwendungen in der Praxis nicht in einem Vakuum existieren, werden Sie auch sehen, wie XML-Anwendungen mit Datenbanken interagieren. Es werden sich verschiedene thematische Stränge durch das Buch ziehen, die wir im folgenden Abschnitt vorstellen möchten. Damit sollten Sie in der Lage sein, gezielt für Sie wichtige Themen herauszugreifen und andere Abschnitte auszulassen
    Date
    22. 6.2005 15:12:11
  7. Trotman, A.: Searching structured documents (2004) 0.01
    0.009944589 = product of:
      0.049722943 = sum of:
        0.049722943 = weight(_text_:22 in 2538) [ClassicSimilarity], result of:
          0.049722943 = score(doc=2538,freq=2.0), product of:
            0.18359412 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052428056 = 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.2 = coord(1/5)
    
    Date
    14. 8.2004 10:39:22
  8. Berliner XMLTage 2004 : 11.-13. Oktober 2004 in Berlin. Proceedings (2004) 0.01
    0.008389084 = product of:
      0.041945416 = sum of:
        0.041945416 = weight(_text_:1 in 4284) [ClassicSimilarity], result of:
          0.041945416 = score(doc=4284,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.32568932 = fieldWeight in 4284, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.09375 = fieldNorm(doc=4284)
      0.2 = coord(1/5)
    
    Date
    1. 3.2008 17:43:47
  9. Pharo, N.: ¬The effect of granularity and order in XML element retrieval (2008) 0.01
    0.005592722 = product of:
      0.02796361 = sum of:
        0.02796361 = weight(_text_:1 in 2118) [ClassicSimilarity], result of:
          0.02796361 = score(doc=2118,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.2171262 = fieldWeight in 2118, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0625 = fieldNorm(doc=2118)
      0.2 = coord(1/5)
    
    Date
    1. 8.2008 14:52:15
  10. Chang, M.: ¬An electronic finding aid using extensible markup language (XML) and encoded archival description (EAD) (2000) 0.00
    0.004893632 = product of:
      0.02446816 = sum of:
        0.02446816 = weight(_text_:1 in 4886) [ClassicSimilarity], result of:
          0.02446816 = score(doc=4886,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.18998542 = fieldWeight in 4886, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4886)
      0.2 = coord(1/5)
    
    Source
    Library hi tech. 18(2000) no.1, S.15-27
  11. Christophides, V.; Plexousakis, D.; Scholl, M.; Tourtounis, S.: On labeling schemes for the Semantic Web (2003) 0.00
    0.004194542 = product of:
      0.020972708 = sum of:
        0.020972708 = weight(_text_:1 in 3393) [ClassicSimilarity], result of:
          0.020972708 = score(doc=3393,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.16284466 = fieldWeight in 3393, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=3393)
      0.2 = coord(1/5)
    
    Abstract
    This paper focuses on the optimization of the navigation through voluminous subsumption hierarchies of topics employed by Portal Catalogs like Netscape Open Directory (ODP). We advocate for the use of labeling schemes for modeling these hierarchies in order to efficiently answer queries such as subsumption check, descendants, ancestors or nearest common ancestor, which usually require costly transitive closure computations. We first give a qualitative comparison of three main families of schemes, namely bit vector, prefix and interval based schemes. We then show that two labeling schemes are good candidates for an efficient implementation of label querying using standard relational DBMS, namely, the Dewey Prefix scheme [6] and an Interval scheme by Agrawal, Borgida and Jagadish [1]. We compare their storage and query evaluation performance for the 16 ODP hierarchies using the PostgreSQL engine.
  12. Barthelmes, C.: Darstellungsmöglichkeiten von Musik mithilfe ausgewählter Musikbeschreibungssprachen (2003) 0.00
    0.0034954515 = product of:
      0.017477257 = sum of:
        0.017477257 = weight(_text_:1 in 1831) [ClassicSimilarity], result of:
          0.017477257 = score(doc=1831,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.13570388 = fieldWeight in 1831, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1831)
      0.2 = coord(1/5)
    
    Abstract
    Musik wird in ihrer klanglichen und teilweise sogar in ihrer visuellen Gestalt (Notenbild) bereits elektronisch festgehalten. Meist handelt es sich jedoch um Klangformate wie wav, au oder midi bzw. um Bilddateien wie jpeg oder gif. Diese lassen sich abspielen bzw. betrachten, aber sie lassen keine gezielten Interaktionen oder Recherchen innerhalb des Materials zu. Die Herausforderung besteht darin, durch Zugriff auf die einzelnen musikbezogenen Elemente und die Potenz ihrer Veränderbarkeit Möglichkeiten der Datengestaltung und vielfältigen Datennutzung bereitzustellen. Könnten nicht sämtliche notwendigen musikrelevanten Informationen in einem Datenformat so gespeichert werden, dass je nach Zielsetzung Notenbilder oder Klänge erzeugt oder dass einzelne Motive gefunden oder musikalische Zusammenhänge entdeckt werden können? Mit verschiedenen Musikbeschreibungssprachen soll dies erreicht werden. Welche Parameter müssen oder sollten als musikrelevantes Material Berücksichtigung finden? Der erste Teil (1.) wird verdeutlichen, welche Schwierigkeiten sich hier auftun. Danach soll ein Überblick (2.) zeigen, welche Zielvorstellungen bisherige Formate verfolgen. In den letzten 30 Jahren entstand eine Vielzahl von Formaten (insgesamt etwa 100). Dennoch ist die Entwicklung längst nicht abgeschlossen, und die Speicher- und Präsentationsmöglichkeiten der Musikbibliotheken, -dokumentationen und -archive nutzen diese Potenziale noch nicht. Für eine dokumentarische Nutzung solcher Musikbeschreibungen sind zudem verschiedene Voraussetzungen zu erfüllen. Gemessen am aufgestellten Maßstab sind für den Bibliotheks- und Dokumentationsbereich nur noch einige brauchbar. Ausgehend von einer weltumspannenden, aktuellen Forschung bei gleichzeitig offensichtlich geringer Präsenz von deutschen Spezialisten der Information und Dokumentation will dieser Beitrag eine Orientierung zur aktiven Mitgestaltung dieses Gebiets ermöglichen.
  13. ¬The ABCs of XML : the librarian's guide to the eXtensible Markup Language (2000) 0.00
    0.0031264268 = product of:
      0.015632134 = sum of:
        0.015632134 = weight(_text_:1 in 3102) [ClassicSimilarity], result of:
          0.015632134 = score(doc=3102,freq=10.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.121377245 = fieldWeight in 3102, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.015625 = fieldNorm(doc=3102)
      0.2 = coord(1/5)
    
    Content
    Sammelrezension mit: (1) Tennant, R. (Hrsg.): XML in libraries. New York: Neal-Schuman 2002. XI, 212 S. ISBN 1-55570-443-3 (2) Learning XML. Erik T. Ray. Sebastopol, CA: O'Reilly & Associates, 2003. 400 pp. $34.95. (ISBN: 0-596-00420-6)
    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.
    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."
    Weitere Rez in: Electronic library 19(2001) no.1, S.51-52 (M. Keary)
  14. XML in libraries (2002) 0.00
    0.002796361 = product of:
      0.013981805 = sum of:
        0.013981805 = weight(_text_:1 in 3100) [ClassicSimilarity], result of:
          0.013981805 = score(doc=3100,freq=8.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.1085631 = fieldWeight in 3100, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.015625 = fieldNorm(doc=3100)
      0.2 = coord(1/5)
    
    Content
    Sammelrezension mit: (1) The ABCs of XML: The Librarian's Guide to the eXtensible Markup Language. Norman Desmarais. Houston, TX: New Technology Press, 2000. 206 pp. $28.00. (ISBN: 0-9675942-0-0) und (2) Learning XML. Erik T. Ray. Sebastopol, CA: O'Reilly & Associates, 2003. 400 pp. $34.95. (ISBN: 0-596-00420-6)
    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.
    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."
    Isbn
    1-55570-443-3
  15. Learning XML (2003) 0.00
    0.002796361 = product of:
      0.013981805 = sum of:
        0.013981805 = weight(_text_:1 in 3101) [ClassicSimilarity], result of:
          0.013981805 = score(doc=3101,freq=8.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.1085631 = fieldWeight in 3101, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.015625 = fieldNorm(doc=3101)
      0.2 = coord(1/5)
    
    Content
    Sammelrezension mit: (1) Tennant, R. (Hrsg.): XML in libraries. New York: Neal-Schuman 2002. XI, 212 S. ISBN 1-55570-443-3 (2) Desmarais, N. (Hrsg.): The ABCs of XML: the librarian's guide to the eXtensible Markup Language. Houston, TX: New Technology Press 2000. XI, 212 S. ISBN 0-9675942-0-0 * 0-85604-374-6
    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.
    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. XML & Co : Die W3C-Spezifikationen für Dokumenten- und Datenarchitektur (2002) 0.00
    0.002796361 = product of:
      0.013981805 = sum of:
        0.013981805 = weight(_text_:1 in 197) [ClassicSimilarity], result of:
          0.013981805 = score(doc=197,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.1085631 = fieldWeight in 197, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.03125 = fieldNorm(doc=197)
      0.2 = coord(1/5)
    
    Footnote
    Rez. in: XML Magazin und Web Services 2003, H.1, S.13 (T. Weitzel): "Die Standards der XML-Familie sind nun auch in deutscher Übersetzung und Kommentierung verfügbar. Unter der Leitung von Stefan Mintert, der 1998 bereits die XML-Spezifikation selbst übersetzte, ist zusammen mit einem Team namhafter XML-Spezialisten und mit Unterstützung des deutsch-österreichischen W3C-Büros eine Sammlung aller wichtigen Specs aus der XML-Familie bei Addison-Wesley erschienen. Genauer gesagt handelt es sich um die kommentierten und übersetzten Versionen der Standards aus der W3C Activity Domain Architecture/XML, und zwar, in chronologischer Reihenfolge, XML, Namensräume, Verknüpfen von Stylesheets mit XML-Dokumenten, XPath, XSLT, XML Schema 0-3 (Einführung, Strukturen und Datentypen), XLink, XML Base und XML Information Set. Ziel des Projekts "edition W3C" war es, den Inhalt der jeweiligen Spezifikationen besser verständlich zu machen und so auch einen Beitrag zur Verbreitung der Standards zu leisten. Daher liegen die Übersetzungen nicht nur in Buchform vor, sondern sind sie über das normative Original hinaus in unterschiedlichem Umfang durch die jeweiligen Experten kommentiert. Insbesondere XPath ist so ausführlich und liebevoll mit vielen Erläuterungen und Abbildungen versehen, dass eine analoge Behandlung etwa der Schema-Specs sicherlich den Rahmen des Buchs gesprengt hätte. Das erhoffte Feedback auf die unterschiedlichen Übersetzungen und Kommentierungen soll helfen, das geplante zweite Buch der edition W3C-Reihe zu XHTML und CSS an den Leserwünschen auszurichten. Interessant ist, dass das Buch selbst in XML erstellt wurde (XMLspec-DTD). Wie schon in "XML in der Praxis" (zusammen mit Henning Behme) hat Stefan Mintert für die edition W3C in lehrbuchmäßiger Cross-Media-Manier XML eingesetzt. So konnte beispielsweise das Stichwortverzeichnis (www.edition-w3c.de/ gesamtindex.html) direkt per Single Source aus den jeweiligen Spezifikationen generiert werden. Eine Besonderheit des 1999 initiierten Projekts liegt darin, dass es sich um die einzige durch das W3C legitimierte PrintPublikation überhaupt handelt, nachdem 1997 das WWW Journal (W3J) bei O'Reilly eingestellt wurde. Darüber hinaus ist die edition W3 C das einzige offizielle, also vom örtlichen W3C-Büro unterstützte, Übersetzungsprojekt. Bedenkt man, dass das W3C-neben Boston-Sitze in Frankreich und Japan hat, stellt sich die Frage, ob dort Übersetzungen nicht noch viel stärker nachgefragt werden könnten und somit auch zur weiteren Durchsetzung der XML-Familie beitragen könnten. Die Übersetzungen sind, allerdings ohne Kommentierungen, auch über die Website des Projekts bei www.edition-w3c.de/ verlinkt. Dort gibt es auch weitere Übersetzungen, etwa zu XHTML oder CSS L2."
  17. Miller, E.; Schloss. B.; Lassila, O.; Swick, R.R.: Resource Description Framework (RDF) : model and syntax (1997) 0.00
    0.002446816 = product of:
      0.01223408 = sum of:
        0.01223408 = weight(_text_:1 in 5903) [ClassicSimilarity], result of:
          0.01223408 = score(doc=5903,freq=2.0), product of:
            0.12878966 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.052428056 = queryNorm
            0.09499271 = fieldWeight in 5903, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.02734375 = fieldNorm(doc=5903)
      0.2 = coord(1/5)
    
    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