 |  | 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 | |||
Documents, applications, and systems may all conform to this Annex.
If a General Architecture document complies with all provisions of this Annex and is a conforming SGML document as defined in ISO 8879, it is a conforming General Architecture document.
A conforming General Architecture document is a minimal General Architecture document if its General Architecture declarations are as follows:
<!Notation
GenArc -- General Architecture --
-- A base architecture used in conformance with the
Architectural Form Definition Requirements of
International Standard ISO/IEC 10744. --
PUBLIC "ISO/IEC 10744:1997//NOTATION AFDR ARCBASE
General Architecture//EN"
>
<!Attlist #NOTATION
GenArc -- General Architecture --
ArcFormA NAME GAForm
ArcNamrA NAME GANames
ArcSuprA NAME GASupr
ArcIgnDA NAME GAIgnD
ArcDocF NAME GADoc
ArcDTD CDATA "GenArc"
-- NAMELEN must be at least 9 because the General Architecture
meta-DTD uses 8-character parameter entity names. --
ArcQuant CDATA #FIXED "NAMELEN 9"
ArcDataF NAME GABrid
ArcBridF NAME GABrid
ArcAuto (ArcAuto|nArcAuto) ArcAuto
ArcOptSA NAMES #FIXED "commatts dcnatts"
>If a General Architecture application meets the requirements of this sub-clause and is a conforming SGML application as defined in ISO 8879, it is a conforming General Architecture application.
A conforming General Architecture application's conventions can affect only areas that are left open to specification by applications.
NOTE 488 Some examples are: names of element types conforming to General Architecture architectural forms, and substitute attribute names.
A conforming General Architecture application shall require its documents to be conforming General Architecture documents, and shall not prohibit any markup that this International Standard would allow in such documents.
NOTE 489 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.
If a General Architecture system meets the requirements of this sub-clause and is a conforming SGML system as defined in ISO 8879, it is a conforming General Architecture system.
A conforming General Architecture system's documentation shall meet the requirements of this International Standard (see 11.5 Documentation requirements).
A conforming General Architecture system shall be capable of processing any conforming General Architecture document that is not inconsistent with the system's General Architecture system declaration (see A.5.9 General Architecture system declaration). A conforming General Architecture system shall report every unsupported General Architecture facility used in any General Architecture document it processes.
NOTE 490 A system's inability to process data content notations that are not defined in this International Standard does not affect whether it is a conforming General Architecture system.
A conforming General Architecture system shall be capable of processing a minimal General Architecture document.
A conforming General Architecture system shall not enforce application conventions as though they were requirements of this International Standard.
NOTE 491 Warnings of the violation of application conventions can be given, but they must be distinguished from reports of General Architecture errors.
If a General Architecture engine in a conforming General Architecture system meets the requirements of this sub-clause, it is a validating General Architecture engine.
NOTE 492 A conforming General Architecture system need not have a validating General Architecture engine. Implementors can therefore decide whether to incur the overhead of validation in a given system.
A validating General Architecture engine shall find and report a reportable General Architecture error if one exists, and shall not report an error when none exists.
A validating General Architecture engine can optionally report other errors.
NOTE 493 This International Standard does not specify how a General Architecture error should be handled, beyond the requirement for reporting it. In particular, it does not state whether the erroneous information should be treated as data, and/or whether an attempt should be made to continue processing after an error is found.
NOTE 494 This International Standard does not prohibit a validating General Architecture engine from reporting an error that this International Standard considers non-reportable if the engine is capable of doing so. Neither does it prohibit an engine from recovering from such errors, nor does it require an engine to report them when it is not performing validation.
A validating General Architecture engine may warn of conditions that are potentially, but not necessarily, errors.
NOTE 495 General Architecture architectural forms do not constrain the construction of document type definitions, only document instances. However, a validating General Architecture engine can optionally report DTD constructs that would prevent the creation of a valid conforming instance, or that would allow the creation of a nonconforming instance.
Reports of General Architecture errors, including optional reports, shall be identified as General Architecture messages in such a manner as to distinguish them clearly from all other messages, including warnings of potential General Architecture errors.
A report of a General Architecture error, including an optional report, shall state the nature and location of the error in sufficient detail to permit its correction.
NOTE 496 This requirement is worded to allow implementors maximum flexibility to meet their user and system requirements.
Standard identification shall be in the natural language of the documentation.
Standard identification text shall be displayed prominently:
in a prominent location in the front matter of all publications (normally the title page and cover page);
on all identifying display screens of HyTime programs; and
in all promotional and training material.
For applications, the identification text is:
A General Architecture application conforming to the General Architecture Annex of International Standard ISO/IEC 10744 -- Hypermedia/Time-based Structuring Language
For systems, the identification text is:
A General Architecture system conforming to the General Architecture Annex of International Standard ISO/IEC 10744 -- Hypermedia/Time-based Structuring Language
The documentation for a conforming General Architecture system shall include a General Architecture system declaration (see A.5.9 General Architecture system declaration).
| 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.