OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [ebxml-msg] [Fwd: Re: W3C - Link report]


done.
-----Original Message-----
From: Arvola Chan [mailto:arvola@tibco.com]
Sent: Tuesday, January 15, 2002 1:56 PM
To: David Fischer
Cc: ebxml-msg@lists.oasis-open.org
Subject: Re: [ebxml-msg] [Fwd: Re: W3C - Link report]

David:
 
We should delete the following line highlighted in red:

These alternative schema SHALL be available from the following URLís:

XML Signature Core - http://www.oasis-open.org/committees/ebxml-msg/schema/xmldsig-core-schema.xsd

Xlink - http://www.oasis-open.org/committees/ebxml-msg/schema/xlink.xsd

xml:lang - http://www.oasis-open.org/committees/ebxml-msg/schema /xml_lang.xsd

SOAP1.1- http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd

We should also replace

<import namespace="http://www.w3.org/XML/1998/namespace"              schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/xml_lang.xsd"/>

with

<import namespace="http://www.w3.org/XML/1998/namespace"              schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>

-Arvola

-----Original Message-----
From: David Fischer <david@drummondgroup.com>
To: Arvola Chan <arvola@tibco.com>; ian.c.jones@bt.com <ian.c.jones@bt.com>
Cc: ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
Date: Tuesday, January 15, 2002 11:19 AM
Subject: RE: [ebxml-msg] [Fwd: Re: W3C - Link report]

Should we replace or should we delete the line?  This is no longer an
"alternative schema".

David.

-----Original Message-----
From: Arvola Chan [mailto:arvola@tibco.com]
Sent: Tuesday, January 15, 2002 12:28 PM
To: David Fischer; ian.c.jones@bt.com
Cc: ebxml-msg@lists.oasis-open.org
Subject: Re: [ebxml-msg] [Fwd: Re: W3C - Link report]


David:

Since both Cliff (using Xerces-J 1.4.4) and Peter (using XML Spy 4.0) do not
have problem with the absence of an explicit declaration of the xml
namespace, I think the changes to the spec can be limited to what you and I
have discussed, i.e.,

- remove the explicit identification of "xml:lang -
http://www.oasis-open.org/committees/ebxml-msg/schema/xml_lang.xsd" on line
2170

- replace http://www.oasis-open.org/committees/ebxml-msg/schema/xml_lang.xsd
with http://www.w3.org/2001/03/xml.xsd as the schema location on line 2189.

Ian:

Can you please post the attached updated version of msg-header-2_0.xsd? The
changes from the previous version is shown in the following diff output (the
old version is msg-header-2_0_bak.xsd):

C:\ebxml>diff msg-header-2_0.xsd msg-header-2_0_bak.xsd
2,4d1
< <!-- Some parsers may require explicit declaration of
'xmlns:xml="http://www.w
3.org/XML/1998/namespace"'.
<      In that case, a copy of this schema augmented with the above
declaration
should be cached and used
<      for the purpose of schema validation on ebXML messages. -->
17c14
<       <import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation=
"http://www.w3.org/2001/03/xml.xsd"/>
---
>       <import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation=
"http://www.oasis-open.org/committees/ebxml-msg/schema/xml_lang.xsd"/>

Thanks,
-Arvola

-----Original Message-----
From: Peter Ogden <pogden@cyclonecommerce.com>
To: Arvola Chan <arvola@tibco.com>; Cliff Collins <collinsc@sybase.com>
Cc: David Fischer <david@drummondgroup.com>; Christopher Ferris
<chris.ferris@sun.com>; ebxml-msg@lists.oasis-open.org
<ebxml-msg@lists.oasis-open.org>
Date: Tuesday, January 15, 2002 10:02 AM
Subject: RE: [ebxml-msg] [Fwd: Re: W3C - Link report]


Arvola,

I am able to load the file
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd
in XML Spy (v4.0) without any errors.

Peter

-----Original Message-----
From: Arvola Chan [mailto:arvola@tibco.com]
Sent: Tuesday, January 15, 2002 9:43 AM
To: Cliff Collins; Peter Ogden
Cc: David Fischer; Christopher Ferris; ebxml-msg@lists.oasis-open.org
Subject: Re: [ebxml-msg] [Fwd: Re: W3C - Link report]


Cliff and Peter:

I like to check with you guys if Xerces-J and XML Spy still require
explicit
declaration of the xml namespace, i.e., whether the declaration

    xmlns:xml="http://www.w3.org/XML/1998/namespace"

