1. XML: A Revolution Unfolds Adam Bosworth Microsoft Corporation

2. Agenda XML today XML today The canonical model The canonical model A Demo A Demo Reminder. Why XML at all Reminder. Why XML at all Where we’re going Where we’re going

3. XML Today

4. What’s shipping today www.microsoft.com/xml www.microsoft.com/xml www.oracle.com/xml www.oracle.com/xml www.ibm.com/xml www.ibm.com/xml Object Design, Poet Object Design, Poet Bluestone Bluestone Perl, Python, Frontier… Perl, Python, Frontier…

5. Shipping from Microsoft Full XML support. Full XML support. XML Parser. Fully DOM Compliant. Server Ready! XML Parser. Fully DOM Compliant. Server Ready! Namespace support Namespace support Direct Browsing of XML Direct Browsing of XML Full XSL Support Full XSL Support Extended Schema Support Extended Schema Support All formats ==> XML. All formats ==> XML.

6. The canonical model A general model for mapping type systems, databases, objects and graphs to XML. A general model for mapping type systems, databases, objects and graphs to XML.  Types = Elements  Members = Attributes  Members whose type isn’t primitive are modeled using ID and IDREF/IDREFS’s.

7. The canonical model  

8. The canonical model    <!ATTLIST Invoice cost CDATA #IMPLIED cost CDATA #IMPLIED billtoIDREF#IMPLIED billtoIDREF#IMPLIED shiptoIDREF#IMPLIED> shiptoIDREF#IMPLIED>   <!ATTLIST Address <!ATTLIST Address idID#REQUIRED idID#REQUIRED City CDATA#IMPLIED City CDATA#IMPLIED ZipCDATA#IMPLIED> ZipCDATA#IMPLIED>

9. The canonical model Sharing Sharing  

10. The canonical model 1 to Many 1 to Many  

11. The canonical model Many to Many Many to Many  

12. Demo Some examples using IE 5.0 Some examples using IE 5.0  Structured Data (Objects, Databases)  Semi-structured Data (Documents)  Mixed Structured and Semi- structured Data. (The real objects on the Web)

13. Reminder. Why XML? Driven by two fundamental strategic imperatives: Driven by two fundamental strategic imperatives:  Provide a model for finding goods, services, and other types of known information  Provide an applications architecture for the Web

14. Scenarios Search for: Search for:  Goods (e.g. Used Books)  Services (e.g. Lawn-mowing)  Information (e.g. Portfolios) Share information between organizations and companies. Share information between organizations and companies.

15. Challenges to Realize the Web’s Full Potential... Find information intelligently Find information intelligently Interact with applications on servers easily and efficiently Interact with applications on servers easily and efficiently But: physical implementations will vary from site to site But: physical implementations will vary from site to site

16. Web Sites Requirements Standardize on logical views, not physical implementations Standardize on logical views, not physical implementations Standard description of logical views available Standard description of logical views available  More than databases actually did Sites can interact with each other and with clients! Sites can interact with each other and with clients!

17. Lessons from the Web Simplicity wins Simplicity wins  Open, Easy, Flexible Efficiency loses Efficiency loses  Complex, Binary formats, Fixed vocabularies

18. Lessons from Servers Servers are like grocery stores Servers are like grocery stores Good performance requires Good performance requires Coarse-grained communication Coarse-grained communication Limited ability to multitask Limited ability to multitask Queues Queues Interruptible models Interruptible models Standards Standards

19. We have learned We need an architecture that lets us interact in a coarse- grained way through logical views We need an architecture that lets us interact in a coarse- grained way through logical views As a Web architecture, it must be easy, open, and flexible to build and interact with these logical views As a Web architecture, it must be easy, open, and flexible to build and interact with these logical views

20. XML XML is the most fundamental building block XML is the most fundamental building block  It is the Meta-grammar that allows us to describe any data or state for any logical view  It is simple, easy, and open  It can describe any package of information moved to or from the middle-tier

