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 between definitions 3.26 and 3.27:

3.26.1 entity body

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

Clause 6 Base Module

Clause 6.3 HyTime support declarations

In note 94, replace the example attribute specification with:

    base     CDATA    "desctxt"
    sched    CDATA    "sched"

Replace 'manyaxes="3"' with

    manyaxes NUMBER   "3"

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

Clause 7.7.3 Reference resolution level

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", NUMBER+)?, (ATTORCON, NUMBER+)*)

Clause 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 7.9.6 Name list specification

Modify the attribute definition list for the nmlist form by adding an apropsrc attribute so as to read:

<!attlist
   nmlist         -- Name list specification --
                  -- Clause: 7.9.6 --

   HyBase   NAME     #FIXED nmsploc
   impsrc   NAME     #FIXED grovert
   apropsrc NAME     "apropsrc"
   HyBnames CDATA    #FIXED "locsrc docorsub
                             namespc nametype
                                #MAPTOKEN elements element
                                #MAPTOKEN entities entity"

   nametype       -- Name-space from which nodes are selected --
      (entity|element)
      entity

   docorsub       -- Document or subdocument location source --
      ENTITY
      #IMPLIED

   notspace       -- If nmspace name is invalid? --
      NAME        -- Lextype: ("ERROR"|"IGNORE") --
      ERROR

   notname        -- If name is not valid in nmspace? --
      NAME        -- Lextype: ("ERROR"|"IGNORE") --
      ERROR
>

Clause 8 Hyperlinks Module

Clause 8.2 Hyperlink architectural forms

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 name of the hyperlink is the link type.

           <!-- Hyperlink Type -->
<[ %linktype; [
<!attlist
-- linktype --    -- Hyperlink type --
                  -- Clause: 8.2.0 --
   (clink,hylink,ilink,varlink)

   linktype       -- Hyperlink link type --
      NAME
      #IMPLIED    -- Default: GI of client element --
                  -- Constraint: For clink, hylink, and ilink anchor
                     role/link-type pairings must be constant for the
                     link type --
>
]]><!-- linktype -->

Modify the marked sections surrounding the clink, hylink, and ilink forms by adding the following line immediately before the marked section close. Also add the line immediately following the declaration of the ancspcat attribute form, followed by a blank line.

<!entity % linktype "INCLUDE">

Clause 8.2.1 Hyperlink

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

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

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 first paragraph with the following paragraph:

The link type aggregation link (agglink) represents the grouping of a list of nodes into an "aggregate". The aggregate represents the list of members as a whole, providing the semantic that the list of members can be treated as a single object.

Add the following paragraph before note 248:

The element forms agglink and agglinkv provide the two possible syntax variants of aggregation links. They are semantically equivalent.

Add missing comment close delimiter to the "Attributes [links]:" comment.

Modify the second line of the agglink attribute list declaration to read:

   agglink        -- Aggregation link (hylink syntax variant) --

Add the following declarations before the end of the agglink marked section:

<!element
   agglinkv       -- Aggregation link (varlink syntax variant) --
                  -- Clause 8.2.3 --
   - O
   (aggmem)+

-- Attributes [links]: agglinkv --
-- OptionalAttributes [links]: vartrav --
-- CommonAttributes [GenArc]: dafe, dvlatt, etfullnm, id,
   ireftype, lextype, opacity --
-- CommonAttributes [base]: activity, conloc, dtxtatt, valueref --
-- CommonAttributes [locs]: refctl, refloc, reftype, rflocspn --
>
<!attlist
   agglinkv       -- Aggregation link (varlink syntax variant) --
                  -- Clause 8.2.3 --

   HyBase   NAME     #FIXED varlink
   anchrole CDATA    #FIXED "agg"
   anchcstr NAMES    "self"
