Thank you Eric for finding this issue and finding a fix! I would
certainly support adding this fix ASAP.
Thanks and best regards,
--Scott
Eric Sirois wrote:
> Hello,
>
> During some final testing of the schemas for the Learning subcommittee I
> discovered that some of the elements in the original domains (ui,
> utilities, programming, software, and highlight) do not have the <group>
> defined for the elements.
>
> What's not working as expected?
> - Specializers who want to include elements defined in directly into
> their content models.
> - The Learning SC directly included some elements defined in
> domains into their content models. At the moment, when they include those
> element like any other element in the schemas they get an error stating
> that there is not group defined with the name coords and shape.
>
> <xs:complexType name="lcArea.class">
> <xs:sequence>
> <xs:group ref="coords"/> <!-- Error: this group definition
> doesn't not exist -->
> <xs:group ref="shape"/> <!-- Error: this group definition
> doesn't not exist -->
> <xs:group ref="xref" minOccurs="0"/>
> <xs:group ref="lcCorrectResponse"/>
> <xs:group ref="lcFeedback"/>
> </xs:sequence>
> <xs:attribute name="outputclass" type="xs:string"/>
> <xs:attributeGroup ref="univ-atts"/>
> <xs:attributeGroup ref="global-atts"/>
> </xs:complexType>
>
>
> At the moment, the only way to access those elements is through the domain
> base element group definitions. It' not the way I would advise developers
> getting access to those elements.
>
> <xs:complexType name="lcArea.class">
> <xs:sequence>
> <!-- coords -->
> <xs:group ref="ut-d-ph"/> <!-- This is a workaround, but don't
> do use it in this manner -->
> <!-- shape -->
> <xs:group ref="ut-d-keyword"/> <!-- This is a workaround, but
> don't do use it in this manner -->
> <xs:group ref="xref" minOccurs="0"/>
> <xs:group ref="lcCorrectResponse"/>
> <xs:group ref="lcFeedback"/>
> </xs:sequence>
> <xs:attribute name="outputclass" type="xs:string"/>
> <xs:attributeGroup ref="univ-atts"/>
> <xs:attributeGroup ref="global-atts"/>
> </xs:complexType>
>
> What's the impact?
> - Specializers cannot directly include specialized domain elements in
> their content models. They would have to include the base element, but
> that would also allow all of the other domain specialized element for the
> base element into the content model.
>
>
> What's the fix?
> - Create the groups for all the elements defined in the ui, utilities,
> programming, software, and highlight domains.
>
> <xs:group name="coords">
> <xs:choice>
> <xs:element ref="coords"/>
> </xs:choice>
> </xs:group>
>
> I believe that the committee draft is still open and I would like to add
> this fix to that process.
>
> Kind regards,
> Eric
> Eric A. Sirois
> Staff Software Developer
> DB2 Universal Database - Information Development
> DITA Migration and Tools Development
> IBM Canada Ltd. - Toronto Software Lab
> Email:
> Blue Pages (Internal)
>
> "Transparency and accessibility requirements dictate that public
> information and government
> transactions avoid depending on technologies that imply or impose a
> specific product or
> platform on businesses or citizens" - EU on XML-based office document
> formats.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
