Next in thread →
Next in month →
Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward
Hi Eliot, That sounds good to me. That said, do we have an idea of changes users were trying to make but were not able to make with the current design of the XSDs. Eric 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: 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. Eliot Kimber ---07/10/2014 08:55:42 AM---I think I had this action and failed to provide some suggested language before I left on vacation. From: Eliot Kimber <> To: Don R Day <>, <> Date: 07/10/2014 08:55 AM Subject: Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward Sent by: <> I think I had this action and failed to provide some suggested language before I left on vacation. What'd I'd like the spec to say is something like: DITA's specialization and constraint features depend on the XML Schema Definition redefine facility. Unfortunately, the redefine facility imposes restrictions on how XSD groups can be constructed. These restrictions make it impossible to redefine certain types of content models without first refactoring those content models into new groups, where each group is then redefinable. The XSDs for the standard DITA base vocabulary and specializations reflect the content models as defined in the RELAX NG and DTD implementations except where the DITA TC has provided constraint modules that require refactoring of the XSD content model in order to allow redefinition (the strict task body and machinery industry task body constraint modules). This means that there are XSD content models that cannot be constrained as provided by OASIS. In the case where you need to constrain such a content model you MAY modify the OASIS-provided XSD module in order to refactor the content model as required by your constraint. You can do this either by simply modifying the OASIS-provided XSD module or by extending the RELAX NG-to-XSD generation process to add your special case. You SHOULD notify the DITA Technical Committee of your constraint requirement so that the TC can consider adding the required refactoring to the XSDs as provided by OASIS. Cheers, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com On 7/8/14, 9:07 AM, "Don R Day" <> wrote: > > > > > > And the "XSD 1.1 feature issues" have > been discussed several times--this was one public disclosure: > >https://groups.yahoo.com/neo/groups/dita-users/conversations/topics/16445 > > > >* Don R. Day <mailto:> > >* Co-Founder, ContelligenceGroup.com <http://contelligencegroup.com/> > >* Founding Chair, OASIS > DITA Technical Committee ><http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita> > >* LinkedIn: donrday <http://www.linkedin.com/in/donrday> Twitter: > @donrday <http://twitter.com/in/donrday> > >* About.me: Don R. Day <http://about.me/donrday> Skype: > don.r.day > > > > >* "Where is the wisdom we have lost in knowledge? > >* Where is the knowledge we have lost in information?" > >* --T.S. Eliot > > > > On 7/8/2014 9:43 AM, Don R Day wrote: > > > > Last week we started discussing the emerging dark reality of XSD's > inability to handle constraints without direct editing, which > mungles the DITA design pattern. So I'm reiterating many past > discussions by suggesting that it's time to add a small statement > into the spec that, besides moving to RNC as the normative > declaration of ongoing DITA design patterns, that we add a new > disclaimer that summarizes our past difficulties with XSD features > needed for DITA (the XSD 1.1 feature issues need to be logged for > historical reasons) and clarifying how to amend/create a one-off > XSD instance that represents modifications that normally would be > supported by RNC/DTD rules. I think we discussed this last week, > but I hope we can get to disposition this week. > > -- > > > >* Don R. Day <mailto:> > >* Co-Founder, ContelligenceGroup.com <http://contelligencegroup.com/> > >* Founding Chair, OASIS > > DITA Technical Committee ><http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita> > >* LinkedIn: donrday <http://www.linkedin.com/in/donrday> Twitter: > > @donrday <http://twitter.com/in/donrday> > >* About.me: Don R. Day <http://about.me/donrday> Skype: > don.r.day > > > > >* "Where is the wisdom we have lost in knowledge? > >* Where is the knowledge we have lost in information?" > >* --T.S. Eliot > > > > > > > > -- > > > >* Don R. Day <mailto:> > >* Co-Founder, ContelligenceGroup.com <http://contelligencegroup.com/> > >* Founding Chair, OASIS > DITA Technical Committee ><http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita> > >* LinkedIn: donrday <http://www.linkedin.com/in/donrday> Twitter: > @donrday <http://twitter.com/in/donrday> > >* About.me: Don R. Day <http://about.me/donrday> Skype: > don.r.day > > > > >* "Where is the wisdom we have lost in knowledge? > >* Where is the knowledge we have lost in information?" > >* --T.S. Eliot > > > > > --------------------------------------------------------------------- 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: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Next in thread →
Next in month →