[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Namespaces,W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProce

• From: Peter Piatko <piatko@r...>
• To: "David E. Cleary" <davec@p...>, Xml-Dev <xml-dev@l...>
• Date: Wed, 01 Aug 2001 12:32:10 -0400

Better minds than mine can say whether my example was a valid schema or not.
FWIW I seem to remember sending it and the example instance through XSV and
getting an OK. (Sorry, I'm not at the right machine to check it right now).

Note that I was not redefining a type.  I was defining two locally scoped
elements that happened to have the same name.

The real issue to me is that this sort of thing is so easy to do in XML
Schema.

Thanks,

Peter

----- Original Message -----
From: "David E. Cleary" <davec@p...>
To: "Xml-Dev" <xml-dev@l...>
Sent: Wednesday, August 01, 2001 11:47 AM
Subject: RE: Namespaces, W3C XML Schema (was Re: ANN: SAX
FiltersforNamespaceProcessing)


> > I don't recall XML Schema permitting multiple redefinitions of the same
> > element type, but I may well be missing something.  Seems like obviously
> > dangerous practice, in any event.
>
> It doesn't. We are not talking redefinitions of types. It is no different
> that having a class foo with a private variable called x of type int and a
> class bar with a private variable called x of type double. Foo can't see
> bar's x and vice-versa. Also, removing x from it's context probably isn't
> usefull.
>
> > To the W3C XML Schema-aware, it may look "special" and have a local
> > context, but to the rest of the world, it looks as if it had been
> > explicitly declared not to be special.  The context understandings
> > surrounding this usage are not intrinsic to anything in XML
> > 1.0+Namespaces.
>
> Your use of XML may have no use of element context (I.E. parent-child
> hierarchy is significant), but you shouldn't think that applys to
everybody.
> I feel context is one of the strengths of using XML. For instance, it is
> important to my application that a street element in a billing address by
> procesed differently than a street in a shipping adress. I will never
> process a street element as a stand alone entity.
>
> Dave
>
>
>
> ------------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: xml-dev-request@l...
>
>

• Follow-Ups:
  • RE: Namespaces,W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProcessing)
    • From: "David E. Cleary" <davec@p...>

• References:
  • RE: Namespaces,W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProcessing)
    • From: "David E. Cleary" <davec@p...>

• Prev by Date: Re: Namespaces,
• Next by Date: Re: Use of XML ?
• Previous by thread: RE: Namespaces,W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProcessing)
• Next by thread: RE: Namespaces,W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProcessing)
• Index(es):
  • Date
  • Thread