MHonArc v2.5.2 -->
ebxml-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: schema in [ebxml-msg] v2.0 rev b, etc.
|
David and Arvola,
I'm confused. In our discussions yesterday, we generally agreed
2.3.2 should stay but include MAY instead of MUST. The sentiments
was primarily around the xsi:schemaLocation attribute doing no harm and
avoiding unnecessary changes to the document. Why has this come back
again?
Chris has also commented on the three points Arvola originally raised.
Were his suggestions incorporated in the changing document and schema?
I'm also concerned we're attempting to vote upon a moving target.
If we don't have something stable to designate a TC specification and (potentially
later) submit to OASIS, let's get things to that state before the vote.
In the meantime, let's push back on Karl and get a (slight) extension to
the submission deadline.
thanx,
doug
Arvola Chan wrote:
David: My
personal opinion is that the entire section 2.3.2 xsi:schemaLocation
attribute is obsolete and no longer necessary now that the "http://schemas.xmlsoap.org/soap/envelope/"
namespace and the "http://www.oasis-open.org/committees/ebxml-msg/msg-header-2_0.xsd"
namespace can be directly resolvable (see strategies 3 and 5 in the following
excerpt from http://www.w3.org/TR/xmlschema-1/). 4.3.2
How schema definitions are located on the Web
Schema
Representation Constraint: Schema Document Location Strategy
Given a namespace
name (or none) and (optionally) a URI reference from xsi:schemaLocation
or xsi:noNamespaceSchemaLocation, schema-aware processors may
implement any combination of the following strategies, in any order:
1 Do nothing, for
instance because a schema containing components for the given namespace
name is already known to be available, or because it is known in advance
that no efforts to locate schema documents will be successful (for example
in embedded systems);
2 Based on the
location URI, identify an existing schema document, either as a resource
which is an XML document or a <schema>
element information item, in some local schema repository;
3 Based on the
namespace name, identify an existing schema document, either as a resource
which is an XML document or a <schema>
element information item, in some local schema repository;
4 Attempt to resolve
the location URI, to locate a resource on the web which is or contains
or references a <schema>
element;
5 Attempt to resolve
the namespace name to locate such a resource.
Whenever possible configuration and/or
invocation options for selecting and/or ordering the implemented strategies
should be provided.
If we adopt this change, then all of
the examples should have the schema locations for the above two namespaces
removed. In addition, the introductory material in Appendix A also needs
tweaking. If we choose not to make the suggested
changes, we should at least update the cached schemas we have on the ebxml-msg
TC web site for the SOAP envelope and for xmldsig-core-schema. Regards,-Arvola
-----Original
Message-----
From: David Fischer <david@drummondgroup.com>
To: Arvola Chan <arvola@tibco.com>
Date: Tuesday, February 19,
2002 7:15 PM
Subject: RE: schema in [ebxml-msg]
v2.0 rev b, etc.
Did
I get this right? It required changes throughout the document.What
did we decide about xsi:schemaLocation? Do we need it in all the
examples?David.
David: I am not sure if we really
want to leave the following unchanged in the schema: 1.
<import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/xmldsig-core-schema.xsd"/>
2.
<import namespace="http://www.w3.org/1999/xlink" schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/xlink.xsd"/>
3.
<import namespace="http://schemas.xmlsoap.org/soap/envelope/" schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"/>
With
respect to #1 above, please seehttp://lists.oasis-open.org/archives/ebxml-msg/200202/msg00154.html
|
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC