Affinity exchange dating service
[local archive copy] [This paragraph is superseded by the technical NOTE 'NOTE-sgml-xml' referenced immediately above.] Features in SGML but not in XML include [as of November 5, 1996]: "Tag omission; The CONCUR, LINK, DATATAG, and SHORTREF features; The "&" connector in content models; Inclusions and exclusions in content models; CURRENT, CONREF, NAME, NAMES, NUMBER, NUMBERS, NUTOKEN, and NUTOKENS declarations for attributes; The NET construct; Abstract syntax; Capacities and quantities; Comments appearing within other markup declarations; Public Identifiers; Omission of quotes on attribute values." For a more recent/complete comparison of features, see the relevant section in the language specification, or "What else has changed between SGML and XML? As of December 1997, the current and former members of the XML WG are: "Jon Bosak, Sun (Chair); James Clark (Technical Lead); Tim Bray, Textuality and Netscape (XML Co-editor); Jean Paoli, Microsoft (XML Co-editor); C. It may be necessary to regard some of these ideas 'in draft' like some of the specifications documents themselves. [June 30, 1999] A 'TEI Lite DTD in XML' was made available from the TEI Web site.
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.
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 specification describes the required behavior of an XML processor in terms of how it must read XML data and the information it must provide to the application." [adapted from the Proposal] Valid XML documents are designed to be valid SGML documents, but XML documents have additional restrictions. Several other W3C specifications are also critical to the understanding and implementation of XML as it is currently used. Editors: Tim Bray (Textuality and Netscape), Jean Paoli (Microsoft), and C. Sperberg-Mc Queen (University of Illinois at Chicago). Obviously, many of these application areas provide exemplary models, having unquestioned integrity and high quality.
The NOTE also includes an SGML declaration which describes the constraints of XML applicable to an SGML parser. It is also to be expected that some early XML/XLink/XSL applications may be merely demonstrations, toys, proof-of-concept applications; still others might be naive or ill conceived.The Extensible Markup Language (XML) is descriptively identified in the XML 1.0 W3C Recommendation as "an extremely simple dialect [or 'subset'] of SGML" the goal of which "is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML," for which reason "XML has been designed for ease of implementation, and for interoperability with both SGML and HTML." Note that the "HTML" referenced in the preceding sentence (bis) means HTML 4.0 and 3.2 which were in common use as of 10-February-1998, when the XML 1.0 specification was published as a W3C Recommendation.The next version of 'HTML' is expected to be reformulated as an XML application, so that it will be based upon XML rather than upon SGML. As the manager of the DNS root zone, we are responsible for coordinating these delegations in accordance with our policies and procedures.Several introductory and tutorial articles on the Extensible Markup Language (XML) are referenced in the shorter XML Introduction document. "The Extensible Markup Language (XML) is the universal format for structured documents and data on the Web." -- W3C XML Web site, 2000-07-06.