 |  | 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)
Documents, meta-DTDs, and architecture engines may all conform to this Annex. In addition, this Annex distinguishes validating architecture engines from conforming architecture engines that do not provide complete validation of documents and meta-DTDs against the provisions of this Annex.
A meta-DTD that uses the AFDRMeta extensions shall so indicate by including the following invalid markup declaration as near as practicable to the start of the meta-DTD and before any use of the AFDRMeta extensions:
<!AFDR "ISO/IEC 10744:1997">
A meta-DTD that does not use the AFDRMeta extensions is a valid meta-DTD if the declarations it contains are valid SGML markup declarations.
Documents and meta-DTDs derived from a conforming architecture should so indicate by including the following statement in the architecture support notation declaration:
A base architecture used in conformance with the Architectural Form Definition Requirements of International Standard ISO/IEC 10744.
Conforming architecture engines may be either general or architecture specific. A general architecture engine supports architectural processing independent of the semantics of any architecture. Architecture-specific engines provide architectural processing only for those architectures for which they are designed.
If an architecture engine meets the requirements of this sub-clause it is a conforming architecture engine.
Either form of architecture engine may be a validating architecture engine.
A conforming architecture engine shall require its documents to be conforming SGML documents, and shall not prohibit any markup that ISO 8879 and this Annex would allow in such documents.
NOTE 437 For example, an application markup convention could recommend that only certain minimization functions be used, but could not prohibit the use of other functions if they are allowed by the formal specification.
A conforming architecture engine's documentation shall meet the requirements of this International Standard (see 11.5 Documentation requirements).
A conforming architecture engine shall not enforce application conventions as though they were requirements of this International Standard.
NOTE 438 Warnings of the violation of application conventions can be given, but they must be distinguished from reports of architecture errors.
A validating architecture engine shall find and report a reportable architectural error (RAE) if one exists, and shall not report an error when none exists. Such engines can optionally report other errors and may warn of conditions that are potentially, but not necessarily, errors.
Reports of architecture errors, including optional reports, shall be identified as architecture messages in such a manner as to distinguish them clearly from all other messages, including warnings of potential architecture errors.
A report of a architecture error, including an optional report, shall state the nature and location of the error in sufficient detail to permit its correction.
NOTE 439 This requirement is worded to allow implementors maximum flexibility to meet their user and system requirements.
An architecture system declaration is an SGML system declaration as defined in ISO 8879, modified as indicated in this subclause.
A new parameter, AFDR support (AFDR), specifies whether or not the system is a validating architecture engine and whether or not it is capable of producing architectural instances. This parameter follows the SDIF support parameter of an SGML declaration when used for architecture engines.
| AFDR support options = | ||
"AFDR", ps+, "VALIDATE", ps+ ( "YES" | "NO" ), ps+, "CONSTRUCT", ps+ ( "YES" | "NO" ) | ||
means that all reportable architectural errors will be found and reported.
means that the engine is capable of creating architectural instances from client documents.
| Next Clause | Previous Clause |
| 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. | |
HTML generated from the original SGML source using a DSSSL style specification and the SGML output back-end of the JADE DSSSL engine.