A software module called an XML processor is used to read XML documents and provide access to their content and structure. Edited by Tim Bray (Textuality and Netscape), Jean Paoli (Microsoft), C. Sperberg-Mc Queen (University of Illinois at Chicago and Text Encoding Initiative), and Eve Maler (Sun Microsystems, Inc. The XML applications and announced industry initiatives listed below have not been evaluated according to any serious criteria for quality and genuineness.
It is assumed that an XML processor is doing its work on behalf of another module, called the application. is the principal document governing the XML standard. Since the various specifications documents for XML/XLink/XSL are still in some flux, it would often be unfair or difficult to make such a judgment.
This paper describes an XML vocabulary for schemas.
One immediate implication of these ideas is a substantive part of the functionalities of XML document types can now be described using the XML instance syntax itself, rather than DTD syntax.
XML was initially "developed by a W3C Generic SGML Editorial Review Board formed under the auspices of the W3 Consortium in 1996 and chaired by Jon Bosak of Sun Microsystems, with the very active participation of a Generic SGML Working Group also organized by the W3C." An XML WG (Working Group) under W3C served initially as an editorial board, which received input from an XML Special Interest Group.
As of late 1998, the XML design effort was re-chartered under the direction of an XML Coordination Group and XML Plenary Interest Group to be carried out in five new XML working groups: XML Schema Working Group, XML Fragment Working Group, XML Linking Working Group (XLink and XPointer), XML Information Set Working Group, and XML Syntax Working Group.
The good news is this: Net users are seeing clearly that a fixed tag set (like HTML) is not the solution. See the references for TEI - the XML version in a separate document, and the section 'Academic Applications' for background on the SGML version of the TEI DTD.