Fw: [ebxml-msg] Re: [ebxml-cppa] Re: v. 2.0 ebXML xsd schema directory

[Arvola Chan <arvola@tibco.com>]

It seems that the file http://www.w3.org/2001/xml.xsd does exists
but read access has not been given to the general public. For
example, if you try

http://www.w3.org/2001/xml.xsd2

You will be told that the requested document does not exist but a
similar document /2001/03/xml.xsd is available.

However, if you click on the link, you will get a 403 error.

Probably an oversight on the part of W3C. Does anyone know
how the problem can be reported to W3C?

-Arvola

-----Original Message-----
From: Michael Wang <mwang@tibco.com>
To: Arvola Chan <arvola@tibco.com>
Date: Monday, January 14, 2002 9:38 AM
Subject: Re: [ebxml-msg] Re: [ebxml-cppa] Re: v. 2.0 ebXML xsd schema
directory


>FYI.
>I think a 403 means Forbidden.  This means the document is available
>but the read access is not turned on.  I somehow think it is an
>oversight by w3c.  In theory, it should be available.  Of course,
>I don't understand how w3c can be asked to make it available ...
>-mw
>
>Arvola Chan wrote:
>>
>> Chris:
>>
>> Thanks for your due diligence. I will update the schema to reference
>>
>> http://www.w3.org/2001/xml.xsd
>>
>> plus add a comment that some parsers may require the declaration:
>>
>> xmlns:xml="http://www.w3.org/XML/1998/namespace"
>>
>> Regards,
>> -Arvola
>>
>> -----Original Message-----
>> From: Christopher Ferris <chris.ferris@sun.com>
>> To: ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
>> Cc: ebxml-cppa@lists.oasis-open.org <ebxml-cppa@lists.oasis-open.org>
>> Date: Monday, January 14, 2002 5:58 AM
>> 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>
>>
>> ----------------------------------------------------------------
>> To subscribe or unsubscribe from this elist use the subscription
>> manager: <http://lists.oasis-open.org/ob/adm.pl>