![]() | ![]() | 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 | |||
Some facilities define their own conformance requirements and methods of indicating their use and their options, if any. In addition, the use of any of the facilities must conform to the following general requirements.
A conforming SGML Extended Facilities application's conventions can affect only areas that are left open by these facilities to specification by applications.
A conforming SGML Extended Facilities application shall require its documents to be conforming SGML documents, and shall not prohibit any markup that this International Standard would allow in such documents.
NOTE 378 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 SGML Extended Facilities system's documentation shall meet the requirements of this annex.
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 Extended Facilities programs; and
in all promotional and training material.
For applications, the identification text is:
An SGML Extended Facilities application conforming to Annex A of International Standard ISO/IEC 10744 -- Hypermedia/Time-based Structuring Language
For systems, the identification text is:
An SGML Extended Facilities system conforming to Annex A of International Standard ISO/IEC 10744 -- Hypermedia/Time-based Structuring Language
The documentation for a conforming SGML Extended Facilities system shall include the relevant system declarations or definition documents.
NOTE 379 For example, a storage manager definition document for Formal System Identifiers.
The documentation shall distinguish Extended Facilities constructs from application conventions and system functions, and shall identify the Extended Facilities constructs as being part of the facility used.
NOTE 380 The objective of this requirement is for the user to be aware of which constructs are common to all Extended Facilities systems, and which are unique to this one. This will reduce the experienced user's learning time for a new system or application.
This International Standard and annex shall be cited as a reference for supported Extended Facilities constructs that are not specifically documented for the system or application. For example, if, for simplicity's sake, only a subset of some function is presented, it shall be stated clearly that other options exist and can be found in this International Standard.
All Extended Facilities constructs shall be introduced using the terminology of this International Standard, translated to the national language used by the publication or program.
Such standard terminology should be used throughout the documentation. If, notwithstanding, a non-standard equivalent is used for a standard term, it must be introduced in context and it shall not conflict with any standard Extended Facilities terms, including terms for unsupported or undocumented constructs.
A conforming SGML Extended Facilities system shall not enforce application conventions as though they were requirements of this annex.
NOTE 381 Warnings of the violation of application conventions can be given, but they must be distinguished from reports of facility errors.
| 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.