Joe Gregorio wrote:
What is the rme: namespace? Do all clients need to support rme?
I made up the namespace, clients do not need to support it, it was a
means to distinguish the different images based on size. There are
probably better ways of doing it.
How does rme help the client pick a representation in the
calendar examples which started this discussion?
It is not needed in the Calendaring example as the media type is enough
to distinguish between the representations.
Maybe the wording needs to be reworked. What I would like to
see is that content/@src MUST be supplied and that it indicates
the 'preferred' read-only resource for the server, the client
is free to choose among all the link/@rel="whatever"s if it so
chooses for another resource.
k, this seems reasonable. I think the important point is that a client
can use any representation returned by the entry and is not restricted
to content/@src. How about adding this paragraph to Section 8.3
"When referencing a media resource a client can choose from any of the
representations supplied in the corresponding Media Link Entry. The
content/@src attribute value is used by the server to indicate its
preferred read-only reference to the media resource."
Also in re-reading PaceMediaEntries4 it is not clear that a non-entry
POST i.e. a media POST, must return a media link entry vs. any old entry.
I'd suggest adding the following line to the end of the first paragraph
in Section 8.1.
"If the post request body does not contain an atom entry then
the resulting Atom Entry must be a Media Link Entry (see section 8.3)"
