![]() | ![]() | Copyright © 1992, 1997 International Organization for Standardization. All rights reserved. This electronic document is for use during development and review of International Standards. Official printed copies of International Standards can be purchased from the ISO and the national standards organization of your country. | ||
| Next Clause | Previous Clause | |||
A.3 Architectural Form Definition Requirements (AFDR)
A document indicates conformance to architectures by using an architecture base declaration (ArcBase).
An ArcBase declaration identifies one or more base architectures of a DTD or a derived meta-DTD. It cannot be used in a meta-DTD that is not derived. It should precede the architecture support declarations pertaining to the base architectures that it identifies. There can be more than one ArcBase declaration in a DTD or meta-DTD.
Syntactically, the ArcBase declaration is a processing instruction (PI), not an SGML markup declaration. In the template below, it is shown in the reference concrete syntax. In use, the ArcName-list parameter must be replaced by one or more architecture names (ArcName) declared as notation names, separated by SGML s separators (white space). It is an RAE if the DTD or meta-DTD does not declare a notation for each ArcName specified..
The declaration name is the character string following the initial keyword "IS10744" and one or more s separators, up to the first s separator. The declaration name is subject to upper-case substitution if the SGML declaration of the client document specifies general upper-case substitution.
The name is normally "ArcBase" but it can be changed using the APPINFO parameter of the SGML declaration, if necessary, to avoid the (admittedly unlikely) possibility of conflicts when retrofitting an architecture to a document that already has PIs that begin with "IS10744 ArcBase " (see A.3.3.1 Enabling architecture use of APPINFO parameter).
The ArcBase declaration will only be recognized in the DTDs and LPDs with respect to which the document is being parsed.
<!-- Architecture Base Declaration -->
<!-- TEMPLATE FOR PI IN DTD OR DERIVED META-DTD -->
<?IS10744 ArcBase ArcName-list >To determine when enabling architectures are in use, the APPINFO parameter of the SGML declaration is parsed as a space-delimited sequence of tokens. Conformance of a document to one or more architectures defined in accordance with these requirements is indicated by specifying the keyword "ArcBase" as such a token. The keyword indicates the potential presence in one or more DTDs or LPDs of an architecture base (ArcBase) declaration that identifies the "architecture support declarations" for the architectures on which the DTD is based. The use of the APPINFO parameter to indicate conformance to an architecture is optional.
NOTE 412 The use of APPINFO serves to declare the use of architectures within SGML declarations. However, it is sufficient to enable architectural processing to declare the use of an architecture with the ArcBase declaration within DOCTYPE declarations.
The format of the token is:
ArcBasewhere "ArcBase" is not case-sensitive. The token can also specify the name of the ArcBase declarations in the document's DTDs and LPDs if it is other than "ArcBase". The format is:
ArcBase ArcBase="NewBase"
The APPINFO parameter is interpreted as an s-separator-delimited list of tokens.
Specification of the ArcBase name to be used in documents is optional when the name of the ArcBase declarations is ArcBase.
| Next Clause | Previous Clause |
HTML generated from the original SGML source using a DSSSL style specification and the SGML output back-end of the JADE DSSSL engine.