[Mirrored from: http://www.allette.com.au/allette/ricko/1861.htm]
|TITLE:||Proposed TC for Extended Naming Rules and Development Principles for SGML|
|PROJECT EDITOR:||Charles F. Goldfarb|
|STATUS:||WG8 approved draft|
|ACTION:||For balloting as TC to ISO 8879:1986|
|SUMMARY OF MAJOR POINTS:||This
Technical Corrigendum adds brief annexes to ISO 8879 for the following purposes:
This TC does not affect existing SGML documents or products. It affects only those SGML documents and products that choose to support the extended naming rules option.
|DATE:||24 May 1996|
|DISTRIBUTION:||WG8 and Liaisons|
|REFER TO:||WG8 N1854|
|REPLY TO:||Dr. James D.
(ISO/IEC JTC1/SC18/WG8 Convenor)
Oak Ridge National Laboratory
Information Management Services
Bldg. 2506, M.S. 6302, P.O. Box 2008
Oak Ridge, TN 37831-6302 U.S.A.
Telephone: +1 423 574-6973
Facsimile: +1 423 574-6983
Add the following two normative annexes to ISO 8879.
This annex describes an optional extension of SGML known as the "Extended Naming Rules". The extension should be used only in SGML documents for which the normal naming rules are unsuitable (usually because of the size of the natural language character set). An SGML system need not support these Extended Naming Rules in order to be a conforming SGML system.
This annex is phrased in terms of revisions to be made to the body of this International Standard. However, these revisions are applicable only when the Extended Naming Rules are in use.
To distinguish SGML declarations that use this extension from those that do not, the minimum literal in productions  and  of ISO 8879:1986 must be modified to read "ISO 8879:1986 (ENR)". To accomplish this add the following sentence to the paragraph immediately following production  and to the second paragraph following production :
However, when extended naming rules are used, the minimum data must be "ISO 8879:1986 (ENR)".
For many languages the distinction made in production  between uppercase and lowercase is not relevant. It is, therefore, necessary to modify clause 13.4.5 to allow for both an extended character set and for the use of character sets that do not have different cases. The changes required, in the order of their occurrence in 13.4.5, are:
 naming rules = "NAMING", ps+, "LCNMSTRT", (ps+, extended naming value)+, "UCNMSTRT", (ps+, extended naming value)+, ("NAMESTRT", (ps+, extended naming value)+)?, "LCNMCHAR", (ps+, extended naming value)+, "UCNMCHAR", (ps+, extended naming value)+, ("NAMECHAR", (ps+, extended naming value)+)?, "NAMECASE", ps+, "GENERAL", ps+, ("NO"| "YES"), ps+, "ENTITY", ps+, ("NO"| "YES")
[189.1] extended naming value = parameter literal | character number | character range
A character number may be used to specify a character that is defined in the syntax-reference character set but is not permitted in an SGML declaration.
[189.2] character range = character number, ps*, "-", ps*, character number
Specifying a character range is equivalent to specifying every character number from (and including) the character number that starts the range to (and including) the character number that ends the range.
The future development of ISO 8879 shall be consistent with the following principles:
NOTE 1 -- These principles should not be construed to mean that no changes can be made to ISO 8879. To meet evolving user requirements, for example, some changes of the following types are possible without violating the above principles:
NOTE 2 -- Future versions of this standard can introduce additional requirements as well.
NOTE 3 -- These principles should not be construed to mean that the definition of a "conforming SGML document" cannot be changed, only that existing conforming SGML documents will continue to be classified as such.