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: Review Comment: 2.1.4.4.2 Constraint module XSD codingrequirements: Error in example


The example in Figure 13: Example of a structural constraint module has a
typo. It should be:

  <xs:redefine schemaLocation="topicMod.xsd">
    <xs:group name="topic.content">
      <xs:sequence>
        <xs:sequence>
          <xs:group ref="title"/>
          <xs:group ref="titlealts" minOccurs="0"/>
          <xs:choice minOccurs="1" >
            <xs:group ref="shortdesc" />
            <xs:group ref="abstract" />
          </xs:choice>
          <xs:group ref="prolog" minOccurs="0"/>
          <!--<xs:group ref="body" minOccurs="0"/>-->
          <xs:group ref="related-links" minOccurs="0"/>
          <xs:group ref="topic-info-types" minOccurs="0"
maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:sequence>
    </xs:group>
  </xs:redefine>


This replaces the redefine of the type topic.class with the content model
group topic.content, which I think is the better way to do it, since the
general intent is to redefine model groups, not entire types.

Unless I've missed some subtlety of how XSD schema works, which is entirely
possible, if not in fact likely.

Cheers,

Eliot


-- 
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.com
www.rsuitecms.com



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