RE: [ubl-ndrsc] Namespace Transitivity

[Matthew Gertner <matthew.gertner@acepoint.cz>]

Mark,

This isn't a correction so much as a clarification. Assuming that Bill's
versioning proposal is accepted (and it seems like a no-brainer), we
need to be clear about which old namespaces must be imported when
creating a new version with a new namespace. Arofan's mail describes
this in more detail; basically there was some uncertainty as to whether
(say) UBL v1.2 need import only UBL v1.1 (which in turn imports UBL
v1.0), or whether both UBL v1.0 and UBL v1.1 must be imported in order
to have access to all names.

It appears from the schema spec that the latter is the case. This is IMO
a bug in the spec since there should be a way to specify that when a
namespace is imported it "brings with it" some or all of the namespaces
that it imports (I think this is most important specifically in the case
of versioning). But if I start lamenting the shortcomings of XML Schema
this will be a very long mail indeed. We will just have to document this
and live with it.

Matt

> -----Original Message-----
> From: CRAWFORD, Mark [mailto:MCRAWFORD@lmi.org]
> Sent: Thursday, February 27, 2003 1:56 PM
> To: UBL NDR
> Subject: RE: [ubl-ndrsc] Namespace Transitivity
> 
> Matt,
> 
> Are you saying there is an issue with a decision we have made, or that
> there is a need for additional rules regarding explicitly importing
> namespaces in UBL?
> 
> Mark
> > -----Original Message-----
> > From: Matthew Gertner [mailto:matthew.gertner@acepoint.cz]
> > Sent: Wednesday, February 26, 2003 12:28 PM
> > To: UBL NDR
> > Subject: [ubl-ndrsc] Namespace Transitivity
> >
> >
> > From the XML Schema spec (Structures):
> >
> > "Schema Representation Constraint: QName resolution (Schema
Document)
> >
> > For a *QName* to resolve to a schema component of a specified kind
all
> > of the following must be true:
> > 1 That component is a member of the value of the appropriate
> > property of
> > the schema which corresponds to the schema document within which the
> > *QName* appears, that is the appropriate case among the following
must
> > be true:
> > 1.1 If the kind specified is simple or complex type
> > definition, then the
> > property is the {type definitions}.
> > 1.2 If the kind specified is attribute declaration, then the
> > property is
> > the {attribute declarations}.
> > 1.3 If the kind specified is element declaration, then the property
is
> > the {element declarations}.
> > 1.4 If the kind specified is attribute group, then the property is
the
> > {attribute group definitions}.
> > 1.5 If the kind specified is model group, then the property is the
> > {model group definitions}.
> > 1.6 If the kind specified is notation declaration, then the
> > property is
> > the {notation declarations}.
> > 2 its {local name} matches the *local name* of the *QName*;
> > 3 its {target namespace} is identical to the *namespace name* of the
> > *QName*;
> > 4 its *namespace name* is either the target namespace of the schema
> > document containing the *QName* or that schema document contains an
> > <import> element information item the *actual value* of whose
> > namespace
> > [attribute] is identical to that *namespace name*."
> >
> > As described in point 4, for a namespace to be referenced it MUST be
> > imported explicitly (or be the target namespace of the schema in
> > question). If a namespace is imported by an imported schema it is
not
> > accessible (i.e. namespace imports are not transitive).
> >
> > Matt
> >
> >
> > ----------------------------------------------------------------
> > 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>