[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ebxml-msg] Re: [ebxml-cppa] Re: v. 2.0 ebXML xsd schema dire ctory
David, But the http://www.w3.org/2001/03/xml.xsd URI cannot be resolved into anything but a 403! We cannot reference a resource which cannot be resolved/dereferenced. Cheers, Chris Burdett, David wrote: > Chris > > I looked at the schema and noticed the following text ... > > <xs:documentation>In keeping with the XML Schema WG's standard versioning > policy, this schema document will persist at > http://www.w3.org/2001/03/xml.xsd. > At the date of issue it can also be found at > http://www.w3.org/2001/xml.xsd. > The schema document at that URI may however change in the future, > in order to remain compatible with the latest version of XML Schema > itself. In other words, if the XML Schema namespace changes, the > version > of this document at > http://www.w3.org/2001/xml.xsd will change > accordingly; the version at > http://www.w3.org/2001/03/xml.xsd will not change. > > In the light of this should we be using > http://www.w3.org/2001/03/xml.xsd instead as it is guaranteed not to > change? > > David > > -----Original Message----- > From: Christopher Ferris [mailto:chris.ferris@sun.com] > Sent: Monday, January 14, 2002 5:57 AM > To: ebxml-msg@lists.oasis-open.org > Cc: ebxml-cppa@lists.oasis-open.org > Subject: Re: [ebxml-msg] Re: [ebxml-cppa] Re: v. 2.0 ebXML xsd schema > directory > > > A couple of points. I'm glad that this was found. > At the time of the ebXML 1.0 specs, (at least the > time when the authoring was on-going) this didn't > exist, hence the reference to an oasis-open.org URI. > > However, I just tried resolving the URI that Arvola > would like to refrerence and I get a 403. I imagine > that this is probably not desireable. > > Suggest instead that the URI referenced be: > > http://www.w3.org/2001/xml.xsd > > Cheers, > > Chris > Arvola Chan wrote: > > > Rich: > > > > I agree with your first point. > > > > With respect to your second point on referring to the canonical location > > http://www.w2.org/2001/xml.xsd, I like to bring your attention to the > > following excerpt from that schema: > > > > <xs:annotation> > > <xs:documentation>In keeping with the XML Schema WG's standard > versioning > > policy, this schema document will persist at > > http://www.w3.org/2001/03/xml.xsd. > > At the date of issue it can also be found at > > http://www.w3.org/2001/xml.xsd. > > The schema document at that URI may however change in the future, > > in order to remain compatible with the latest version of XML Schema > > itself. In other words, if the XML Schema namespace changes, the > version > > of this document at > > http://www.w3.org/2001/xml.xsd will change > > accordingly; the version at > > http://www.w3.org/2001/03/xml.xsd will not change. > > </xs:documentation> > > </xs:annotation> > > > > I think we should set the xsi:schemaLocation for the xml namespace to > > http://www.w3.org/2001/03/xml.xsd. > > > > -Arvola > > > > ----- Original Message ----- > > From: "Rich Salz" <rsalz@zolera.com> > > To: "Arvola Chan" <arvola@tibco.com> > > Cc: <ebxml-msg@lists.oasis-open.org>; <ebxml-cppa@lists.oasis-open.org> > > Sent: Friday, January 11, 2002 3:42 PM > > Subject: Re: [ebxml-msg] Re: [ebxml-cppa] Re: v. 2.0 ebXML xsd schema > > directory > > > > > > > >>{I'm not a member of the CPPA list, so they won't see this :} > >> > >>According to the XML namespace standard [1], > >>The prefix xml is by definition bound to the namespace name > >>http://www.w3.org/XML/1998/namespace. > >>So the declaration is not required, but it might not be illegal to have > >>it. I suggest *not* putting it, since it would cause folks to look > >>twice and wonder if the prefix is being bound to it's non-default > >>value. And it's easier to point buggy software to the URL that shows > >>them where they're non-compliant. :) > >> > >>Also, according to the same spec [2] > >>Prefixes beginning with the three-letter sequence x, m, l, in > >>any case combination, are reserved for use by XML and > >>XML-related specifications. > >> > >>It's not clear if defining The "xml" prefix to have its official value > >>is allowed. :) > >> > >> > >>>We can either replace the contents of > >>>http://www.oasis-open.org/committees/ebxml-msg/schema/xml-lang.xsd with > >>> > > the > > > >>>contents of the above file, or we can update our schema and examples to > >>> > > use > > > >>>the above URL as the schema location. I think it is simpler to do the > >>>former. > >>> > >>Again, it would lead to some puzzled looks. I would refer to the > >>official canonical location. > >> > >>/r$ > >> > >>[1] http://www.w3.org/TR/REC-xml-names/#nsc-NSDeclared > >>[2] http://www.w3.org/TR/REC-xml-names/#xmlReserved > >>-- > >>Zolera Systems, Securing web services (XML, SOAP, Signatures, > >>Encryption) > >>http://www.zolera.com > >> > >>---------------------------------------------------------------- > >>To subscribe or unsubscribe from this elist use the subscription > >>manager: <http://lists.oasis-open.org/ob/adm.pl> > >> > > > > > > ---------------------------------------------------------------- > > To subscribe or unsubscribe from this elist use the subscription > > manager: <http://lists.oasis-open.org/ob/adm.pl> > > > > > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC