[
Lists Home |
Date Index |
Thread Index
]
I don't think I downgraded the priority on that last message. Maybe the
mail list is developing sentience?
One thing to add:
There's no mechanism, short of possible legal contrivances (or maybe very
locked-up schemas [if you're validating against one]), to prevent authors
from inserting all sorts of original junk in a namespace. There is no
namespace membership control.
> -----Original Message-----
> From: Jeff Lowery [mailto:jlowery@scenicsoft.com]
> Sent: Monday, December 16, 2002 10:58 AM
> To: 'Simon St.Laurent'; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] nested namespaces
> Importance: Low
>
>
> > Does it make sense to design a vocabulary such that:
> >
> > <item xmlns:dc="http://purl.org/dc/elements/1.1/";>
> > <title>My Summer Vacation</title>
> > <description>On my summer vacation I went to...</description>
> >
> > <link>http://127.0.0.1/cgi-bin/RESTLog.py/4</link>
> > <dc:date>2002-10-28T22:18:53-05:00</dc:date>
> > </item>
> >
> > is considered equivalent (even when you're not using SOAP) to:
> >
> > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/";>
> > <s:Body>
> > <item xmlns:dc="http://purl.org/dc/elements/1.1/";>
> > <title>My Summer Vacation</title>
> > <description>On my summer vacation I went to...</description>
> >
> > <link>http://127.0.0.1/cgi-bin/RESTLog.py/4</link>
> > <dc:date>2002-10-28T22:18:53-05:00</dc:date>
> > </item>
> > </s:Body>
> > </s:Envelope>
>
> I don't see how you can extract content out of the context of
> a container
> with any assurance of understanding it's meaning. Taking your original
> example,
>
> > <item xmlns:dc="http://purl.org/dc/elements/1.1/";>
> > <title>My Summer Vacation</title>
> > <description>On my summer vacation I went to...</description>
> >
> > <link>http://127.0.0.1/cgi-bin/RESTLog.py/4</link>
> > <dc:date>2002-10-28T22:18:53-05:00</dc:date>
> > </item>
>
> We might have in the same document:
>
> <item xmlns:dc="http://purl.org/dc/elements/1.1/";>
> <diary>2002-10-28</diary>
> <dc:date>Had a hot one with Mindy tonight. Hachacha!</dc:date>
> </item>
>
> Without context, you'd have to resort to parsing values to
> determine intent.
>
>
>
>
>
>
>
>
>
> >
> > We can just ignore the s:Enveloper and s:Body tags, right?
> Or can we?
> > What's over-complicated here? (The unqualified nature of the item
> > vocabulary raises another nice set of questions about what is
> > complicated or not, but that's another issue.)
> >
> > --
> > Simon St.Laurent
> > Ring around the content, a pocket full of brackets
> > Errors, errors, all fall down!
> > http://simonstl.com -- http://monasticxml.org
> >
> > -----------------------------------------------------------------
> > 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 subscribe or unsubscribe from this list use the subscription
> > manager: <http://lists.xml.org/ob/adm.pl>
> >
>
> -----------------------------------------------------------------
> 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 subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
|
