Re: XML Schema language version
"Timothy W. Cook" <[email protected]> Wed, 2 Oct 2013 20:22:09 -0300
| Newsgroups | gmane.text.xml.schema.devel |
|---|---|
| Message-ID | <CA+=OU3Uo3NA0K7XDn2J4ae_jBV5nimp894ye2gRzOBXnVe6UdA@mail.gmail.com> |
--e89a8ff2518e9df39c04e7ca5671 Content-Type: text/plain; charset=UTF-8 vc:minVersion="1.1" is a great solution for marking them as 1.1 required. Is there a need for a vc:maxVersion? --Tim On Wed, Oct 2, 2013 at 5:12 PM, Michael Kay <[email protected]> wrote: > I think it would be a creative but perfectly reasonable interpretation of > the XSD 1.1 specification to advise users to set vc:minVersion="1.0" or > vc:minVersion="1.1" or vc:maxVersion="1.0" on the xs:schema element to > indicate whether they expect to use a 1.0 processor or a 1.1 processor for > the schema, and for an IDE such as oXygen to use this attribute when > selecting a processor to run. > > See http://www.w3.org/TR/xmlschema11-1/#cip > > Michael Kay > Saxonica > > On 2 Oct 2013, at 20:55, C. M. Sperberg-McQueen wrote: > > > > > On Sep 26, 2013, at 2:58 AM, George Cristian Bina wrote: > > > >> Hi all, > >> > >> We introduced XML Schema 1.1 support in oXygen some time ago. As there > is no way to specify the version of the XML Schema language we added an > application option that controls what version is in use. By default XML > Schema 1.1 is selected and we show a notification to the user informing him > that we use XML Schema 1.1 with two options: > >> Continue with 1.1 > >> Switch back to 1.0 > >> After the user chooses one of these options this notification > disappears and is not presented again, the user being able to change the > XML Schema version from the oXygen preferences and even specify a specific > value for each project. > >> > >> One problem we encountered with a number of users is that they choose > to continue with XML Schema 1.1 and then they forget about this. They > develop XML Schema 1.1 schemas and deploy them to users using XML Schema > 1.0 tools, without being aware that they are using XML Schema 1.1 features > in their schemas. > >> > >> Not having a mechanism of setting the XML Schmea language version > inside the schema file makes difficult working with XML Schema 1.0 and XML > Schema 1.1 files in the same time. > >> > >> We can add of course an oXygen specific way of specifying the XML > Schema language version required to process a specific XML Schema in the > form of a PI or an annotation but it will be useful to see if there is more > interest in having this functionality and then find a better way to specify > and implement this so that people can use the same syntax and have that > understood by more tools. Maybe a W3C Note will be a good choice for > specifying this, similar to the xml-model PI for associating a schema with > a document. > > > > It certainly seems that the two decisions (a) not to put any version > identifier > > into an XSD 1.0 schema, and (b) not to change the namespace in XSD 1.1, > > working together, were a mistake. > > > > I believe the URIs specified in XSD 1.1 for denoting specific versions of > > XSD should be useful here -- at least, they provide a standard way to say > > things like "XSD 1.0" and "XSD 1.1". > > > > > > -- > > **************************************************************** > > * C. M. Sperberg-McQueen, Black Mesa Technologies LLC > > * http://www.blackmesatech.com > > * http://cmsmcq.com/mib > > * http://balisage.net > > **************************************************************** > > > > > > > > > > > > > -- MLHIM VIP Signup: http://goo.gl/22B0U ============================================ Timothy Cook, MSc +55 21 94711995 MLHIM http://www.mlhim.org Like Us on FB: https://www.facebook.com/mlhim2 Circle us on G+: http://goo.gl/44EV5 Google Scholar: http://goo.gl/MMZ1o LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook --e89a8ff2518e9df39c04e7ca5671 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">vc:minVersion=3D"1.1" is a great solution for ma= rking them as 1.1 required. Is there a need for a vc:maxVersion?<div><br></= div><div>--Tim=C2=A0</div></div><div class=3D"gmail_extra"><br><br><div cla= ss=3D"gmail_quote"> On Wed, Oct 2, 2013 at 5:12 PM, Michael Kay <span dir=3D"ltr"><<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>></= span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e= x;border-left:1px #ccc solid;padding-left:1ex"> I think it would be a creative but perfectly reasonable interpretation of t= he XSD 1.1 specification to advise users to set vc:minVersion=3D"1.0&q= uot; or vc:minVersion=3D"1.1" or vc:maxVersion=3D"1.0" = on the xs:schema element to indicate whether they expect to use a 1.0 proce= ssor or a 1.1 processor for the schema, and for an IDE such as oXygen to us= e this attribute when selecting a processor to run.<br> <br> See <a href=3D"http://www.w3.org/TR/xmlschema11-1/#cip" target=3D"_blank">h= ttp://www.w3.org/TR/xmlschema11-1/#cip</a><br> <span class=3D"HOEnZb"><font color=3D"#888888"><br> Michael Kay<br> Saxonica<br> </font></span><div class=3D"HOEnZb"><div class=3D"h5"><br> On 2 Oct 2013, at 20:55, C. M. Sperberg-McQueen wrote:<br> <br> ><br> > On Sep 26, 2013, at 2:58 AM, George Cristian Bina wrote:<br> ><br> >> Hi all,<br> >><br> >> We introduced XML Schema 1.1 support in oXygen some time ago. As t= here is no way to specify the version of the XML Schema language we added a= n application option that controls what version is in use. By default XML S= chema 1.1 is selected and we show a notification to the user informing him = that we use XML Schema 1.1 with two options:<br> >> Continue with 1.1<br> >> Switch back to 1.0<br> >> After the user chooses one of these options this notification disa= ppears and is not presented again, the user being able to change the XML Sc= hema version from the oXygen preferences and even specify a specific value = for each project.<br> >><br> >> One problem we encountered with a number of users is that they cho= ose to continue with XML Schema 1.1 and then they forget about this. They d= evelop XML Schema 1.1 schemas and deploy them to users using XML Schema 1.0= tools, without being aware that they are using XML Schema 1.1 features in = their schemas.<br> >><br> >> Not having a mechanism of setting the XML Schmea language version = inside the schema file makes difficult working with XML Schema 1.0 and XML = Schema 1.1 files in the same time.<br> >><br> >> We can add of course an oXygen specific way of specifying the XML = Schema language version required to process a specific XML Schema in the fo= rm of a PI or an annotation but it will be useful to see if there is more i= nterest in having this functionality and then find a better way to specify = and implement this so that people can use the same syntax and have that und= erstood by more tools. Maybe a W3C Note will be a good choice for specifyin= g this, similar to the xml-model PI for associating a schema with a documen= t.<br> ><br> > It certainly seems that the two decisions (a) not to put any version i= dentifier<br> > into an XSD 1.0 schema, and (b) not to change the namespace in XSD 1.1= ,<br> > working together, were a mistake.<br> ><br> > I believe the URIs specified in XSD 1.1 for denoting specific versions= of<br> > XSD should be useful here -- at least, they provide a standard way to = say<br> > things like "XSD 1.0" and "XSD 1.1".<br> ><br> ><br> > --<br> > ****************************************************************<br> > * C. M. Sperberg-McQueen, Black Mesa Technologies LLC<br> > * <a href=3D"http://www.blackmesatech.com" target=3D"_blank">http://ww= w.blackmesatech.com</a><br> > * <a href=3D"http://cmsmcq.com/mib" target=3D"_blank">http://cmsmcq.co= m/mib</a><br> > * <a href=3D"http://balisage.net" target=3D"_blank">http://balisage.ne= t</a><br> > ****************************************************************<br> ><br> ><br> ><br> ><br> ><br> <br> <br> </div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>= MLHIM VIP Signup: <a href=3D"http://goo.gl/22B0U" target=3D"_blank">http://= goo.gl/22B0U</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D<br>Timothy Cook, MSc =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +55 21 94711995= <br> MLHIM <a href=3D"http://www.mlhim.org" target=3D"_blank">http://www.mlhim.o= rg</a><br>Like Us on FB: <a href=3D"https://www.facebook.com/mlhim2" target= =3D"_blank">https://www.facebook.com/mlhim2</a><br>Circle us on G+: <a href= =3D"http://goo.gl/44EV5" target=3D"_blank">http://goo.gl/44EV5</a><br> Google Scholar: <a href=3D"http://goo.gl/MMZ1o" target=3D"_blank">http://go= o.gl/MMZ1o</a><br>LinkedIn Profile:<a href=3D"http://www.linkedin.com/in/ti= mothywaynecook" target=3D"_blank">http://www.linkedin.com/in/timothywayneco= ok</a><br> </div> --e89a8ff2518e9df39c04e7ca5671--