[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xml-dev] So maybe ID isn't a problem after all.
Gavin Thomas Nicol wrote:
> In the above scenario, what you're left with is the fact that in order to
> uniquely, and reliably address a given octet sequence (entity body), you have
> to provide a URI, a complete set of headers (Accept*), a server, the server
> configuration, and all of the "entity bodies" as well, and even then, you
> might not have it.
Right. If you grab many of the resources at www.weather.com today, for
example, you will get completely different entity bodies from what
you would have gotten yesterday. That's the idea; people want a
particular URI (= resource) to specify the current (varying) weather.
The only way to reliably address a given entity body is to use a
data: URL, and even then you have to mention the media type
by which the octets are to be interpreted. Type the URL
data:text/html,<p><b>boldface</b></p> into a Netscape/Mozilla
browser to see the effect.
> I don't think that's what people expect.... and I'm sure the web services
> folk will be none too happy about it.
>
> -----------------------------------------------------------------
> 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>
>
>
--
Not to perambulate || John Cowan <jcowan@reutershealth.com>
the corridors || http://www.reutershealth.com
during the hours of repose || http://www.ccil.org/~cowan
in the boots of ascension. \\ Sign in Austrian ski-resort hotel