binary/file resource metadata

say you GET some /a.jpg

and additionally you want to return RDF about this image (tags, geodata, comments, distillations from EXIF)

i asked about a GETMETA and was told thats synonymous with HEAD.. only true if your RDF/metadata is all in the header.

so there is a Link/N3 header proposed. that feels kinda nasty to me. id rather use RDF to express all the headers (gaining flexibility, and eliminating the need for this hack), than embed RDF inside a particular field (which has the bonus of backwards compatibiltiy with unmaintained UAs


what about Multipart-Mixed reponses. eg returning image/jpeg data, as well as a text/n3 file. can Tabulator or any tool grok these kind of responses ?

does anyone have a preference for one technique over the other?

Received on Friday, 25 July 2008 02:21:23 UTC