Re: [xml-dev] Need a language whiz: An XML Schema "specifies" how data is to be structured? "describes"? "constrains"?
It's a reality which (again) the publishing sector has been living with since ever publishers started using markup.
They acknowledge or cope with it to a greater or lesser degree: the old-style trope was to have an "authoring DTD" and a "publishing DTD", the latter more finely attuned to publication needs.
Nowadays, things like Schematron's phases also address this need quite elegantly.
Andrew
On 6 January 2018 at 13:02, Frank Steimke <[email protected]> wrote:
This Idea is supported very well in the Oxygen Product: there you have so
called "validation scenarios", which is essentially a combination of
Schemata. You could have one validation scenario for "work in progress"
documents, and another scenario for "final" documents, both for the same
namespace. I would think that both scenarios would share the same XSD
Schema, but would differ in a "weak" vs "strong" Schematron Schema. In the
Oxygen IDE, it’s the users choice which scenario should be applied.
Out tool for validation and assessment, which I have mentioned in the mail
from Jan. 4th, tries to implement this idea of different validation
scenarios as a java library. Since there is no user interaction, you need
some mechanism to find out which scenario shall be applied. This can be any
XPATH expression. In the example given , I would think of a @status flag.
Frank
-----Ursprüngliche Nachricht-----
Von: Michael Kay [mailto:[email protected]]
Gesendet: Samstag, 6. Januar 2018 10:13
An: bryan rasmussen <[email protected]>
Cc: Costello, Roger L. <[email protected]>; [email protected]
Betreff: Re: [xml-dev] Need a language whiz: An XML Schema "specifies" how
data is to be structured? "describes"? "constrains"?
>
> Theoretically, although I have never seen it with XSD and would
> probably think it was a weird use of the language, you could have
> multiple schemas for validating documents in the same namespace.
I have seen one client who was attempting to do this: essentially applying
stricter validation to "finished" documents than to "work in progress". It
proved quite difficult to manage the maintenance of different versions of
the same schema; I think this is something that would benefit from better
support in languages and tools.
Michael Kay
Saxonica
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support
XML implementation and development. To minimize spam in the archives, you
must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: [email protected]
subscribe: [email protected] List archive:
http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: [email protected]
subscribe: [email protected]
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php