At 08.04 +0100 0-10-14, Graham Klyne wrote:
Specifically, I would like there to be an XML namespace URI
associated with an IANA registry for RFC822 headers. From this,
according to RDF URI-construction rules, would follow a URI for each
header in the registry.
So, yes: I think Jacob's 1998 draft would form a good starting
point for such a registry. I think I'd focus more on simply
creating a single registry of header field names and references to
definitions, and slightly less on trying to categorize different
flavours of header field. If there's a consensus that this is a
Good Thing, I'll undertake to review and comment on Jacob's draft
with a view to moving it towards a registry BCP.
I also think that Jacob's mail header summary draft would be a good
starting point for initially populating the registry. The
registration template might be tuned with an eye to information that
is readily available in this draft, so that the initial
registrations are easily constructed.
The controversy when this was discussed years ago was what
requirements one should put to include a header field name
in the registry.
Very strong requirements ^ Only headers from published IETF standards.
|
+ Only headers approved by a thorough vetting
| procedure.
|
+ Only headers accepted by a vetting procedure
| similar to that for new Content-Types.
|
Very lenient requirements v All reasonable proposals accepted.
Arguments for strong requirements: Avoid badly defined headers
to get into the registry.
Arguments against strong requirements: New headers would not get
into the registry, because of the difficulty in getting them
registered. And no large harm is done by adding a header which
never succeeds, there are lots of synonyms to use. For example,
suppose the registry register a badly defined "Obsoletes", IETF
can then define a better defined header, and call it "Replaces"
or "Supersedes". The badly designed header can stay in the
registry, possibly with a note saying that its use is not
recommended.
--
Jacob Palme <jpalme(_at_)dsv(_dot_)su(_dot_)se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/