[
Lists Home |
Date Index |
Thread Index
]
You could, if you wanted, use a namespace filter to coerce unqualified
elements into that namespace during processing - before or after
transmission. Integrating that with SOAP processing might not be much fun,
but it's possible.
I wrote some basic (Java) tools for doing this kind of thing, available at:
http://simonstl.com/projects/namespace/
I should add something that qualifies all unqualified children of a given
element and variations on that.
At 09:07 AM 5/29/2003 -0400, Joe Gregorio wrote:
>Now this could be solved by declaring an optional namespace for RSS 2.0
>that could be used in just such a case:
>
><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:rss2="http://backend.userland.com/rss/";
> <soap:Header/>
> <soap:Body>
> <rss2:rss version="2.0">
> <rss2:channel>
> <rss2:title>...
>
>I have also run into such a need in other cases, for example
>I have worked with a group that is, at best, namespace allergic.
>Getting them to place the vocabulary we are working on in a namespace
>will be impossible. On the other hand, getting them to agree to an optional
>namespace to be used when combining our work other vocabularies may be
>palatable. What are the pros and cons of such
>an approach?
>
> Thanks,
> -joe
>
>[1] http://backend.userland.com/rss/
>[2] http://www.intertwingly.net/blog/1354.html
>
>--
>http://BitWorking.org
>http://WellFormedWeb.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>
|
