- From: Jodi Schneider <jschneider@pobox.com>
- Date: Tue, 20 Jan 2015 11:05:02 +0100
- To: public-lod@w3.org
- Message-ID: <CAP5TGf84g=vyv1EsGb6JCOgvqy-rsuqnNhOYbnFV6o7h-rr_eQ@mail.gmail.com>
> > From: Herbert Van de Sompel <hvdsomp@gmail.com> > Date: Mon, 19 Jan 2015 18:10:45 -0700 > Message-Id: <464E492A-1394-4A59-9C1D-520F9CB631B9@gmail.com> > Cc: "public-lod@w3.org" <public-lod@w3.org> > To: Larry Masinter <masinter@adobe.com> > > Larry > How about HTTP Link headers (RFC 5988) to convey links and metadata > expressed as links when serving PDFs? I can imagine an authoring tool > embedding the info in XMP. But I have a harder time imagining a consumer > application that would want to read the info via XMP. > I don't: Bibliographic managers for PDFs could make use of XMP metadata. Imagine never typing another citation again! > How about a web server add-on that can extract (and map/transform.) the > info from the XMP container as the PDF is being served. And stuff it all in > the HTTP Link header on the fly. > This of course is a good idea but I don't think it's either/or. -Jodi > Cheers > Herbert
Received on Tuesday, 20 January 2015 10:05:31 UTC