>
<!element
   aggmem         -- Aggregation link member --
                  -- Clause 8.2.3 --
   (#PCDATA|%HyCFC;)*

-- Attributes [links]: aggmem --
-- OptionalAttributes [links]: vartrav --
-- CommonAttributes [GenArc]: dafe, dvlatt, etfullnm, id,
   ireftype, lextype, opacity --
-- CommonAttributes [base]: activity, conloc, dtxtatt, valueref --
-- CommonAttributes [locs]: refctl, refloc, reftype, rflocspn --
>
<!attlist
   aggmem         -- Aggregation link member --
                  -- Clause 8.2.3 --

   HyBase   NAME     #FIXED anchspec
   anchrole CDATA    #FIXED "members"
   multmem  NAME     "list"
   emptyanc NAME     #IMPLIED
   loctype  CDATA    "#CONTENT IDLOC"
>

Editor's Comment (PJN): should agglink allow user-specifiable traversal rules? If so, then should it get those attributes via vartrav, or should it just have

   linktrav NAME     #IMPLIED
   listtrav NAME     #IMPLIED

or something similar in its own attribute list? There's a number of things that'll have to be done either way (and it can't just stay the way it is now), but the latter would be easier in terms of number of changes to the marked section magic.

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 --
-- OptionalAttributes [links]: vartrav --

Replace the "Default:" comments for the anchrole attribute definition of the ancspcat attribute form with:

      #IMPLIED    -- Default: for anchspec, anchor role is GI of
                     client element; for varlink, varlink is not self
                     anchor --

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

Clause 9.4.5 Scheduled extent list

Add missing comment close delimiter to the "Attributes [sched]:" comment.

Clause 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)

Clause A.3.5.2 Architectural attribute renamer

Add the following paragraph following note 424:

If the substitute name is "#GI", the value of the attribute is the element type name of the client element.

Replace the paragraph following node 425 with this paragraph:

Architectural syntactic data content can be entered as an attribute value (or GI) by specifying the architectural attribute name as "#ARCCONT" and naming the client attribute in whose value it will occur or specifying #GI to use the client element type name as the architectural content. In this case, any syntactic content in the client document is considered non-architectural (unless separately mapped to an attribute with the #CONTENT keyword).

Modify the Lextype comment for the ArcNames attribute in the architectural attribute renamer element attribute list declaration template to read:

                  -- Lextype: ((NAME,(ATTORCON|"#GI"|"#DEFAULT"),
                                ("#MAPTOKEN", NMTOKEN, NMTOKEN)*)|
                               ("#ARCCONT",(ATTNAME|"#GI")))* --

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 a nodal property of class with noderel=subnode, or that of a character, string, or byteseq property

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 conprop=value>

<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.4.2.1.4 Member of default grove plan

Change the default value specification of the "default" attribute from "ndefault" to

      #IMPLIED    -- Default: inherited from containing classdef or
                     psmodule element, if any; otherwise required in
                     every grove plan. --

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.6.7.3.1 URL Portable storage manager

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.3.1 --

Clause A.6.7.3.2 Neutral file identifier storage manager

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.3.2 --

Clause A.6.7.3.4 Notation processor storage managers

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.3.4 --

Clause A.6.7.4 Global storage manager notation form

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.4 --

Clause A.6.7.5 Global storage managers

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.5 --

Clause A.6.7.6 Container storage manager notation form

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.6 --

Clause A.6.7.6.1 Container storage managers

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.6.1 --

Clause A.6.7.6.2 Standard BENTO (sbento)

Change the "Clause:" comments in the forms to read:

                  -- Clause: A.6.7.6.2 --

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>

Update the class definition for the pelement class by adding a conprop attribute so as to read:

<classdef rcsnm=pelement appnm="pseudo element" conprop=content
fullnm="pseudo-element" sd=HyTime clause="71420">

Change the application name and full names of the "attdldecl" properties of "elemtype" and "notation" to "attribute def list decls" and "attribute definition list declarations", respectively.

Clause C Architectural Meta-Declarations

Clause C.1 HyTime Lexical Types

Add "LTDR" to the public identifier given in the initial comment of the HyTime lexical type definition document, so that it reads:

<!--
This file is identified by the following public identifier:

"ISO/IEC 10744:1997//NONSGML LTDR LEXTYPES HyTime Lexical Types//EN"
-->

Add ":1997" and "LTDR" to the public identifer given for the parameter entity "SGMLlex", so that it reads:

"ISO/IEC 10744:1997//NONSGML LTDR LEXTYPES SGML Lexical Types//EN"

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).

Add the following declarations, plus a trailing blank line, immediately preceding the ArcBase PI for the General Architecture:

<!entity %
   gacomatt       -- GenArc common attributes options --

   '"%gadafe; %gadvl; %gaHyLex; %gaHyOrd; %gairftp; %galextp;
     %gaopaci; %gaREGEX;"'
>
<!entity %
   gadcnatt       -- GenArc common data attributes options --

   '"%gaaltrp; %gaincl; %gaspdcn;"'
>

Replace the "commatts" and "dcnatts" General Architecture support attributes with:

    commatts CDATA    #FIXED %gacomatt;
    dcnatts  CDATA    #FIXED %gadcnatt;