DR 19-0005: Identical complex types

[Francis Cave]

During yesterday’s telecon we discussed DR 19-0005, specifically the four
groups of complex types where all the complex types in each group have
identical structures. I shall deal with each group in turn.

 

Group 1: Category

 

§21.4.2.4 cat (Category), content model CT_Category

§21.4.4.1 cat (Color Transform Category), content model CT_CTCategory

§21.4.5.1 cat (Style Definition Category), content model CT_SDCategory.

 

The content models are all identical. All are defined in the DML-Diagrams
schema module:

 

<xsd:complexType name="CT_Category">

    <xsd:attribute name="type" type="xsd:anyURI" use="required"/>

    <xsd:attribute name="pri" type="xsd:unsignedInt" use="required"/>

</xsd:complexType>

 

<xsd:complexType name="CT_CTCategory">

    <xsd:attribute name="type" type="xsd:anyURI" use="required"/>

    <xsd:attribute name="pri" type="xsd:unsignedInt" use="required"/>

</xsd:complexType>

 

<xsd:complexType name="CT_SDCategory">

    <xsd:attribute name="type" type="xsd:anyURI" use="required"/>

    <xsd:attribute name="pri" type="xsd:unsignedInt" use="required"/>

</xsd:complexType>

 

I therefore propose that the title of §21.4.5.1 be changed as indicated
above, and that the Notes at the ends of §21.4.4.1 and §21.4.5.1 be revised
as follows:

 

§21.4.4.1:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_CTCategory) is located in §A.5.3. It is intentional that CT_CTCategory
is identical to CT_Category. end note]

 

§21.4.5.1:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_SDCategory) is located in §A.5.3. It is intentional that CT_SDCategory
is identical to CT_Category. end note]

 

Group 2: Category List

 

§21.4.2.5 catLst (Category List), content model CT_Categories

§21.4.4.2 catList (Color Transform Category List), content model
CT_CTCategories

§21.4.5.2 catList (Style Definition Category List), content model
CT_SDCategories.

 

The content models are all, in effect, identical, although they refer to the
three complex types in Group 1 above, and two of the content models contain
redundant attributes on <xs:sequence>. All are defined in the DML-Diagrams
schema module:

 

<xsd:complexType name="CT_Categories">

    <xsd:sequence>

        <xsd:element name="cat" type="CT_Category" minOccurs="0"
maxOccurs="unbounded"/>

    </xsd:sequence>

</xsd:complexType>

 

<xsd:complexType name="CT_CTCategories">

    <xsd:sequence minOccurs="0" maxOccurs="unbounded">

        <xsd:element name="cat" type="CT_CTCategory" minOccurs="0"
maxOccurs="unbounded"/>

    </xsd:sequence>

</xsd:complexType>

 

<xsd:complexType name="CT_SDCategories">

    <xsd:sequence minOccurs="0" maxOccurs="unbounded">

        <xsd:element name="cat" type="CT_SDCategory" minOccurs="0"
maxOccurs="unbounded"/>

    </xsd:sequence>

</xsd:complexType>

 

I therefore propose that the title of §21.4.5.2 be changed as indicated
above, that redundant attributes be deleted from the schema definitions of
two of the complex types, and that the Notes at the ends of §21.4.4.2 and
§21.4.5.2 be revised as follows:

 

§21.4.4.2:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_CTCategories) is located in §A.5.3. It is intentional that
CT_CTCategories is identical to CT_Categories. end note]

 

§21.4.5.2:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_SDCategories) is located in §A.5.3. It is intentional that
CT_SDCategories is identical to CT_Categories. end note]

 

Group 3: Description

 

§21.4.2.11 desc (Description), content model CT_Description

§21.4.4.6 desc (Color Transform Description), content model CT_CTDescription

§21.4.5.3 desc (Style LabelDefinition Description), content model
CT_SDDescription.

 

The content models are all identical. All are defined in the DML-Diagrams
schema module:

 

<xsd:complexType name="CT_Description">

    <xsd:attribute name="lang" type="xsd:string" use="optional" default=""/>

    <xsd:attribute name="val" type="xsd:string" use="required"/>

</xsd:complexType>

 

<xsd:complexType name="CT_CTDescription">

    <xsd:attribute name="lang" type="xsd:string" use="optional" default=""/>

    <xsd:attribute name="val" type="xsd:string" use="required"/>

</xsd:complexType>

 

<xsd:complexType name="CT_SDDescription">

    <xsd:attribute name="lang" type="xsd:string" use="optional" default=""/>

    <xsd:attribute name="val" type="xsd:string" use="required"/>

</xsd:complexType>

 

I therefore propose that the titles of §21.4.4.6 and §21.4.5.3 be changed as
indicated above and that the Notes at the ends of §21.4.4.6 and §21.4.5.3 be
revised as follows:

 

§21.4.4.6:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_CTDescription) is located in §A.5.3. It is intentional that
CT_CTDescription is identical to CT_Description. end note]

 

§21.4.5.3:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_SDDescription) is located in §A.5.3. It is intentional that
CT_SDDescription is identical to CT_Description. end note]

 

Group 4: Name

 

§21.4.2.30 title (Title), content model CT_Name

§21.4.4.11 title(Color Transform Title), content model CT_CTName

§21.4.5.11 title (Style Definition Title), content model CT_SDName.

 

The content models are all identical. All are defined in the DML-Diagrams
schema module:

 

<xsd:complexType name="CT_Name">

    <xsd:attribute name="lang" type="xsd:string" use="optional" default=""/>

    <xsd:attribute name="val" type="xsd:string" use="required"/>

</xsd:complexType>

 

<xsd:complexType name="CT_CTName">

    <xsd:attribute name="lang" type="xsd:string" use="optional" default=""/>

    <xsd:attribute name="val" type="xsd:string" use="required"/>

</xsd:complexType>

 

<xsd:complexType name="CT_SDName">

    <xsd:attribute name="lang" type="xsd:string" use="optional" default=""/>

    <xsd:attribute name="val" type="xsd:string" use="required"/>

</xsd:complexType>

 

I therefore propose that the titles of §21.4.4.11 and §21.4.5.11 be changed
as indicated above and that the Notes at the ends of §21.4.4.11 and
§21.4.5.11 be revised as follows:

 

§21.4.4.11:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_CTName) is located in §A.5.3. It is intentional that CT_CTName is
identical to CT_Name. end note]

 

§21.4.5.11:

 

[Note: The W3C XML Schema definition of this element’s content model
(CT_SDName) is located in §A.5.3. It is intentional that CT_SDName is
identical to CT_Name. end note]

 

Regards,

 

Francis



This message has been scanned for malware by Forcepoint. www.forcepoint.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20190124/be7503f9/attachment-0001.html>