Who is the inventor of xml

Since many applications are data centric and are interested in the contents of the XML document, then the first approach is not suitable. The second option is to parse the data from the XML document and store this as regular relational data. Since XML should be self-contained, in the sense that it contains both data, and the meaning of the data, it should be possible to parse the XML file to find the data points of interest to the application, and store these in relational or object-relational tables.

A consequence of this approach is that a significant amount of processing is required when parsing XML data. This is especially pronounced when large datasets are being transported as XML. All that is required in this approach is to register the XML schema with Oracle database.

This approach provides the best of both previous approaches with ease of storage, and relational style access to the contained data through SQL queries.

This approach is only appropriate when a schema is defined for the stored XML so it makes this approach unsuitable where no schema exists, or where the schema is frequently modified. As older legacy system are being upgraded for service oriented architecture, and web services, making the contained data available in XML formats is becoming more important for engineers.

This requires approaches for mapping existing relational data to XML formats. They present a method to generate DTDs from relational schemas in the presence of keys, foreign keys, and functional dependencies, which can preserve the semantics implied by functional dependencies, keys and foreign keys of relational schemas and can convert multiple tables to XML DTDs.

While this is a forward step towards full semantic conversion of relational schemas to XML DTDs, they note there is still work remaining in converting further relational semantics such as multi-valued dependencies.

These do not allow a sufficient level of detail to be used in XML to relational mapping. For example, DTD can define a list to contain zero or more, or one or more elements, though it cannot define other limits. This can specify a list to contain 2 to 5 elements for example, and can be used to ensure that an XML document is both well formed and valid against this schema.

XML has proved hugely successful in the areas of document mark-up, data and meta-data sharing, enabling interoperability, and transparently transporting and storing data. With the current level of interest in the next generation of enterprise systems, the use of XML is set to grow as it is a core technology to web services, portal development and service oriented architectures.

Here are the latest Insider stories. More Insider Sign Out. Sign In Register. Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here.

More from the IDG Network. Sun's stars: Where are they now? Browsers also tried to be tolerant of hastily written web pages that committed crimes like using an opening tag without a corresponding closing tag. Tolerance is normally commendable, but the resulting lack of discipline became a barrier to programmatic interpretation of web content, or the use of HTML for structured data.

That is only one small part of what XML is all about. The key point is that using XML the industry can specify how to store almost any kind of data, in a form that applications running on any platform can easily import and process. In the mid s Sun Microsystems introduced Java, with the ability to applications securely on any supported platform.

One early use was to create applets, applications designed to run safely in web browsers. Rather, Java helped companies like IBM make sense of their diverse range of operating systems. Having each system running Java greatly simplifies the business of creating interoperable applications.

Another example is Oracle, which uses Java stored procedures as an ideal solution for its cross-platform database. The significance of XML to Microsoft is only now becoming clear, with the company describing its. Microsoft emphatically does not own XML, and the technology has transcended politics by virtue of its sheer usefulness.

The fact that XML is important to all three companies says a lot for its bridge-building potential. The mere fact of a document being in XML is no guarantee of usefulness. These are large documents with hundreds of Visio-specific elements and attributes. It might make it easier for other vendors to create an import filter; but the real benefit will come if and when Microsoft and other drawing application vendors sit down to thrash out an agreed XML standard for drawing documents.

With XML, standards are everything.