> I don't entirely understand your concern here, so it's difficult to
> respond in detail. It seems you're finding it harder than it should
> be to review the status categorization for each header field, or is
> there more?
No, that's it.
> At the end of the day, the specific document format is quite mutable
> -- the raw data is all in RDF/N3, and I can change the software's
> output moderately easily, within limits. My original plan was that
> the summary consists of name + 1-line summary, because that's what
> seemed useful to me. The current format results from some feedback,
> and I'm open to constructive suggestions if the present format is
I just want something that is both reviewable and the same content as
what you are going to give IANA. My guess is that would be simply a
summary table followed by RDF, or just list the headers in sepa rate
sections by status and let the ToC be the summary. If IANA wants the
templates (yuck), then just including a link to the RDF/N3 may be
>> Oh, bugger, never mind -- I was looking at the wrong section
> >> of RFC 3864. Status and provisional are not orthogonal at all.
>> Why the heck was it written that way? Oh well...
> Well, your first take looked closer. From the PoV of the
> registration, they are largely orthogonal, except that the status has
> some bearing on which sub-registry is applicable.
> As for why it was written that way... it's a couple of years ago now
> that this was being reviewed and debated, so the details are now
> fuzzy, but I do remember there were a number of conflicting concerns
> to be navigated. It reflected the balance of consensus at the time.
Sign-up for Ads Free at Mail.com