21. Application architecture Storage Middle- Tier Client Transform Data into XML Logical Views (web objects) View, Edit & Manage XML XML Msg’s XML Store XML Store

22. Coming very soon Stores and convertors Stores and convertors RPC’s RPC’s Schema support Schema support “XQL” “XQL” eCommerce and XML eCommerce and XML

23. Stores and Converters Converters between physical implementations and XML- based logical views. Oracle has already got a stake in the ground here. Converters between physical implementations and XML- based logical views. Oracle has already got a stake in the ground here. There is a need to cache, index, update, transact, and in short, have a store for managing XML. ODI & eXcelon There is a need to cache, index, update, transact, and in short, have a store for managing XML. ODI & eXcelon

24. Schema Active working group in the W3C now. Active working group in the W3C now. Unified support for data types. Unified support for data types. Clear understanding of the need for: Clear understanding of the need for:  FK/PK relationships  Ordered or unordered  Inherited types.

25. RPC XML provides a basis for an extremely simple extensible RPC. UserLand(Frontier), Perl, Python, Allaire( WDDX), and webMethods(B2B). XML provides a basis for an extremely simple extensible RPC. UserLand(Frontier), Perl, Python, Allaire( WDDX), and webMethods(B2B). But, in many cases, messages, not RPC’s will be used. RPC’s are rarely robust over time and distance. But, in many cases, messages, not RPC’s will be used. RPC’s are rarely robust over time and distance.

26. Unified “XQL” The Query language is the object construction language. The Query language is the object construction language. Which language? Which language?  XSL? Sql?  Key W3C Meeting in Boston in December. Database vendors and object vendors will end up working together on this “XQL” Database vendors and object vendors will end up working together on this “XQL”

27. eCommerce using XML XML/EDI Group XML/EDI Group ASC X12 /CommerceNet/ Graphics Communication Association ASC X12 /CommerceNet/ Graphics Communication Association OO-EDI Brief /DRAFT. Relevant Standards Organization UN/CEFACT OO-EDI Brief /DRAFT. Relevant Standards Organization UN/CEFACT OFX (Financial Services) OFX (Financial Services)

28. Remember the book store Describe the books Describe the books Describe the store’s services Describe the store’s services Request specific books Request specific books Act as my shopping cart Act as my shopping cart Allow me to buy books Allow me to buy books

29. Still to come… “XUL” “XUL” We need a grammar to act as an intelligent diff or updating grammar to XML. This is actually a hard problem when the document being updated is “virtual” rather than real. We need a grammar to act as an intelligent diff or updating grammar to XML. This is actually a hard problem when the document being updated is “virtual” rather than real.

30. Still to come Application Services Broker Application Services Broker  This mediates between sites, discovering which sites provide which services meeting certain filters or characteristics.  It should, if scalability can be handled, allow subscription and notification based upon criteria.

31. Still to come Application Bus Application Bus This allows general publish/subscribe to messages of interest. It assumes a general message queue accessible through HTTP. This allows general publish/subscribe to messages of interest. It assumes a general message queue accessible through HTTP. Ideally, it will be able to post messages directly to other machines message queues. Ideally, it will be able to post messages directly to other machines message queues.

32. What can be built today? Line-of-business applications Line-of-business applications  Planning  Notification  Data Capture  Information searching  Collaboration

33. Summary We’re only at the very start of the Web revolution. The most exciting part is just getting started. We’re only at the very start of the Web revolution. The most exciting part is just getting started. With XML, interacting with data and applications on the Web will be as easy as viewing shared content With XML, interacting with data and applications on the Web will be as easy as viewing shared content

34. Application architecture Storage Middle- Tier Client Transform Data into XML Logical Views (web objects) View, Edit & Manage XML XML Msg’s XML Store XML Store

35. ™ http://www.microsoft.com/xml