Hi, as per my action item I hereby propose a reformulation of the
XMLP-UC-2 use case [1] generated during the face-to-face meeting.
The use-case can be taken to mean two things:
1) an application wants to send some piece of data along with the
message and the app wants to identify the data using a URI; the first
part of this is covered by first two of Mark's use-cases [2] and the
second part is just an implementation detail.
2) an application wants to send a representation of a web resource along
with the message and possibly expects that the receiver gets the
representation when it dereferences the resource's URI. Below is a
reformulation of this.
--- Representation Use Case
An application wishes to send in a message a URI, which the receiver
will dereference. The receiver has limited access to the world wide web
so the sender chooses to "bundle" a representation of the resource in
the message, too, so that the receiver may choose this representation in
case the resource identified by the URI is inaccessible to it.
--- UC end
Notes: the use case has many variants we might want to consider: the
sender wants the receiver always to use the provided representation; the
reason for sending a representation along is not the limitation of the
receiver but elimination of dereferencing overhead; the sender may want
to include all available metainformation (like HTTP headers) that the
receiver would get when dereferencing the resource etc.
Share and enjoy!
Jacek Kopecky
Senior Architect
Systinet Corporation
http://www.systinet.com/
[1] burried in http://www.w3.org/2000/xp/Group/3/03/06-minutes.html
[2] http://lists.w3.org/Archives/Public/xml-dist-app/2003Sep/0008.html