XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Misuse of Schematron

TMTOWTDI

I would prefer to think of the schematron as extending and/or restricting the data model: your example works well enough when youíre using schema to define your data model (and Iím sure you could do something equally well with RELAX), but if youíre still saddled with DTDs the 'conflicting' approach is your only option.

There is also an argument to be made for loose data model definitions and tight QA requirements if the ramifications of frequent changes to your DTD or Schema outweigh those of your QA system Ė such is the case we have with our suppliers.

Tom

From: <Costello>, "Roger L." <costello@mitre.org>
Date: Sunday, 12 April 2015 16:19
To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
Subject: [xml-dev] Misuse of Schematron

The XML Schema and the Schematron schema are making conflicting assertions. Surely that is a sign of poor design.

Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.



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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS