<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>02919cam a2200313 a 4500</leader>
  <controlfield tag="001">1/45320</controlfield>
  <controlfield tag="008">140822s2003    us            001 0 eng  </controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">0585448213 (electronic bk.)</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">9780585448213 (electronic bk.)</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">9781558607453</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">1558607455</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="l">48280</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">N$T</subfield>
   <subfield code="b">eng</subfield>
   <subfield code="c">N$T</subfield>
   <subfield code="d">OCLCQ</subfield>
   <subfield code="d">YDXCP</subfield>
   <subfield code="d">OCLCG</subfield>
   <subfield code="d">OCLCQ</subfield>
   <subfield code="d">TUU</subfield>
   <subfield code="d">OCLCQ</subfield>
   <subfield code="d">TNF</subfield>
   <subfield code="d">OCLCQ</subfield>
   <subfield code="d">OPELS</subfield>
   <subfield code="d">OKU</subfield>
   <subfield code="d">OCLCF</subfield>
   <subfield code="d">OCLCE</subfield>
   <subfield code="d">GR-PeUP</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Daum, Berthold,</subfield>
   <subfield code="d">1949-</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">System architecture with XML</subfield>
   <subfield code="h">[electronic resource] /</subfield>
   <subfield code="c">Berthold Daum, Udo Merten.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
   <subfield code="a">San Francisco, Calif. :</subfield>
   <subfield code="b">Morgan Kaufmann Publishers,</subfield>
   <subfield code="c">c2003.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">1 online resource (xxii, 458 p.) :</subfield>
   <subfield code="b">ill.</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
   <subfield code="a">Includes bibliographical references (p. 433-440) and index.</subfield>
  </datafield>
  <datafield tag="505" ind1="0" ind2=" ">
   <subfield code="a">Scenario -- Groundwork -- Structure -- Meaning -- Modeling processes -- Communication -- Navigation and discovery -- Presentation formats -- Infrastructure -- Solutions.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
   <subfield code="a">XML is bringing together some fairly disparate groups into a new cultural clash: document developers trying to understand what a transaction is, database analysts getting upset because the relational model doesn't fit anymore, and web designers having to deal with schemata and rule based transformations. The key to rising above the confusion is to understand the different semantic structures that lie beneath the standards of XML, and how to model the semantics to achieve the goals of the organization. A pure architecture of XML doesn't exist yet, and it may never exist as the underlying technologies are so diverse. Still, the key to understanding how to build the new web infrastructure for electronic business lies in understanding the landscape of these new standards. If your background is in document processing, this book will show how you can use conceptual modeling to model business scenarios consisting of business objects, relationships, processes, and transactions in a document-centric way. Database designers will learn if XML is subject to relational normalization and how this fits in with the hierarchical structure of XML documents. Web designers will discover that XML puts them into a position to automatically generate visually pleasing web pages and rich multimedia shows from otherwise dry product catalogues by using XSLT and other transformation tools. Business architects will see how XML can help them to define applications that can be quickly adapted the ever changing requirements of the market.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="4">
   <subfield code="a">Computer architecture.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="4">
   <subfield code="a">XML (Document markup language)</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
   <subfield code="a">XML.</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="4">
   <subfield code="a">Electronic books.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Merten, Udo.</subfield>
  </datafield>
  <datafield tag="852" ind1=" " ind2=" ">
   <subfield code="a">INST</subfield>
   <subfield code="b">UNIPILB</subfield>
   <subfield code="c">EBOOKS</subfield>
   <subfield code="e">20100705</subfield>
   <subfield code="p">00b48280</subfield>
   <subfield code="q">00b48280</subfield>
   <subfield code="t">ONLINE</subfield>
   <subfield code="y">0</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="3">ScienceDirect</subfield>
   <subfield code="u">http://www.sciencedirect.com/science/book/9781558607453</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
   <subfield code="d">/webopac/covers/03/48280_9781558607453.jpg</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
   <subfield code="d">/webopac/covers/03/48280_1558607455.jpg</subfield>
  </datafield>
 </record>
</collection>
