Chapter 13XML and ADO.NET.ppt

Chapter 13XML and ADO.NET Introduction Database processing and document processing need each other Database processing needs document processing for expressing database views Document processing needs database processing for storing and manipulating data As Internet usage increased, organizations wanted to make their Web pages more functional by displaying and updating data from organizational databases XML XML, or Extensible Markup Language, developed in early 1990s XML is a subset of SGML, or Standard Generalized Markup Language Today XML is a hybrid of document processing and database processing It provides a standardized yet customizable way to describe the content of documents XML documents can automatically be generated from database data, and vice versa SOAP is an XML-based standard protocol for sending messages of any type, using any protocol over the Internet XML (cont.) XML is used for describing, representing, and materializing database views XML is better than HTML because It provides a clear separation between document structure, content, and materialization It is standardized but allows for extension by developers XML tags accurately represent the semantics of their data Document Type Declarations (DTDs) and XML Schemas can be used to describe the content of XML documents Both Oracle and SQL Server can produce XML documents from database data Example: XML Document XML DTD XML document consists of two sections: Document Type Declaration (DTD) The DTD begins with DOCTYPE document_type_name Document data XML documents could be Type-valid if the document conforms to its DTD Well-formed and not be type-valid, because It violates the structure of its DTD It has no DTD DTD may be stored externally so many documents can be validated against the same DTD XSLT XSLT, or the Extensible Style Language may be used to materialize (transform) XML documents using XSL document From XML documents into HTML or into XML in another format XSLT is a declarative trans