Re: [xml-dev] XML Schema Checklist

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

At 2012-10-20 13:17 -0300, Timothy Cook wrote:
>On Sat, Oct 20, 2012 at 11:43 AM, G. Ken Holman
><gkholman@cranesoftwrights.com> wrote:
>
> > So I do not see any interpretation of the specification that would allow
> > what you ask.
> >
> > I hope this is helpful.
> >
>
>It is immensely!!!!! helpful.  I seriously appreciate it too.
>I guess my, so far unstated, question is; how the heck do parsers know
>whether they are looking at an XML schema that uses 1.1 specific
>capabilities?
>
>A (sort of) use case:
>I am using oXygen with SAXON-EE set to use 1.1 because I know this 
>before hand.
>
>But since this is an openly available schema and hopefully thousands
>of developers will use it and create restrictions based on it, and
>instance documents on them. There should be some way for a parser to
>know which schema version it is parseing. Other than waiting for it to
>"bump into" a 1.1 capability.

Actually, I think that's about it.  Certainly it is true for XSLT and 
it is designed into XSLT that unrecognized constructs are innocuous 
in a stylesheet unless they are encountered.

>I know that this has been thought of, so what am I still missing?

I'm scanning the W3C Schema 1.0 document and cannot quickly put my 
finger on the chapter and verse that addresses a schema expression 
containing non-1.0 constructs.  Perhaps someone else on the list 
knows where this is found.

. . . . . . . Ken


--
Contact us for world-wide XML consulting and instructor-led training
Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm
Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/x/
G. Ken Holman                   mailto:gkholman@CraneSoftwrights.com
Google+ profile: https://plus.google.com/116832879756988317389/about
Legal business disclaimers:    http://www.CraneSoftwrights.com/legal