W3C home > Mailing lists > Public > xml-editor@w3.org > April to June 2000

http://www.w3.org/TR/1998/REC-xml-19980210.xml

From: Glenn family <glennfamily@maranatha.net>
Date: Wed, 3 May 2000 19:24:39 -0400
Message-ID: <000d01bfb556$c4a92ea0$5f65fdd8@default>
To: <xml-editor@w3.org>


Was attempting to download this xml page so I could veiw it's source and possibly teach myself in the process.  Have IE5 installed.  Is there a problem with the page or am I missing something... maybe a browser plugin?  Got following message:

                
    The XML page cannot be displayed 
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. 


----------------------------------------------------------------------------

    Error while parsing entity 'lt'. A declaration was not closed. Line 1, Position 1 

     

<

.............................................
This is a copy of what source I was able to view:
<?xml version='1.0' encoding='ISO-8859-1' standalone='no'?><!DOCTYPE spec SYSTEM "spec.dtd" [
<!-- LAST TOUCHED BY: Tim Bray, 8 February 1997 -->
<!-- The words 'FINAL EDIT' in comments mark places where changesneed to be made after approval of the document by the ERB, beforepublication.  -->
<!ENTITY XML.version "1.0"><!ENTITY doc.date "10 February 1998"><!ENTITY iso6.doc.date "19980210"><!ENTITY w3c.doc.date "02-Feb-1998"><!ENTITY draft.day '10'><!ENTITY draft.month 'February'><!ENTITY draft.year '1998'>
<!ENTITY WebSGML  'WebSGML Adaptations Annex to ISO 8879'>
<!ENTITY lt     "<"> <!ENTITY gt     ">"> <!ENTITY xmlpio "'&lt;?xml'"><!ENTITY pic    "'?>'"><!ENTITY br     "\n"><!ENTITY cellback '#c0d9c0'><!ENTITY mdash  "--"> <!-- &#x2014, but nsgmls doesn't grok hex --><!ENTITY com    "--"><!ENTITY como   "--"><!ENTITY comc   "--"><!ENTITY hcro   "&amp;#x"><!-- <!ENTITY nbsp " "> --><!ENTITY nbsp   "&#160;"><!ENTITY magicents "<code>amp</code>,<code>lt</code>,<code>gt</code>,<code>apos</code>,<code>quot</code>"> <!-- audience and distribution status:  for use at publication time --><!ENTITY doc.audience "public review and discussion"><!ENTITY doc.distribution "may be distributed freely, as long asall text and legal notices remain intact">
]>
<!-- for Panorama *--><?VERBATIM "eg" ?>
<spec><header><title>Extensible Markup Language (XML) 1.0</title><version></version><w3c-designation>REC-xml-&iso6.doc.date;</w3c-designation><w3c-doctype>W3C Recommendation</w3c-doctype><pubdate><day>&draft.day;</day><month>&draft.month;</month><year>&draft.year;</year></pubdate>
<publoc><loc  href="http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;">http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;</loc><loc  href="http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.xml">http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.xml</loc><loc  href="http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.html">http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.html</loc><loc  href="http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.pdf">http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.pdf</loc><loc  href="http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.ps">http://www.w3.org/TR/1998/REC-xml-&iso6.doc.date;.ps</loc></publoc><latestloc><loc  href="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</loc></latestloc><prevlocs><loc  href="http://www.w3.org/TR/PR-xml-971208">http://www.w3.org/TR/PR-xml-971208</loc><!--<loc  href='http://www.w3.org/TR/WD-xml-961114'>http://www.w3.org/TR/WD-xml-961114</loc><loc  href='http://www.w3.org/TR/WD-xml-lang-970331'>http://www.w3.org/TR/WD-xml-lang-970331</loc><loc  href='http://www.w3.org/TR/WD-xml-lang-970630'>http://www.w3.org/TR/WD-xml-lang-970630</loc><loc  href='http://www.w3.org/TR/WD-xml-970807'>http://www.w3.org/TR/WD-xml-970807</loc><loc  href='http://www.w3.org/TR/WD-xml-971117'>http://www.w3.org/TR/WD-xml-971117</loc>--></prevlocs><authlist><author><name>Tim Bray</name><affiliation>Textuality and Netscape</affiliation><email href="mailto:tbray@textuality.com">tbray@textuality.com</email></author><author><name>Jean Paoli</name><affiliation>Microsoft</affiliation><email href="mailto:jeanpa@microsoft.com">jeanpa@microsoft.com</email></author><author><name>C. M. Sperberg-McQueen</name><affiliation>University of Illinois at Chicago</affiliation><email href="mailto:cmsmcq@uic.edu">cmsmcq@uic.edu</email></author></authlist><abstract><p>The Extensible Markup Language (XML) is a subset ofSGML that is completely described in this document. Its goal is toenable generic SGML to be served, received, and processed on the Webin the way that is now possible with HTML. XML has been designed forease of implementation and for interoperability with both SGML andHTML.</p></abstract><status><p>This document has been reviewed by W3C Members andother interested parties and has been endorsed by theDirector as a W3C Recommendation. It is a stabledocument and may be used as reference material or citedas a normative reference from another document. W3C'srole in making the Recommendation is to draw attentionto the specification and to promote its widespreaddeployment. This enhances the functionality andinteroperability of the Web.</p><p>This document specifies a syntax created by subsetting an existing,widely used international text processing standard (StandardGeneralized Markup Language, ISO 8879:1986(E) as amended andcorrected) for use on the World Wide Web.  It is a product of the W3CXML Activity, details of which can be found at <lochref='http://www.w3.org/XML'>http://www.w3.org/XML</loc>.  A list ofcurrent W3C Recommendations and other technical documents can be foundat <loc href='http://www.w3.org/TR'>http://www.w3.org/TR</loc>.</p><p>This specification uses the term URI, which is defined by <bibrefref="Berners-Lee"/>, a work in progress expected to update <bibrefref="RFC1738"/> and <bibref ref="RFC1808"/>. </p><p>The list of known errors in this specification is available at <loc href='http://www.w3.org/XML/xml-19980210-errata'>http://www.w3.org/XML/xml-19980210-errata</loc>.</p><p>Please report errors in this document to <loc href='mailto:xml-editor@w3.org'>xml-editor@w3.org</loc>.</p></status>
<pubstmt><p>Chicago, Vancouver, Mountain View, et al.:World-Wide Web Consortium, XML Working Group, 1996, 1997.</p></pubstmt><sourcedesc><p>Created in electronic form.</p></sourcedesc><langusage><language id='EN'>English</language><language id='ebnf'>Extended Backus-Naur Form (formal grammar)</language></langusage><revisiondesc><slist><sitem>1997-12-03 : CMSMcQ : yet further changes</sitem><sitem>1997-12-02 : TB : further changes (see TB to XML WG,2 December 1997)</sitem><sitem>1997-12-02 : CMSMcQ : deal with as many corrections andcomments from the proofreaders as possible:entify hard-coded document date in pubdate element,change expansion of entity WebSGML,update status description as per Dan Connolly (am not sureabout refernece to Berners-Lee et al.),add 'The' to abstract as per WG decision,move Relationship to Existing Standards to back matter andcombine with References,re-order back matter so normative appendices come first,re-tag back matter so informative appendices are tagged informdiv1,remove XXX XXX from list of 'normative' specs in prose,move some references from Other References to Normative References,add RFC 1738, 1808, and 2141 to Other References (they are notnormative since we do not require the processor to enforce any rules based on them),add reference to 'Fielding draft' (Berners-Lee et al.),move notation section to end of body,drop URIchar non-terminal and use SkipLit instead,lose stray reference to defunct nonterminal 'markupdecls',move reference to Aho et al. into appendix (Tim's right),add prose note saying that hash marks and fragment identifiers areNOT part of the URI formally speaking, and are NOT legal in system identifiers (processor 'may' signal an error).Work through:Tim Bray reacting to James Clark,Tim Bray on his own,Eve Maler,
NOT DONE YET:change binary / text to unparsed / parsed.handle James's suggestion about &lt; in attriubte valuesuppercase hex characters,namechar list,</sitem><sitem>1997-12-01 : JB : add some column-width parameters</sitem><sitem>1997-12-01 : CMSMcQ : begin round of changes to incorporaterecent WG decisions and other corrections:binding sources of character encoding info (27 Aug / 3 Sept),correct wording of Faust quotation (restore dropped line),drop SDD from EncodingDecl,change text at version number 1.0,drop misleading (wrong!) sentence about ignorables and extenders,modify definition of PCData to make bar on msc grammatical,change grammar's handling of internal subset (drop non-terminal markupdecls),change definition of includeSect to allow conditional sections,add integral-declaration constraint on internal subset,drop misleading / dangerous sentence about relationship ofentities with system storage objects,change table body tag to htbody as per EM change to DTD,add rule about space normalization in public identifiers,add description of how to generate our name-space rules from Unicode character database (needs further work!).</sitem><sitem>1997-10-08 : TB : Removed %-constructs again, new rulesfor PE appearance.</sitem><sitem>1997-10-01 : TB : Case-sensitive markup; cleaned upelement-type defs, lotsa little edits for style</sitem><sitem>1997-09-25 : TB : Change to elm's new DTD, withsubstantial detail cleanup as a side-effect</sitem><sitem>1997-07-24 : CMSMcQ : correct error (lost *) in definition of ignoreSectContents (thanks to Makoto Murata)</sitem><sitem>Allow all empty elements to have end-tags, consistent withSGML TC (as per JJC).</sitem><sitem>1997-07-23 : CMSMcQ : pre-emptive strike on pending corrections:introduce the term 'empty-element tag', note that all empty elementsmay use it, and elements declared EMPTY must use it.Add WFC requiring encoding decl to come first in an entity.Redefine notations to point to PIs as well as binary entities.Change autodetection table by removing bytes 3 and 4 from examples with Byte Order Mark.Add content model as a term and clarify that it applies to bothmixed and element content.</sitem><sitem>1997-06-30 : CMSMcQ : change date, some cosmetic changes,changes to productions for choice, seq, Mixed, NotationType,Enumeration.  Follow James Clark's suggestion and prohibit conditional sections in internal subset.  TO DO:  simplifyproduction for ignored sections as a result, since we don't need to worry about parsers which don't expand PErefs findinga conditional section.</sitem><sitem>1997-06-29 : TB : various edits</sitem><sitem>1997-06-29 : CMSMcQ : further changes:Suppress old FINAL EDIT comments and some dead material.Revise occurrences of % in grammar to exploit Henry Thompson's pun,especially markupdecl and attdef.Remove RMD requirement relating to element content (?).</sitem><sitem>1997-06-28 : CMSMcQ : Various changes for 1 July draft:Add text for draconian error handling (introducethe term Fatal Error).RE deleta est (changing wording from original announcement to restrict the requirement to validatingparsers).Tag definition of validating processor and link to it.Add colon as name character.Change def of %operator.Change standard definitions of lt, gt, amp.Strip leading zeros from #x00nn forms.</sitem><sitem>1997-04-02 : CMSMcQ : final corrections of editorial errorsfound in last night's proofreading.  Reverse course once more onwell-formed:   Webster's Second hyphenates it, and that's enoughfor me.</sitem><sitem>1997-04-01 : CMSMcQ : corrections from JJC, EM, HT, and self</sitem><sitem>1997-03-31 : Tim Bray : many changes</sitem><sitem>1997-03-29 : CMSMcQ : some Henry Thompson (on entity handling),some Charles Goldfarb, some ERB decisions (PE handling in miscellaneousdeclarations.  Changed Ident element to accept def attribute.Allow normalization of Unicode characters.  move def of systemliteralinto section on literals.</sitem><sitem>1997-03-28 : CMSMcQ : make as many corrections as possible, fromTerry Allen, Norbert Mikula, James Clark, Jon Bosak, Henry Thompson,Paul Grosso, and self.  Among other things:  give in on "well formed"(Terry is right), tentatively rename QuotedCData as AttValueand Literal as EntityValue to be more informative, since attributevalues are the <emph>only</emph> place QuotedCData was used, andvice versa for entity text and Literal. (I'd call it Entity Text, but 8879 uses that name for both internal and external entities.)</sitem><sitem>1997-03-26 : CMSMcQ : resynch the two forks of this draft, reapplymy changes dated 03-20 and 03-21.  Normalize old 'may not' to 'must not'except in the one case where it meant 'may or may not'.</sitem><sitem>1997-03-21 : TB : massive changes on plane flight from Chicagoto Vancouver</sitem><sitem>1997-03-21 : CMSMcQ : correct as many reported errors as possible.</sitem><sitem>1997-03-20 : CMSMcQ : correct typos listed in CMSMcQ hand copy of spec.</sitem><sitem>1997-03-20 : CMSMcQ : cosmetic changes preparatory to revision forWWW conference April 1997:  restore some of the internal entity references (e.g. to docdate, etc.), change character xA0 to &amp;nbsp;and define nbsp as &amp;#160;, and refill a lot of paragraphs forlegibility.</sitem><sitem>1996-11-12 : CMSMcQ : revise using Tim's edits:Add list type of NUMBERED and change most lists either toBULLETS or to NUMBERED.Suppress QuotedNames, Names (not used).Correct trivial-grammar doc type decl.Rename 'marked section' as 'CDATA section' passim.Also edits from James Clark:Define the set of characters from which [^abc] subtracts.Charref should use just [0-9] not Digit.Location info needs cleaner treatment:  remove?  (ERBquestion).One example of a PI has wrong pic.Clarify discussion of encoding names.Encoding failure should lead to unspecified results; don'tprescribe error recovery.Don't require exposure of entity boundaries.Ignore white space in element content.Reserve entity names of the form u-NNNN.Clarify relative URLs.And some of my own:Correct productions for content model:  model cannotconsist of a name, so "elements ::= cp" is no good.</sitem><sitem>1996-11-11 : CMSMcQ : revise for style.Add new rhs to entity declaration, for parameter entities.</sitem><sitem>1996-11-10 : CMSMcQ : revise for style.Fix / complete section on names, characters.Add sections on parameter entities, conditional sections.Still to do:  Add compatibility note on deterministic content models.Finish stylistic revision.</sitem><sitem>1996-10-31 : TB : Add Entity Handling section</sitem><sitem>1996-10-30 : TB : Clean up term &amp; termdef.  Slip inERB decision re EMPTY.</sitem><sitem>1996-10-28 : TB : Change DTD.  Implement some of Michael'ssuggestions.  Change comments back to //.  Introduce language forXML namespace reservation.  Add section on white-space handling.Lots more cleanup.</sitem><sitem>1996-10-24 : CMSMcQ : quick tweaks, implement some ERBdecisions.  Characters are not integers.  Comments are /* */ not //.Add bibliographic refs to 10646, HyTime, Unicode.Rename old Cdata as MsData since it's <emph>only</emph> seenin marked sections.  Call them attribute-value pairs notname-value pairs, except once.  Internal subset is optional, needs'?'.  Implied attributes should be signaled to the app, nothave values supplied by processor.</sitem><sitem>1996-10-16 : TB : track down &amp; excise all DSD references;introduce some EBNF for entity declarations.</sitem><sitem>1996-10-?? : TB : consistency check, fix up scraps sothey all parse, get formatter working, correct a few productions.</sitem><sitem>1996-10-10/11 : CMSMcQ : various maintenance, stylistic, andorganizational changes:Replace a few literals with xmlpio andpic entities, to make them consistent and ensure we can change picreliably when the ERB votes.Drop paragraph on recognizers from notation section.Add match, exact match to terminology.Move old 2.2 XML Processors and Apps into intro.Mention comments, PIs, and marked sections in discussion ofdelimiter escaping.Streamline discussion of doctype decl syntax.Drop old section of 'PI syntax' for doctype decl, and addsection on partial-DTD summary PIs to end of Logical Structuressection.Revise DSD syntax section to use Tim's subset-in-a-PImechanism.</sitem><sitem>1996-10-10 : TB : eliminate name recognizers (and more?)</sitem><sitem>1996-10-09 : CMSMcQ : revise for style, consistency through 2.3(Characters)</sitem><sitem>1996-10-09 : CMSMcQ : re-unite everything for convenience,at least temporarily, and revise quickly</sitem><sitem>1996-10-08 : TB : first major homogenization pass</sitem><sitem>1996-10-08 : TB : turn "current" attribute on div type into CDATA</sitem><sitem>1996-10-02 : TB : remould into skeleton + entities</sitem><sitem>1996-09-30 : CMSMcQ : add a few more sections prior to exchange                            with Tim.</sitem><sitem>1996-09-20 : CMSMcQ : finish transcribing notes.</sitem><sitem>1996-09-19 : CMSMcQ : begin transcribing notes for draft.</sitem><sitem>1996-09-13 : CMSMcQ : made outline from notes of 09-06,do some housekeeping</sitem></slist></revisiondesc></header><body> <div1 id='sec-intro'><head>Introduction</head><p>Extensible Markup Language, abbreviated XML, describes a class ofdata objects called <termref def="dt-xml-doc">XML documents</termref> andpartially describes the behavior of computer programs which process them. XML is an application profile orrestricted form of SGML, the Standard Generalized Markup Language <bibref ref='ISO8879'/>.By construction, XML documents are conforming SGML documents.</p><p>XML documents are made up of storage units called <termrefdef="dt-entity">entities</termref>, which contain either parsedor unparsed data.Parsed data is made up of <termref def="dt-character">characters</termref>,some of which form <termref def="dt-chardata">character data</termref>, and some of which form <termref def="dt-markup">markup</termref>.Markup encodes a description of the document's storage layout andlogical structure. XML provides a mechanism to impose constraints onthe storage layout and logical structure.</p><p><termdef id="dt-xml-proc" term="XML Processor">A software modulecalled an <term>XML processor</term> is used to read XML documentsand provide access to their content and structure.</termdef> <termdefid="dt-app" term="Application">It is assumed that an XML processor isdoing its work on behalf of another module, called the<term>application</term>.</termdef> This specification describes therequired behavior of an XML processor in terms of how it must read XMLdata and the information it must provide to the application.</p> <div2 id='sec-origin-goals'><head>Origin and Goals</head><p>XML was developed by an XML Working Group (originally known as theSGML Editorial Review Board) formed under the auspices of the WorldWide Web Consortium (W3C) in 1996.It was chaired by Jon Bosak of SunMicrosystems with the active participation of an XML SpecialInterest Group (previously known as the SGML Working Group) alsoorganized by the W3C. The membership of the XML Working Group is givenin an appendix. Dan Connolly served as the WG's contact with the W3C.</p><p>The design goals for XML are:<olist><item><p>XML shall be straightforwardly usable over theInternet.</p></item><item><p>XML shall support a wide variety of applications.</p></item><item><p>XML shall be compatible with SGML.</p></item><item><p>It shall be easy to write programs which process XMLdocuments.</p></item><item><p>The number of optional features in XML is to be kept to theabsolute minimum, ideally zero.</p></item><item><p>XML documents should be human-legible and reasonablyclear.</p></item><item><p>The XML design should be prepared quickly.</p></item><item><p>The design of XML shall be formal and concise.</p></item><item><p>XML documents shall be easy to create.</p></item><item><p>Terseness in XML markup is of minimal importance.</p></item></olist></p><p>This specification, together with associated standards(Unicode and ISO/IEC 10646 for characters,Internet RFC 1766 for language identification tags, ISO 639 for language name codes, and ISO 3166 for country name codes),provides all the information necessary to understand XML Version &XML.version;and construct computer programs to process it.</p><p>This version of the XML specification<!-- is for &doc.audience;.-->&doc.distribution;.</p>
</div2> 
 <div2 id='sec-terminology'><head>Terminology</head> <p>The terminology used to describe XML documents is defined in the body ofthis specification.The terms defined in the following list are used in building thosedefinitions and in describing the actions of an XML processor:<glist><gitem><label>may</label><def><p><termdef id="dt-may" term="May">Conforming documents and XMLprocessors are permitted to but need not behave asdescribed.</termdef></p></def></gitem><gitem><label>must</label><def><p>Conforming documents and XML processors are required to behave as described; otherwise they are in error.<!-- do NOT change this! this is what defines a violation ofa 'must' clause as 'an error'. -MSM --></p></def></gitem><gitem><label>error</label><def><p><termdef id='dt-error' term='Error'>A violation of the rules of thisspecification; results areundefined.  Conforming software may detect and report an error and mayrecover from it.</termdef></p></def></gitem><gitem><label>fatal error</label><def><p><termdef id="dt-fatal" term="Fatal Error">An errorwhich a conforming <termref def="dt-xml-proc">XML processor</termref>must detect and report to the application.After encountering a fatal error, theprocessor may continueprocessing the data to search for further errors and may report sucherrors to the application.  In order to support correction of errors,the processor may make unprocessed data from the document (withintermingled character data and markup) available to the application.Once a fatal error is detected, however, the processor must notcontinue normal processing (i.e., it must notcontinue to pass character data and information about the document'slogical structure to the application in the normal way).</termdef></p></def></gitem><gitem><label>at user option</label><def><p>Conforming software may or must (depending on the modal verb in thesentence) behave as described; if it does, it mustprovide users a means to enable or disable the behaviordescribed.</p></def></gitem><gitem><label>validity constraint</label><def><p>A rule which applies to all <termref def="dt-valid">valid</termref> XML documents.Violations of validity constraints are errors; they must, at user option, be reported by <termref def="dt-validating">validating XML processors</termref>.</p></def></gitem><gitem><label>well-formedness constraint</label><def><p>A rule which applies to all <termrefdef="dt-wellformed">well-formed</termref> XML documents.Violations of well-formedness constraints are <termref def="dt-fatal">fatal errors</termref>.</p></def></gitem>
<gitem><label>match</label><def><p><termdef id="dt-match" term="match">(Of strings or names:) Two strings or names being compared must be identical.Characters with multiple possible representations in ISO/IEC 10646 (e.g.characters with both precomposed and base+diacritic forms) match only if they have thesame representation in both strings.At user option, processors may normalize such characters tosome canonical form.No case folding is performed. (Of strings and rules in the grammar:)  A string matches a grammatical production if it belongs to thelanguage generated by that production.(Of content and content models:)An element matches its declaration when it conformsin the fashion described in the constraint<specref ref='elementvalid'/>.</termdef></p></def></gitem><gitem><label>for compatibility</label><def><p><termdef id="dt-compat" term="For Compatibility">A feature ofXML included solely to ensure that XML remains compatible with SGML.</termdef></p></def></gitem><gitem><label>for interoperability</label><def><p><termdef id="dt-interop" term="For interoperability">Anon-binding recommendation included to increase the chances that XMLdocuments can be processed by the existing installed base of SGMLprocessors which predate the&WebSGML;.</termdef></p></def></gitem></glist></p></div2>
 </div1><!-- &Docs; --> <div1 id='sec-documents'><head>Documents</head> <p><termdef id="dt-xml-doc" term="XML Document">A data object is an<term>XML document</term> if it is<termref def="dt-wellformed">well-formed</termref>, asdefined in this specification.A well-formed XML document may in addition be<termref def="dt-valid">valid</termref> if it meets certain further constraints.</termdef></p> <p>Each XML document has both a logical and a physical structure.Physically, the document is composed of units called <termref
Received on Wednesday, 3 May 2000 19:25:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:30 GMT