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: Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

Following up on an action from a couple of weeks ago, Don Day and I have put together proposed wording for this position statement.

Here is our draft:
If you want to create a specialization or constraint using the DITA XSD schema, you need to use the XSD redefine facility. However, this facility does not allow sequence groups to be directly constrained. Thus, to support specialization and constraints, it may be necessary to refactor content models into named groups that can be redefined. In order to keep the XSD, RELAX NG, and DTD implementations as consistent as possible, the DITA Technical Committee only refactored those content models that were required for OASIS-provided schemas. These were the strict task body and machinery industry task model. The other DITA content models distributed by OASIS have not been refactored.

You MAY modify the OASIS-provided XSD module to refactor the content model if required by your constraint. You can either modify the OASIS-provided XSD module or extend the RELAX NG-to-XSD generation process [link?] to add your special case. You SHOULD notify the DITA Technical Committee of your constraint requirement so the TC can consider adding the required refactoring to the OASIS-provided XSDs.

Please look this over for technical accuracy and clarity.

Best regards,
Dick Hamilton
XML Press
XML for Technical Communicators

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