Introduction

This technical corrigendum corrects errors of fact and omissions in ISO/IEC 10744:1997 as published in August 1997.

The TC is organized by clause.

Clause 3 Definitions

Add the following definition:

entity body

The information provided by an entity manager to the SGML parser or processing application.

Clause 6 Base Module

Clause 6.5.1 HyTime bounded object set attributes

Modify the second paragraph by splitting it between the first and second sentences. Insert the following paragraph between two new paragraphs:

The entity discovery process only examines the declarations in entities whose entity body is unique within the HyTime BOS. An entity's body is not unique if the storage manager that resolves the system identifier reports that the body it provides to the entity manager is identical to the result of resolution of the system identifiers of any entities already examined. If an entity's body is not unique, the entity is not included in the HyTime BOS. If the HyTime BOS is used as the basis for defining packages for interchange (such as SDIF packages), the package must be defined so that the identity of entity bodys for different entities declared by documents in the package is maintained. In the HyTime semantic grove, the BOS property of the Hyperdoc node will include one grove for each unique source data/grove constructor pair. Thus, there may not be a one-to-one correspondence between entities in the HyTime BOS and groves in the BOS property of the Hyperdoc node.

Clause 6.5.3 Bounded object set exception specification

Remove note 108

clause 6.8.6 HyTime Marker Function Language (HyFunc)

In the production for the dimref function, change '("selcomp: ("' to '("selcomp:" ('.

In the production for the dimref function, change keyword following '"axisspec:"' from "IDREF" to "NAME".

Clause 7 Location Address Module

7.7.3

Change the paragraph starting "A resolution level is specified..." by deleting the word "non-zero".

Add note 171.a: Specifying a reference resolution level of zero is functionally equivalent to using a reference range of "D" (direct references only).

Modify the lexical type specification comment in the declaration of the reflevel attribute to be: (("#ALL", [0-9]+)?, (ATTORCON, [0-9]+)*)

7.8 Reference location address

Add the following entries to the list of loctype keywords:

ENTLOC

The attribute value is interpreted as a name-space location in the location source document's "entities" name space.

PROPLOC

The attribute value is interpreted as a property location address of the property (of the location source) named by the attribute. Requires support for the proploc option.

BIBLOC

The attribute value is interpreted as a bibliographic location. If the attribute has a reference location source, it must also be a BIBLOC and is interpreted as for the bibsrc attribute of the bibloc element form.

Add the string '"ENTLOC"|"PROPLOC"|"BIBLOC"' to the lexical type comment in the declaration of the loctype attribute.

Modify the example in note 176 by changing the declaration of the target attribute from 'IDREFS' to 'NAMES'.

Clause 8 Hyperlinks Module

Clause 8.2

Before clause 8.2.1, insert a new clause 8.2.0:

8.2.0 Hyperlink type

The attribute form hyperlink type (linktype) specifies the link type of the hyperlink. If a linktype attribute is not specified the element type of the hyperlink is the link type.

<![%hylink;[
 <!ENTITY % linktype "INCLUDE" >
]]>
<![%clink;[
 <!ENTITY % linktype "INCLUDE" >
]]>
<![%agglink;[
 <!ENTITY % linktype "INCLUDE" >
]]>
<![%varlink;[
 <!ENTITY % linktype "INCLUDE" >
]]>
<![%ilink;[
 <!ENTITY % linktype "INCLUDE" >
]]>
<!ENTITY % linktype "IGNORE" >
<[ %linktype; [

             <!-- Hyperlink type -->
<!attlist
   (hylink,clink,agglink,varlink,ilink)
   linktype         -- Hyperlink link type --
      NAME
      #IMPLIED      -- Default: Element type of hyperlink element --
                    -- Constraint: For hylink,agglink, clink, ilink
                       anchor role/link-type pairings must be
                       constant for the link type --
>
]]><!-- linktype -->

Clause 8.2.1 Hyperlink

Replace the attributes comment in the declaration of the hylink element form with this line:

