| Title: | Disposition of comments report on ISO/IEC FCD 13240 |
| Source: | David Cooper, Editor of ISO/IEC 13240 |
| Project: | JTC 1.34.43 (ISMID) |
| Project editor: | David Cooper |
| Status: | Editor's submission |
| Action: | Text for SC34 approval |
| Date: | 27 February 2001 |
| Summary: | |
| Distribution: | SC34 and Liaisons |
| Refer to: | SC34 N 64 Final DIS Ballot for ISO/IEC 13240 (ISMID), SC34 N 201 Final text of ISO/IEC 13240 (ISMID) |
| Supercedes: | |
| Reply to: | Dr. James David Mason (ISO/IEC JTC1/SC34 Chairman) Y-12 National Security Complex Information Technology Services Bldg. 9113 M.S. 8208 Oak Ridge, TN 37831-8208 U.S.A. Telephone: +1 423 574-6973 Facsimile: +1 423 574-1896 E-mailk: mailto:mxm@y12.doe.gov http://www.y12.doe.gov/sgml/sc34/sc34oldhome.htm Ms. Sara Hafele, ISO/IEC JTC 1/SC 34 Secretariat American National Standards Institute 11 West 42nd Street New York, NY 10036 Tel: +1 212 642 4976 Fax: +1 212 840 2298 E-mail: shafele@ansi.org |
Comments were received from the National Body of Japan.
Clause 8 of ISMID gives the reason for leaving HyFunk in Conformance clause 2, namely that it is a minimum requirement that is anticipated to be adequate for some documents. The DSSSL expression language is the default in the architecture (9.11.7) because it is a richer and more general language. HyFunc remains part of the HyTime standard.
Clause 8 has, however, been modified to clarify the relationship (see italics in sections from clause 8 quoted below).
"A conforming ISMID system shall, at a minimum, support the HyTime Marker Function Language (HyFunk) expression language. This expression language is adequate for documents that require only integer arithmetic operations. HyFunk is a subset of the DSSSL expression language."
" If a richer set of expressions are required, the ISMID system shall support the expression language described in clause 8 of the DSSSL standard."
" It is also important to recognize that any static source of data (i.e., any document in the SGML sense) can be made interactive through the application of behavioral style. Throughout this standard the term interactive document is used when referring to the presentation of the source data (i.e., when referring to a document that has been dynamically rendered)."
In addition, the definition of "interactive document" in Clause 4 (Definitions) has been modified as follows for consistency."A particular presentation of static SGML source data, dynamically rendered for viewing by a particular user. It typically contains instructions that define the rules of its own presentation."
The style used herein is modeled after the style used in other standards, such as HyTime. The full English name is in bold type to distinguish it from usual terms in main texts. The style is as follows:
The current document indicates HyFunc and DSSSL as expression languages, and it specifies that DSSSL is default in 9.11.7 and that HyFunc is mandatory in 2. HyFunc is a subset of DSSSL and redundant.
DSSSL should be specified to be mandatory in 2. Conformance, and HyFunc should be removed from expression language alternatives.
External objects are a kind of interface objects and are important constituents in ISMID. No definition, however, are given in 4. Definitions.
The following definition should be added:
external objects
A type of interface objects which are used to allow an interactive document to communicate with external systems.
References of clauses should contain clause numbers.
For example,
* "clause The ISMID architecture" in the 2nd line of the 1st paragraph in 1.1.1 should be "clause 9. The ISMID architecture".
* "Simple ISMID Application Definition Document (Informative)" in the 1st line of the 1st paragraph in 1.1.2 should be "Annex B. Simple ISMID Application Definition Document (Informative)".
Other references should be rewritten in the same way as above.
The 3rd line in the 2nd paragraph contains unnecessary symbol "(1)". This symbol should be removed.
RCS (used in 6.1) and AFDR (used in 6) should be added in 5.
The expression style of full construct names in English for elements and attributes is not clear; it cannot be distinguished from usual terms in main texts. See the example below.
The proposed styles are
* The element/attribute SGMLname ("full construct name")
...
or
* The SGMLname ("full construct name") element/attribute
...
For example, the 2nd sentence in 9.3,
The reference content does not exist (ContentNotExist) attribute determines how the system shall handle ...
should be replaced with
The ContentNotExist ("reference content does not exist") attribute determines how the system shall handle ...
The year indication in HyTimePUBLIC should be 1997 instead of 1992 because HyTime published in 1997 is referred to.