OASIS Darwin Information Typing Architecture (DITA) TC

 View Only

  • 1.  Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-04-2014 17:18
    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 http://xmlpress.net hamilton@xmlpress.net


  • 2.  Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-04-2014 19:00
    Looks great. Thanks for your work here, Dick. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype) On 8/4/2014 1:17 PM, Richard Hamilton wrote: 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 http://xmlpress.net hamilton@xmlpress.net --------------------------------------------------------------------- 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


  • 3.  Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-04-2014 19:37
    That looks fine to me. Cheers, E. ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com On 8/4/14, 1:17 PM, "Richard Hamilton" <hamilton@xmlpress.net> wrote: >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 > http://xmlpress.net >hamilton@xmlpress.net > > > > >--------------------------------------------------------------------- >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 > >


  • 4.  Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-05-2014 13:08
    Yes, looks good. This does not sound too negative when it comes to using XSD with DITA, which is good for XML editors that work with XSD only, like ours. Also, I would indeed be in favor of including the link to the RNG-to-XSD generator, since I do not think everyone reading the spec knows where to find that. Kind regards, Fredrik Geers Product Owner SDL LiveContent Create/SDL Xopus SDL (t) +31 (0)20 201 0500 (e) fgeers@sdl.com On 04/08/14 19:17, "Richard Hamilton" <hamilton@xmlpress.net> wrote: >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 > http://xmlpress.net >hamilton@xmlpress.net > > > > >--------------------------------------------------------------------- >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 > SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. This message has been scanned for malware by Websense. www.websense.com


  • 5.  Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-05-2014 17:41
    Hi Fredrik, I agree with the link. The only question I have is procedural. Does the link need to be labeled as non-normative, or is that assumed for links? Best regards, Dick ------- XML Press XML for Technical Communicators http://xmlpress.net hamilton@xmlpress.net On Aug 5, 2014, at 6:08 AM, Fredrik Geers <fgeers@sdl.com> wrote: > Yes, looks good. This does not sound too negative when it comes to using > XSD with DITA, which is good for XML editors that work with XSD only, like > ours. > Also, I would indeed be in favor of including the link to the RNG-to-XSD > generator, since I do not think everyone reading the spec knows where to > find that. > > Kind regards, > > Fredrik Geers Product Owner SDL LiveContent Create/SDL Xopus SDL > (t) +31 (0)20 201 0500 (e) fgeers@sdl.com > > > > On 04/08/14 19:17, "Richard Hamilton" <hamilton@xmlpress.net> wrote: > >> 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 >> http://xmlpress.net >> hamilton@xmlpress.net >> >> >> >> >> --------------------------------------------------------------------- >> 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 >> > > SDL PLC confidential, all rights reserved. > If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. > SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. > > > > This message has been scanned for malware by Websense. www.websense.com


  • 6.  Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-05-2014 17:45
    Interesting point. We link to non-normative material currently in the spec; see http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/metadata-elements.html#metadata-elements where we link to the Dublin Core Metadata Initiative. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype) On 8/5/2014 1:40 PM, Richard Hamilton wrote: Hi Fredrik, I agree with the link. The only question I have is procedural. Does the link need to be labeled as non-normative, or is that assumed for links? Best regards, Dick ------- XML Press XML for Technical Communicators http://xmlpress.net hamilton@xmlpress.net On Aug 5, 2014, at 6:08 AM, Fredrik Geers <fgeers@sdl.com> wrote: Yes, looks good. This does not sound too negative when it comes to using XSD with DITA, which is good for XML editors that work with XSD only, like ours. Also, I would indeed be in favor of including the link to the RNG-to-XSD generator, since I do not think everyone reading the spec knows where to find that. Kind regards, Fredrik Geers Product Owner SDL LiveContent Create/SDL Xopus SDL (t) +31 (0)20 201 0500 (e) fgeers@sdl.com On 04/08/14 19:17, "Richard Hamilton" <hamilton@xmlpress.net> wrote: 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 http://xmlpress.net hamilton@xmlpress.net --------------------------------------------------------------------- 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 SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. This message has been scanned for malware by Websense. www.websense.com --------------------------------------------------------------------- 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


  • 7.  RE: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-05-2014 17:59
    What's common practice elsewhere? As a reader of specs, my intuition would be to consider externally linked content as non-normative w.r.t. the spec I'm reading, unless the spec explicitly stated otherwise. mag
    Original Message


  • 8.  Re: [dita] Suggested TC position WRT XSD usage from DITA 1.3 onward -- Proposed wording

    Posted 08-05-2014 23:52
    Hi Tom, The DocBook spec has links like this that are not labeled either normative or non-normative, but which are clearly informational. For example, "RFEs are tracked through the SourceForge tracker interface," where "SourceForge tracker" is a hot link. I doubt anyone would consider SourceForge to be normative to this spec. It also contains more traditional references to things like the RELAX NG and SGML specifications, which might be either (in the DocBook spec, RELAX NG is normative and SGML isn't). These are handled as links to a reference section that has Normative and Non-Normative sections. So you see something like: "DocBook is defined using a [RELAX NG] Schema." [RELAX NG] is a link to a traditional bibliographic reference that is in the Normative section of the References. I'd argue that while most folks would consider the reference to the conversion program to be non-normative, it would be safer to be explicit in this case, either by tagging the reference as non-normative or using a strategy like the one used in the DocBook spec. Best regards, Dick ------- XML Press XML for Technical Communicators http://xmlpress.net hamilton@xmlpress.net On Aug 5, 2014, at 10:58 AM, Tom Magliery <tom.magliery@justsystems.com> wrote: > What's common practice elsewhere? > > As a reader of specs, my intuition would be to consider externally > linked content as non-normative w.r.t. the spec I'm reading, unless the > spec explicitly stated otherwise. > > mag > > > > >
    Original Message


Related Content