"The Document Object Model is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents.
The document can be further processed and the results of that processing can be incorporated back into the presented page." The main database entry for the W3C DOM has been moved to a separate document.
By construction, XML documents are conforming SGML documents." "XML is primarily intended to meet the requirements of large-scale Web content providers for industry-specific markup, vendor-neutral data exchange, media-independent publishing, one-on-one marketing, workflow management in collaborative authoring environments, and the processing of Web documents by intelligent clients.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 W3C XML WG has published a technical NOTE providing a "detailed comparison of the additional restrictions that XML places on documents beyond those of SGML": see for the details. (XML Co-editor); Dan Connolly, W3C; Steve De Rose, INSO; Dave Hollander, HP; Eliot Kimber, Highland; Eve Maler, Arbor Text; Tom Magliery, NCSA; Murray Maloney, Muzmo and Grif; Makoto Murata, Fuji Xerox Information Systems; Joel Nava, Adobe; Peter Sharpe, Soft Quad; John Tigue, Data Channel." Historically: The W3C SGML Editorial Review Board, as of November 5, 1996, had the following members: Jon Bosak, Sun ([email protected]), chair; Tim Bray, Textuality ([email protected]), editor; James Clark ([email protected]), technical lead; Dan Connolly ([email protected]), W3C contact; Steve De Rose, EBT ([email protected]), editor; Dave Hollander, HP ([email protected]); Eliot Kimber, Passage Systems ([email protected]); Tom Magliery, NCSA ([email protected]); Eve Maler, Arbor Text ([email protected]); Jean Paoli, Microsoft ([email protected]); Peter Sharpe, Soft Quad ([email protected]); C. These specifications are being developed by various working groups, sometimes as part of activity outside the sphere of the XML Activity. Some already play a vital role in profitable commercial enterprise.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.Markup encodes a description of the document's storage layout and logical structure. See now the separate document for references to SGML/XML FAQs.