[
Lists Home |
Date Index |
Thread Index
]
Knowing what schema individual components come from is really not that
useful when one starts mixing elements. For instance take a look at a
typical RSS 2.0 feed, (http://intertwingly.net/blog/index.rss2) does
having the schema for the Dublin Core and XHTML namespaces really tell
what the type of document they are included in is?
Then again from that example, you may then think all you have to do is
look at the {namespace-uri}local-name of the root element then that also
is naive. For example take a look at SQLXML mapping schemas[0] whose
root element is {http://www.w3.org/2001/XMLSchema}schema.
[0]http://msdn.microsoft.com/library/en-us/sqlxml3/htm/ssxsdannotations_
0gqb.asp
--
PITHY WORDS OF WISDOM
If the crooks are within pistol range, so are you.
This posting is provided "AS IS" with no warranties, and confers no
rights.
> -----Original Message-----
> From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> Sent: Wednesday, July 09, 2003 9:54 AM
> To: Dare Obasanjo
> Cc: Eric van der Vlist; xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Motivations for namespaces (sorry)
>
> It signifies that:
>
> <ns1:SomeDate>2001-01-01</ns1:SomeDate>
>
> is contained in schema Schema1.xsd and that
>
> <ns2:AnotherDate>2001-01-01</ns2:AnotherDate>
>
> is contained in schema Schema2.xsd.
>
> Perhaps that's not the issue we're talking about here?
>
> Kind Regards,
> Joe Chiusano
> Booz | Allen | Hamilton
>
> Dare Obasanjo wrote:
> >
> > Again, how would that help? Although one can tell what the document
> > type is from looking at the namespaces used in the document (using
> > prefixes is such a horrific idea, so I assume you meant using
> > namespaces), this requires scanning the entire document
> first and even
> > then may have problems if some optional namespaced
> components are missing.
|
