W3C home > Mailing lists > Public > spec-prod@w3.org > April to June 2012

Re: [rfc-i] IETF RFC format <-> W3C pubrules

From: Paul E. Jones <paulej@packetizer.com>
Date: Wed, 09 May 2012 09:19:52 -0400
Message-ID: <4FAA6EF8.5050600@packetizer.com>
To: Julian Reschke <julian.reschke@gmx.de>
CC: Phillip Hallam-Baker <hallam@gmail.com>, rfc-interest <rfc-interest@rfc-editor.org>, Paul Hoffman <paul.hoffman@vpnc.org>, spec-prod@w3.org
On 5/9/2012 9:11 AM, Julian Reschke wrote:
>>> ...which means: little metadata or no metadata to rely on, right?
>>
>> I am not sure quite what you mean there.
>
> A way to programatically extract all the information xml2rfc captures 
> for us, such as author names, WG information, "updates"/"obsoletes" 
> information, references, ABNF, copyright status, ...

The RFC Editor publishes all of this metadata as an XML document that is 
independent of any RFC.  Why would we need to have this information 
inside the RFC itself?  And if we did, some information would still be 
lacking.  For example, if an RFC is updated or is made obsolete, the XML 
document published by the RFC Editor would contain that information, but 
an RFC document obviously cannot predict the future.

I have a tool (not xml2rfc) that provides this metadata to me based on 
the aforementioned XML document.  I don't see a need to have it somehow 
bound to the format of the RFC itself.

Paul
Received on Wednesday, 9 May 2012 13:20:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 13:20:33 GMT