is still necessary.

I recall that Cliff has indicated that Xerces-J 1.4.4 works much better
than
earlier versions. I also have the strong suspicion that the remaining
error

    Error: constraint 3.x.3: Attribute 'form' cannot appear in element
'attribute'

may have been solved by replacing our version of xml_lang.xsd with
either

    http:/www.w3.org/2001/03/xml.xsd or http:/www.w3.org/2001/xml.xsd

because Anli Shundi has warned me that there is a problem with the use
of
the 'form' construct in xml_lang.xsd.

Similarly, Peter does not seem to have any problem sharing with me a
working
version of the CPP/A schema even though it makes use of the xml:lang
attribute in a way similar to msg-header-2_0.xsd.

David:

If neither Xerces-J nor XML Spy requires the explicit xml namespace
delcaration, I suggest we don't even say in the spec that some parsers
may
require the explicit xml namespace declaration (a comment in the XSD may
be
sufficient).  Therefore, only one change needs to go into both Appendix
A
and the separately available msg-header-2_0.xsd. We should simply fix
the
import element for the xml namespace to use a schema location of
http:/www.w3.org/2001/03/xml.xsd.

I don't think it is a problem even if two MSH's have to use different
versions of msg-header-2_0.xsd, one with the explicit xml namespace
declaration and the other without the declaration. The schema instances
(i.e., the ebXML messages) may or may not carry the optional
xsi:schemaLocation indication for the

http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd

namespace. If not, the parser must still be able to resolve the above
namespace. Even if they do specify the default schema location, i.e.,

http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd

the receiving MSH should still be able to configure its own parser to
use a
locally cached version of the schema, one that is understandable to that
parser, instead of the one hinted at by the xsi:schemaLocation
declaration.

Regards,
-Arvola

-----Original Message-----
From: David Fischer <david@drummondgroup.com>
To: Christopher Ferris <chris.ferris@sun.com>; ebXML Msg
<ebxml-msg@lists.oasis-open.org>
Date: Tuesday, January 15, 2002 8:06 AM
Subject: RE: [ebxml-msg] [Fwd: Re: W3C - Link report]


Where in our spec does this need to go?  Since we have voted, I don't
feel
like
we can change anything more than typo's.

The only place I can find any mention is at the beginning of Appendix A
but
we
don't actually use this anywhere.  I am still uncomfortable with the
idea of
use
it sometimes and don't use it sometimes.  If Company-A points to a url
.xsd
which does not contain this declaration (and their parser is fine) and
then
sends to Company-B who's parser chokes without this .xsd declaration,
then
we
have a problem.  I understand that the schema can be cached locally and
modified
but that sounds like trouble to me.  If two MSHs point to the same url,
then
that url should work the same in both cases.

David.

-----Original Message-----
From: Christopher Ferris [mailto:chris.ferris@sun.com]
Sent: Tuesday, January 15, 2002 9:01 AM
To: ebXML Msg
Subject: [ebxml-msg] [Fwd: Re: W3C - Link report]


FYI,

The resource has been fixed, and there should be no
problems accessing it (no more 403). I therefore recommend
that we use the URI http://www.w3.org/2001/03/xml.xsd
in our spec since that is the version that is guaranteed
not to change.

Cheers,

Chris

-------- Original Message --------
Subject: Re: W3C - Link report
Date: Tue, 15 Jan 2002 04:28:31 -0500
From: Dominique Hazael-Massieux <dom@w3.org>
To: chris.ferris@sun.com
CC: web-human@w3.org, ht@w3.org
References: <200201141845.NAA13588@www19.w3.org>

On Mon, Jan 14, 2002, chris.ferris@sun.com wrote:
> Email:                       chris.ferris@sun.com
> Originating URL:             http://www.w3.org/2001/xml.xsd
> Forbidden Page:                      http://www.w3.org/2001/03/xml.xsd
> Comments:                    The schema document at the URI
http://www.w3.org/2001/xml.xsd
indicates that the permanent URI of the current resource will be at the
forbidden URI address. It
would seem to me that the URI    http://www.w3.org/2001/xml.xsd has
incorrect
access control applied
  to it.  From the comments within the schema:  "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."

Fixed, thank you for your report!

Regards,

Dom
--
Dominique HazaŽl-Massieux - http://www.w3.org/People/Dom/
W3C's Webmaster
mailto:dom@w3.org


----------------------------------------------------------------
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>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC