System architecture with XML / Berthold Daum, Udo Merten.

By:

Daum, Berthold, 1949- [author.]

Contributor(s):

Merten, Udo [eauthor.]

Material type: Text

Text

Media type:

Unmediated

Carrier type:

Volume

ISBN:

9781558607453
1558607455

Subject(s):

LOC classification:

QA76.9.A7 D38 2003

Available additional physical forms:

Karton kapak.

Contents:

Scenario -- Groundwork -- Structure -- Meaning -- Modeling processes -- Communication -- Navigation and discovery -- Presentation formats -- Infrastructure -- Solutions.

Summary: 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.

Tags from this library: No tags from this library for this title. Log in to add tags.

Average rating: 0.0 (0 votes)

Holdings
Item type	Current library	Home library	Collection	Call number	Status	Date due	Barcode
Book	Merkez Kütüphane Genel Koleksiyon / Main Collection	Merkez Kütüphane	Genel Koleksiyon	QA76.9.A7.D38 2003 (Browse shelf(Opens below))	Available		0053265

Browsing Merkez Kütüphane shelves, Shelving location: Genel Koleksiyon / Main Collection, Collection: Genel Koleksiyon Close shelf browser (Hides shelf browser)

Previous								Next
Previous	QA76.9.A43 M58 1997 Machine learning /	QA76.9.A43 V38 2004 Algoritma geliştirme ve programlamaya giriş /	QA76.9.A43 V39 2001 Approximation algorithms /	QA76.9.A7.D38 2003 System architecture with XML /	QA76.9.A73 1987 AKTs Structured analysis and design of information systems /	QA76.9.A73 B79 2004 MIPS assembly language programming /	QA76.9.A73 C38 2002 Schaum's outline of computer architecture /	Next

Scenario -- Groundwork -- Structure -- Meaning -- Modeling processes -- Communication -- Navigation and discovery -- Presentation formats -- Infrastructure -- Solutions.

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.