[rfc-i] suggestion for the RPC, IEEE standards
tony at gs4nj.org
Tue Jul 21 01:50:45 PDT 2015
I'm thinking that we should create a new bibxml6 / bibxml-ieee seeded
from John Levine's dig of the current IEEE networking standards.
Towards this end, I've taken John Levine's dig at
http://www.taugh.com/ieeestd/, renamed all of the files to
reference.IEEE.<std-number>.xml, added in the XML declarations, and
created this tree:
Please review this list and let me know if there are any issues.
If people think this looks good, I will move it into place as
The next step is to work towards automating the updating of this tree.
Eliot, while I appreciate the work you did to extract those references
from current drafts, I'm hesitant to drop those into place as they have
not been vetted by anyone other than just the author. However, I think
it would be useful to take your tool and run it against a corpus of the
RFC-Editor-vetted XML files, say for RFCs since RFC 6000. I think that
>those< files could be safely added to bibxml2.
On 7/21/15 3:41 AM, John R Levine wrote:
>> I think these scrapers (yours and Eliot's) are great.
>> To be able to introduce some more tool support on the authoring side
>> we'd need to find out how to stabilize these as a service -- this could
>> be a tools service, a secretariat service, an RPC service, etc.
> My IEEE scraper isn't entirely automatic since you have to manually
> download a CSV of the standards from their site first (too much
>> John Levine wrote:
>>> In article <55ACA5CB.3050601 at att.com> you write:
>>>> Please send nominations of additional bibxml2 references to
>>>> citations at rfc-editor.org. This email address was set up several years
>>>> ago and advertised back then, but has seen little traffic.
>>> Turns out it was easier to scrape IEEE standards than I'd thought.
>>> Ninety lines of python did the trick:
>>> (These are the networking standards, I can change a parameter and
>>> get any of
>>> the other ones if we want them.)
More information about the rfc-interest