OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: Troubleshooting Topic Nesting Rules: XSD Is A Problem


I have figured out a slightly easier solution for the troubleshooting issue without having to resort to an intermediate file design. As a precedent, I'm using the same solution that is used in the ditabase.xsd shell document.  The solution is to remove troubleshooting element from the troubleshooting-info-type group model and add  the task element to the info-types model.  That way, we don't need to have a new intermediate file to accomplish the same magic. ;)

Here is the pertinent snippet of code, if interested.  If SVN allows me to check-in the content, I will do so. Otherwise, I will send the files to Eliot for check-in.

<!-- Remove task-info-types from the group so we don't have collidng task elements -->
   <xs:redefine schemaLocation="strictTaskbodyConstraintMod.xsd">
      <xs:group name="task-info-types">
            <xs:group ref="info-types"/>
   <!-- Remove troubleshooting element from the group since we prefer task as the embedable topic type-->
   <xs:redefine schemaLocation="./troubleshootingMod.xsd">
      <xs:group name="troubleshooting-info-types">
            <xs:group ref="info-types"/>
   <!--  ================ INFO-TYPES DEFINITION =====================  -->
   <xs:group name="info-types">
            This group is referenced in all topic modules but not defined there.
            It must be declared in topic-type shells.
         <xs:group  ref="task" />

Éric Sirois
DITA Toolsmith​

825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
tel  + 1 514 279-4942  /  toll free + 1 877 279-4942
eric.sirois@ixiasoft.com / www.ixiasoft.com  

-----Original Message-----
From: dita@lists.oasis-open.org [mailto:dita@lists.oasis-open.org] On Behalf Of Eliot Kimber
Sent: May 19, 2015 10:55 AM
To: dita
Subject: [dita] Troubleshooting Topic Nesting Rules: XSD Is A Problem

Because of the way XSD's redefine feature works, a direct redefine of the troubleshooting-info-types group cannot disallow nesting of troubleshooting within troubleshooting for the XSD.

There are a few possible solutions:

1. Don't worry about it. XSD is already broken and nobody should use it anyway.

2. Change the base definition of troubleshooting-info-types to disallow any nested topics

3. Add the required intermediate group files required to allow the definition of the group so it matches the RNG and DTD versions.

I vote for option (1) but option (2) would be consistent with the TC's decision to make the default nesting for troubleshooting be "task" and not "troubleshooting" as defined in the troubleshooting document type shell. I don't like option (3).



Eliot Kimber, Owner
Contrext, LLC

To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]