-- Attributes [links]: linktype, hylink --

Clause 8.2.2 Contextual link

Replace the attributes comment in the declaration of the clink element form with this line:

-- Attributes [links]: clink, linktype --

Add the following line to the attribute list declaration for the clink element form before the MDC:

   listtrav CDATA     "N"

Clause 8.2.3 Aggregation link

Replace the attributes comment in the declaration of the agglink element form with this line:

-- Attributes [links]: agglink, linktype  --

Clause 8.2.4 Variable link

Replace the attributes comment in the declaration of the varlink element form with this line:

-- Attributes [links]: ancspcat, linktype, 
varlink, vartrav --

Clause 8.2.5 Independent link

Replace the attributes comment in the declaration of the ilink element form with this line:

-- Attributes [links]: ilink, linktype --

Clause 8.3.1 Hyperlink location address

Modify the second constraint comment in the element declaration for the HyLnkLoc notation to read:

-- Constraint: csnames and 
literals must be link
                     types in location source. --

Modify the second constraint comment in the element declaration for the linkloc element form to read:

-- Constraint: csnames and literals must be link
                     types in location source. --

Clause 9 Scheduling Module

9.8.1 Implicit dimension reference

Add the following sentence after the third sentence of the first paragraph:

If the event is the first event in an event schedule, the omission of the first marker is an implicit dimension reference to the first quantum of the axis.

Clause A.3 Architectural Form Definition Requirements (AFDR)

Corrections yet to be identified.

Clause A.4 Property Set Definition Requirements (PSDR)

Clause A.4.1.2 Classes and properties

Add the following entry to the list of declared data types:

byteseq

An ordered sequence of bytes

Modify the paragraph following the list of declared data types to read: The node, enum, character, string, integer, compname, and byteseq datatypes are known as "primitive datatypes"; the nodelist, strlist, intlist, and cnmlist datatypes are known as "list datatypes".

Clause A.4.1.5 Content trees

Modify the first sentence of the last paragraph of the clause to read: If the content property of a node is a character, string, or byte sequence property, the property is also known as the "data property" of the node.

Clause A.4.2.3 Class definition

Modify the constraint comment of the conprop attribute to read: Constraint: RCS name of nodal property of class with noderel=subnode, char property, string, or byte sequence

Clause A.4.2.4 Property definition

Add "|byteseq" to the end of the list of enumeration keywords in the declaration of the datatype attribute

Clause A.4.4.1.1 The Value-To-Node property set

Modify the last sentence of the second paragraph to read: The value properties of the char, string, byteseq, and list classes are also the content properties of those classes.

Add the following class definition at the end of the VTN property set definition document:

<classdef rcsnm=byteseq>

<propdef rcsnm=srcprop appnm="source property" compname>

<propdef rcsnm=value byteseq>

Clause A.4.5.3 Constraints on CGR source construction

Add the following entries to the list of primitive data type string representations:

boolean

The string "#t" for true, "#f" for false.

byteseq

For each byte of the sequence, a pair of characters representing a two-digit hexidecimal number, high-order bits first.

Clause A.5 General Architecture

Clause A.5.2 Common attributes of elements

Add the following constraint comment to the declaration of the etfullnm attribute:

         -- Constant --

Clause A.6 Formal System Identifiers Requirements (FSIDR)

Clause A.6.4.2 FSI declaration

In the last paragraph of this clause, remove the duplicated text "The name is always "FSIDR" in meta-DTDs. It should also be "FSIDR" in DTDs or LPDs, but provision is made for changing it in the"

Clause A.7 SGML Property Set

Add the following property to the definition of the notation class in prolog abstract 0:

<propdef 
subnode rcsnm=dfltatts appnm="default attributes"
datatype=nmndlist ac=attasgn acnmprop=name>

Modify property set to reflect changes caused by Web SGML TC to ISO 8879.

Clause C.2 HyTime Meta-Declarations

Update the meta declarations to reflect the changes as specified above (this is an automatic process as the meta-DTD is generated from the source for the other clauses).