- From: Mark Baker <distobj@acm.org>
- Date: Wed, 30 Oct 2002 13:56:41 -0500
- To: www-ws-arch@w3.org
I was going to send this to xml-dist-app directly, but figured that it
might best be first discussed here. It also seems to overlap with
Chris' concern about "comment 1" too.
The bit I'm concerned about is;
"The integrity of references (i.e. URIs) to secondary parts MUST
be maintained accross SOAP intermediaries. That is, a URI which
resolves to a secondary part in an inbound SOAP message MUST
continue to resolve to that part in the outbound message, unless
that part was removed by the SOAP intermediary."
This could be interpreted as suggesting that URIs cannot be rewritten,
though I'm not sure if that's the intent or not. Plus it seems to
exclude using URIs whose identified resource changes state over time,
as it requires that resolution continue to yield the same content.
With respect to the former issue, a valuable use of intermediaries
could be rewriting URIs to effect resolution of previously unresolvable
references. For example, changing cid URIs to be http URIs that point
back to the representation cached at the intermediary.
For the latter issue, I think it would suffice to not mention resolution
at all (I'm assuming that it isn't the intent to suggest that a URI for
a part must always resolve to the same content), and instead just say
something akin to;
"URI ambiguity: Ambiguity in the relationship between URIs and
resources is harmful for humans and machines."
-- http://www.w3.org/2001/tag/2002/WD-webarch-20021029#identifiers
MB
--
Mark Baker, CTO, Idokorro Mobile. Ottawa, Ontario, CANADA.
http://www.markbaker.ca http://www.idokorro.com
Received on Wednesday, 30 October 2002 13:54:19 UTC