1. Challenges in XML It’s good… but is it good enough? Siddhesh Bhobe Persistent eBusiness Solutions

2. XML goals 1. XML shall be straightforwardly usable over the Internet. 2. XML shall support a wide variety of applications. 3. XML shall be compatible with SGML. 4. It shall be easy to write programs which process XML documents. 5. The number of optional features in XML is to be kept to the absolute minimum, ideally zero.

3. XML goals (Cont.) 6. XML documents should be human-legible and reasonably clear. 7. The XML design should be prepared quickly. 8. The design of XML shall be formal and concise. 9. XML documents shall be easy to create. 10. Terseness in XML markup is of minimal importance.

4. XML has been successful! XML is emerging as a standard for Document Exchange Significant momentum in the market place and industry consortia –Commerce One –Rosetta Net –Biztalk –PeBS

5. But… is it good enough?

6. XML is verbose Column1|Column2|………. ColumnN| becomes value1 value2 : valueN

7. So? More storage space More network transmission time Data exchange on the net will be very expensive!

8. Anything positive? Lends itself very well to compression in case of structured data (like web logs) Migrated non-XML data gives better compression than the original data. (Xmill, paper at SIGMOD 2000)

9. Storing XML is difficult! Store as text, but… Impossible to query… no indexing possible! Additional cost of creating blocks… limit on size of text that can be stored in databases Can be updated only by replacing the entire XML document!

10. Storing XML (Cont.) Store in database tables, but… XML to relational data conversion is very expensive! Current set of tools handle only regular XML document structures (Ex. XML-DBMS)

11. XML in Oracle 8i Store XML document as a single, intact object with its tags in a CLOB or BLOB Store the XML document as data and distribute it untagged across object- relational tables Combine XML documents and data using views

12. Processing XML is costly! XML needs to be parsed… and that is not efficient! Tools available today are not easy to use. Need better ones. Text processing is always a performance hit Do NOT use XML for passing parameters!

13. No data types in XML No data type support… all XML data is text Limited options for binary data XML Schema Part 2: Datatypes ( W3C Working Draft, 22 September 2000) proposes facilities for defining datatypes in XML

14. Encoding Binary Data 2048 2500... The PIXELS element would contain the binary data encoded in some notation like Base64.

15. Multipart/related MIME type (RFC 2112) MIME is used for e-mail messages that are not just ASCII text, but include different "types" of information The multipart/related MIME type was developed to represent compound documents. Individual parts represent individual streams in the compound document.

16. Example… Content-Type: multipart/related --xxxxxxxxxx Content-Type: application/binary Content-Transfer-Encoding: Little-Endian Content-ID: Pixels Content-Length: 524288.…encoded binary data here... --xxxxxxxxxx

17. Conclusion XML is great as a data exchange format, but…. Need compression Need better storage techniques Need fast and easy to use parsers Need data type support