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: [dita] Bug in DITA XML Schema and updates for XML catalog.

While I think a correction to the DITA 1.1 Schemas is in order, I wonder if you shouldn’t wait on this for a week or two to see if we uncover anything else.


Adding dir to univ-atts should be straight forward.


How are you going to fix the misspelling of outputclass?  If you just correct the spelling, it is possible that existing documents will become invalid. Is that OK or do we need to add the correct spelling and continue to support the misspelling?  We did something along these lines for a misspelled attribute name in a DTD.




From: Eric Sirois [mailto:esirois@ca.ibm.com]
Sent: Monday, March 31, 2008 10:36 AM
To: dita@lists.oasis-open.org
Subject: [dita] Bug in DITA XML Schema and updates for XML catalog.



While working with John Hunt and Jeff Ogden to hammer out some final details for the Learning DTD/XML Schemas(XSDs).  Jeff discovered a couple of bugs with the XML Schemas.
  1) the attribute outputclass in the <foreign> and <unknown> is misspelled.
  2) the univ-atts attribute group the not have @dir attribute defined.

The other issue is related to the current XML catalog for the XML schemas.  
We are currently using <systemId> instead of <uri> because Xerces does not properly resolve entries using <uri>.  There was a bug report opened regarding this issue a few years back.  See the following Xerces bug report to see the details. http://issues.apache.org/jira/browse/XERCESJ-1104 (Resolution of schemaLocation URIs should be via URI resolution, not entity resolution).  Apologies to Eliot if this rehashes some unpleasant memories.
That being said, we should include <uri> entries in the XML Catalog for the DITA XSDs, as per the proper interpretation of the XML Entity Resolution specification with regards to XSDs. Applications that can properly interpret the specification can resolve the DITA XSDs appropriately and correctly.  

I propose that the fixes to the XSDs and the catalog should be approved by the TC and that the errata should be posted in the TC homepage.

Kind regards,

Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
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]