FYI: HTTP header fields (re packaging)

A few weeks ago, when we discussed the pros and cons of the new Web Packaging document, Brady emphasized the power of having explicit metadata for each 'part' within the package offered by the HTTP Headers which, according to the packaging definition, is available within the package by virtue of the fact that each part begins with what is essentially an HTTP header. I have just run into this:

https://github.com/dret/sedola/blob/master/MD/headers.md

which is a list of the 152 'official' headers that are already defined somewhere, which is, therefore, a vocabulary available in packaging, too. Nice list... Not all of the list may be immediately meaningful in an EPUB-WEB setting, but one may never know... For example, all the fields related to the life-span of a given part may be used to renew one part of a document without necessary downloading the whole package. Headers like 'Link' are actually starting point for further vocabulary items, because a Link has a 'rel' parameter which is defined as a 'link relation' which are registered elsewhere...

Ivan






----
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704