1、 INCITS/ISO/IEC 8879:1986/COR 2:19992010 (ISO 8879/Cor2:1999, IDT) Corrigendum Reaffirmed as INCITS/ISO/IEC 8879:1986/COR 2:1999 R2015INCITS/ISO/IEC 8879:1986/COR 2:19992010 PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be prin
2、ted or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no li
3、ability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is
4、 suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard. Date of ANSI Appr
5、oval: 7/15/2010 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2010 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copyright claims of International Standardization Organization (ISO),
6、 International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission
7、 of ITI. All requests pertaining to this standard should be submitted to ITI, 1101 K Street NW, Suite 610, Washington DC 20005. Printed in the United States of America ii ITIC 2010 All rights reserved ICS 35.240.30 Ref. No. ISO 8879:1986/Cor.2:1999(E) ISO/IEC 1999 All rights reservedPrinted in Switz
8、erlandINTERNATIONAL STANDARD ISO 8879:1986TECHNICAL CORRIGENDUM 2Published 1999-11-01INTERNATIONAL ORGANIZATION FOR STANDARDIZATION Gb7 Gb7 ORGANISATION INTERNATIONALE DE NORMALISATIONINTERNATIONAL ELECTROTECHNICAL COMMISSION Gb7 Gb7 COMMISSION LECTROTECHNIQUE INTERNATIONALEInformation processing Te
9、xt and office systems Standard Generalized Markup Language (SGML)TECHNICAL CORRIGENDUM 2Traitement de linformation Systmes bureautiques Langage normalis de balisage gnralis (SGML)RECTIFICATIF TECHNIQUE 2Technical Corrigendum 2 to International Standard ISO 8879:1986 was prepared by Joint Technical C
10、ommitteeISO/IEC JTC 1, Information technology, Subcommittee SC 34, Document description and processing languages.All occurrences of “element declaration“ in this International Standard are changed to “element type declaration“.All occurrences of “element set“ in this International Standard are chang
11、ed to “element type set“.Replace 4.223 with:4.223 owner identifier: The portion of a public identifier that identifies its owner.Note: The owner of a public identifier is not necessarily the owner of the object that it identifies.Add the following normative annex K and informative annex L to ISO 887
12、9.ISO 8879:1986/Cor.2:1999(E)2 ISO/IEC 1999 All rights reservedAnnex K(normative)Web SGML AdaptationsThis annex remedies defects revealed by the multiple adaptations of SGML for the World Wide Web (WWW), intranets, andextranets. The annex corrects errors, resolves ambiguities for which there is a cl
13、ear resolution that does not cause existingconforming documents to become non-conforming, and provides a choice of alternative resolutions for other ambiguities.Although motivated by the World Wide Web, applicability of this annex extends to all uses of SGML.This annex makes reference to groves and
14、property sets, which are defined in the SGML Extended Facilities of the 2nd Editionof HyTime (ISO/IEC 10744) and also in DSSSL (ISO/IEC 10179).K.1 ConformanceThe decision to conform to this annex is made for individual documents and is indicated in the SGML declaration, as describedbelow (K.3.2). An
15、 SGML system need not support this annex in order to be a conforming SGML system.This annex is organized as a set of replacement and new syntax productions and text, and is phrased in terms of modificationsto be made to the body of this International Standard, though the numbers of the affected clau
16、ses are not necessarily cited.However, these modifications are applicable only when conforming to this annex.An SGML parser that supports this annex shall be able to parse conforming SGML documents that do not claim conformanceto it. The parsing of such documents must produce the same grove as would
17、 a conforming SGML parser that does not supportthis annex. Error reporting for such documents, however, is with respect to the standard as modified by this annex; errors withrespect to the unmodified standard need not be reported.K.2 DefinitionsK.2.1 Definitions related to document type declarations
18、K.2.1.1 DTD declarations:Markup declarations that occur in a document type declaration subset.K.2.1.2 external subset:The portion of a document type declaration subset located within the external subset entity.K.2.1.3 internal subset:The portion of a document type declaration subset that occurs betw
19、een the dso and dsc of a document type declaration.If the dso and dsc are omitted, the internal subset is empty (rather than non-existent).K.2.1.4 external subset entity:The entity that is declared by the external identifier parameter of a document type declaration and referenced (implicitly) at the
20、end of the internal subset.K.2.2 Definitions related to document instancesK.2.2.1 fully-declared document instance:A document instance whose associated document type declaration contains sufficient markup declarations to express all of theDTD properties required for the instance by the body of this
21、International Standard, and that does not contain DTD data entitiesthat modify those properties.ISO 8879:1986/Cor.2:1999(E) ISO/IEC 1999 All rights reserved 3The document type declaration itself could be an implied declaration, as provided in clause K.4.9.Note 1: An SGML declaration requires documen
22、t instances to be fully-declared if it specifies IMPLYDEF ATTLIST NO andELEMENT NO ENTITY NO NOTATION NO. A system should offer means, such as a parameter to the invocation ofprocessing, to request validation of whether an instance is fully-declared even when the SGML declaration does not require it
23、to be.A document instance that is not fully-declared must be either a fully-tagged document instance or an amply-tagged documentinstance.K.2.2.2 fully-tagged document instance:A document instance in which a start-tag with a generic identifier, and an end-tag, are present for every element, and theat
24、tribute name is present in every attribute specification in the start-tag.Note 2: An SGML declaration requires document instances to be fully-tagged if it specifies DATATAG NO, RANK NO,OMITTAG NO, SHORTTAG STARTTAG EMPTY NO, and SHORTTAG ATTRIB OMITNAME NO. A system shouldoffer means, such as a para
25、meter to the invocation of processing, to request validation of whether an instance is fully-taggedeven when the SGML declaration does not require it to be.K.2.2.3 type-valid document instance:A document instance that conforms to such DTD properties as are required for it by the body of this Interna
26、tional Standard andthat are expressed in its associated document type declaration, either by markup declarations, DTD data entities, or both.K.2.2.4 amply-tagged document instance:A document instance whose use of markup minimization does not require access to a document type declaration.Note 3: An S
27、GML declaration requires document instances to be amply-tagged, insofar as they use minimization, if it specifiesDATATAG NO, RANK NO, SHORTTAG ATTRIB OMITNAME NO, and either IMPLYDEF ELEMENT NO orIMPLYDEF ELEMENT ANYOTHER. A system should offer means, such as a parameter to the invocation of process
28、ing, torequest validation of whether an instance is amply-tagged even when the SGML declaration does not require it to be.Note 4:End-tags can be omitted in an amply-tagged document instance, even for element types that have been declared bydefault as provided for in K.3.7.More precisely, an amply-ta
29、gged document instance can omit the end-tag for an element of an implicitly-declared typeby satisfying any of the three conditions - a), b), or c) - specified in 7.3.1.2. However, condition c) can be satisfiedonly when “IMPLYDEF ELEMENT ANYOTHER“ is specified in the SGML declaration and the element
30、is followedby another element of the same type.The following amply-tagged document instance illustrates these possibilities when “IMPLYDEF ELEMENTANYOTHER“ has been specified and there are no DTD declarations:Chapter titleFirst item in the listSecond item in the listThe end-tag for the first item in
31、 the list can be omitted because of condition c): This element is followed by an elementthat is not allowed in its content-in particular, another item.The end-tag for the second item in the list can be omitted because of condition b): This element is followed by theend-tag of another open element (t
32、he list).The end-tag for the chapter can be omitted because of condition a): This element is followed by the end of the SGMLdocument entity.ISO 8879:1986/Cor.2:1999(E)4 ISO/IEC 1999 All rights reservedK.2.2.5 immediately recursive element:An element whose immediate content includes a child subelemen
33、t of the same type.Note 5: In the following fully-tagged text, the first section element is immediately recursive while the first list element is not.The titleThe data.First outer list itemSecond outer list item, which contains an inner list.Inner list itemNote 6: A system should offer means, such a
34、s a parameter to the invocation of processing, to request validation that an instancecontains no immediately recursive elements even when the DTD would permit them.K.2.3 Definitions related to entity constraintsNote 7: An SGML system that supports unconstrained SGML documents must be able to parse D
35、TD declarations and resolveboth internal and external entity references. If it continues parsing (as a form of error-recovery) after failing to access areferenced entity, the results are unpredictable. Observing one or more of the entity constraints defined in this InternationalStandard may cause a
36、document to be more amenable to processing by a simpler SGML system, or in an environment (such asa network) where access to external entities may be slow or unreliable.K.2.3.1 integrally-stored document instance:A document instance in which every element and marked section ends in the entity in whi
37、ch it begins.Note 8: This constraint makes it possible, as a form of error-recovery, for parsing to continue in a fully-tagged documentinstance after a failure to access a referenced entity. The resulting grove will be the same for the parsed text, except for the treeaddresses of younger siblings of
38、 the nodes in the inaccessible entity. The constraint also has implementation benefits foreditors, “lazy“ replacement of entity references, and sharing of grove portions when entities are reused.K.2.3.2 reference-free document:An SGML document that has no entity references other than references to p
39、redefined data character entities.Note 9: A reference-free document can be parsed by conforming SGML systems that cannot resolve entity references.K.2.3.3 external-reference-free document:An SGML document that has no external entity references.Note 10: An external-reference-free document could have
40、attribute values that contain names of external entities or thatotherwise might cause an application to access an external entity by means other than entity references.Note 11: External-reference-free documents can be parsed by systems that cannot resolve external entity-references.ISO 8879:1986/Cor
41、.2:1999(E) ISO/IEC 1999 All rights reserved 5K.2.4 Other definitionsK.2.4.1 predefined data character entity:A general entity, associated with a character number in the syntax-reference character set, that is used to reference significantSGML characters as data.Note 12: In order to allow delimiter e
42、scaping when parsing without respect to DTD declarations, there should be a predefineddata character entity for the first character of each delimiter string that can be recognized in a mode where data can occur.K.2.4.2 white space:The characters assigned to the SEPCHAR, SPACE, RE, and RS functions.K
43、.2.4.3 mandatorily empty element:An element of a type declared EMPTY, or that is forced to be EMPTY by an explicit content reference attribute.K.2.5 Definitions related to DTD notationsK.2.5.1 DTD notation:A data notation that is capable of expressing DTD properties.Note 13: This International Stand
44、ard provides markup declarations as the means of expressing DTD properties. It also allowsthe use of DTD notations, but does not define any.Note 14: A DTD notation can also be capable of expressing other information. For example, it could express constraints on adocuments data content or structure t
45、hat cannot be expressed by markup declarations but could be validated by an application.However, it is not a reportable markup error if the document fails to conform to such additional constraints.Note 15: DTD notations are used in DTD data entities.K.2.5.2 DTD properties:Classes and properties that
46、 are specifiable by markup declarations. They are defined by the following grove plan:DTD Properties Grove PlanClasses and properties that are specifiable by DTD declarations. Theyare needed to parse and validate a document instance.prlgabs0 prlgabs1 dtgabs rankabs srabs subdcabsfpiabs arcabs fsiabs
47、 dafeabs gadcabs pelementsgmldoc doctpdclappinfo epilogK.2.5.3 Parameter entity (4.225)An entity that is either the external subset entity, or that is declared with a parameter entity name.ISO 8879:1986/Cor.2:1999(E)6 ISO/IEC 1999 All rights reservedK.2.5.4 DTD data entity:An external parameter enti
48、ty whose declaration includes a notation name.Note 16: The notation name should be that of a DTD notation and the entity content should describe DTD properties.K.3 SGML declaration171 SGML declaration =“In order for SGML documents to be self-identifying, it is strongly recommended that all conformin
49、g SGML documents containone of the forms of SGML declaration.K.3.1 SGML declaration reference171.1 SGML declaration reference =name, external identifier?where:“name“ is a name in the reference concrete syntax.“external identifier“ must reference an SGML declaration body. Ifomitted, the external identifier is “SYSTEM“.An external identifier, if it is a formal public identifi
