2006/2/13, Eric Scheid <[EMAIL PROTECTED]>: > > On 13/2/06 8:50 PM, "Thomas Broyer" <[EMAIL PROTECTED]> wrote: > > > We were talking about pictures, so they probably are in JPEG or TIFF format. > > PNG doesn't support EXIF but has textual [1] and timestamp [2] information. > > JPEG2000 seems to have something similar too [3]. > > > > If we had been talking about an article or some documentation, the > > binary resource would probably have been represented in MSWord, ODF or > > PDF, which support embedded metadata. > > > > If we had been talking about songs or audio interviews, the binary > > resource would probably have been represented in MP3, OggVorbis > > Sounds like a lot of work to support metadata for binary data. Lots of work, > incomplete coverage, and unending as new resource types come into vogue.
I'm not arguing in favor of metadata extraction (at least as the only mean of providing metadata), I think Multipart/Related or "POST a non-Atom entity to create a compound entry" (generating two URLs: one for the Atom Entry containing metadata, the other for the non-Atom resource ; the Atom Entry can be initialized from metadata extracted from the non-Atom entity) are better approaches. I understand that Multipart/Related cannot be in the core (requires quoted-printable and binary decoders, CID URL handling, etc.) but the other solution could very well be. Another solution could be WebDAV's PROPFIND and PROPPATCH. -- Thomas Broyer
