On 4/24/06, Bill de hÓra <[EMAIL PROTECTED]> wrote:
> James M Snell wrote:

> > The Entry includes one atom:link with a link relation of "enclosure",
> > and a second with a link relation "edit-enclosure", respectively
> > identifying the IRI's used for public read-only referencing of the media
> > resource and the IRI to be used for modifying the media resource.
>
> I'm -1 to this part. Why do we need to divide safe and unsafe operations
> using URIs, when HTTP has methods for doing that across one URI already?

But what if there is more than one URI? The example is
one URI for read-only usage and the other for
the editing interface.

  http://static.example.org/images/mycat.png

  http://app.example.org/jcgregorio/edit.cgi/mycat.png

Sure they could be the same and
so the values of rel="enclosure" and rel="edit-enclosure" would
be the same in that case, but I believe there needs to
be a way to support two URIs and a hint to the client
as to the use of each.

   -joe

--
Joe Gregorio        http://bitworking.org

Reply via email to