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

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,
XML Press
XML for Technical Communicators

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

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