[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PaceControlResource, PacePubControl, PacePubStatusResource... seeking consensus




Eric Scheid wrote:


On 14/7/05 2:31 AM, "Bill de hÓra" <bill@xxxxxxxxxx> wrote:


I'm also curious to know how to set /collection/member@title for non-atom
resources, and how come we can't set any other metadata for these resources.


Eric, do you have an example we can talk through?


Take images for example. Some metadata I might like to store with the
resource is geo:latitude, or even simple meta data such as foaf:depicts (I
have too many photos from conventions and parties where I'm left scratching
my head figuring out who the heck that other person is). I could try packing
some of this into the file name, but that's clunky, and also prone to
failure as a server implementation is free to ignore the HTTP Name header
and assign whatever it wants to the resource.

I could also try packing this into /collection/member@title ... if I knew
how (and didn't gag on the clunkyness of it).


Or you could post your photos base64-encoded within an Atom Entry Document, using atom:title, atom:summary, atom:rights and other extension elements to add metadata to the photo...

Or, if you don't want to base64-encode the photo, post the photo to a "photo collection" and then post an Atom entry, using atom:content/@src, to a "photo metadata collection"... (the only problem here is that you must retrieve the photo collection once more to get the photo's @hrefreadonly; or you could then use a "compound entry" [1] and post the photo + Atom entry to a "photo-with-metadata collection")

[1] http://intertwingly.net/wiki/pie/PaceCompoundEntries

--
Thomas Broyer