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: Bug fixes for DITA XML Schema


Hi,

I had some discussion regarding the DITA XML Schema on dita-users.  He wanted to restrict the use of mixed content models (PCDATA) in his schema specialization.  The issue that needs to be fixed so users can have complete control over specialization they want to create.

For instance, in the sample below, the issue is that with the current design in XML Schema 1.0 there's no way for someone to redefine/override the mixed attribute definition in the complexType defined within the section element declaration.  The fix is to remove that from the schema doc.  I'm in the process of scanning the rest of the schema documents at the moment.  As well, I have some other schema updates that need to be pushed to the SVN repository.

Kind regards,
Eric


<xs:element name="section">
   
<xs:annotation>
     
<xs:documentation> The &lt;<keyword>section</keyword>> element represents an organizational
       division in a topic. Sections are used to organize subsets of information
       that are directly related to the topic. For example, the titles
<b>Reference
         Syntax
</b>, <b>Example</b> and <b>Properties</b> might represent section-level
       discourse within a topic about a command-line process—the content in each
       section relates uniquely to the subject of that topic. Multiple sections within
       a single topic do not represent a hierarchy, but rather peer divisions of
       that topic. Sections cannot be nested. A section may have an optional title.
     
</xs:documentation>
   
</xs:annotation>
 
 <xs:complexType mixed="true">
     
<xs:complexContent>
       
<xs:extension base="section.class">
         
<xs:attribute ref="class" default="- topic/section "/>
       
</xs:extension>
     
</xs:complexContent>
   
</xs:complexType>
 
</xs:element>
 
<xs:complexType name="section.class" mixed="true">
   
<xs:sequence>
     
<xs:group ref="section.content"/>
   
</xs:sequence>
   
<xs:attributeGroup ref="section.attributes"/>
 
</xs:complexType>



Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA XML Schema Architect and DITA Open Toolkit Developer
IBM Canada Ltd. - Toronto Software Lab
Email:
esirois@ca.ibm.com
Phone:(905) 413-2841

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. 

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