 |  | 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 | |||
If a HyTime engine in a conforming HyTime system meets the requirements of this sub-clause, it is a validating HyTime engine.
NOTE 370 A conforming HyTime system need not have a validating HyTime engine. Implementors can therefore decide whether to incur the overhead of validation in a given system. A user whose multimedia authoring system allowed the validation and correction of HyTime documents, for example, would not require the validation process to be repeated when the documents are rendered by a processing system.
A validating HyTime engine shall find and report a reportable HyTime error if one exists, and shall not report an error when none exists.
A validating HyTime engine can optionally report other errors.
NOTE 371 This International Standard does not specify how a HyTime 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 372 This International Standard does not prohibit a validating HyTime 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 HyTime engine may warn of conditions that are potentially, but not necessarily, errors.
NOTE 373 For example, several events that occupy the same position in a coordinate space.
NOTE 374 HyTime architectural forms do not constrain the construction of document type definitions, only document instances. However, a validating HyTime 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 HyTime errors, including optional reports, shall be identified as HyTime messages in such a manner as to distinguish them clearly from all other messages, including warnings of potential HyTime errors.
A report of a HyTime error, including an optional report, shall state the nature and location of the error in sufficient detail to permit its correction.
NOTE 375 This requirement is worded to allow implementors maximum flexibility to meet their user and system requirements.
| 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.