Re: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt and all_id.txt

[Fred Baker <[e-mail]>]

quite a few of our documents are not submitted to working groups. Did  
you intend to have "ietf" as a potential working group? How did you  
want to handle that?

Personally, I would like to find individual submissions to working  
groups as well as working group documents here, perhaps with an  
attribute distinguishing them. The way we do this now is that working  
group documents are named draft-ietf-<wg>-... while individual  
submissions to working groups are named draft-<author>-<wg>-...  
Submissions that are not to a working group are draft-<author>-...  
and don't name a WG. But the secretariat only keeps track of the one  
category. That's mostly a database question, but it raises the  
question of an attribute that indicates working group status.

In a tool/page that used this, I would appreciate having a mailto  
link that got me to the authors, as in
     <a href="mailto:[e-mail]">authors</a>,
similar links that got me to the relevant working group chairs and  
ADs, and a link that got me to the ID tracker, as in
     <a href="https://datatracker.ietf.org/idtracker/? 
&search_filename=draft...">ID Status</a>

I don't think that has to be in the XML description of the doc, but  
is certainly derivable from the data and would be useful.


On Apr 23, 2008, at 3:41 PM, Tony Hansen wrote:

> There was some discussion recently of having an xml version of the
> internet-drafts files 1id-*.txt and all_id.txt.
>
> Moving this further along, I'd like to make concrete proposals for the
> schema for such files. First off, for 1id-abstract, the schema  
> would be
> (I'm not an expert at DTDs, so forgive any errors here):
>
> <!ELEMENT internet-drafts (docs working-group-map)>
>    <!ELEMENT docs (doc*)>
>      <!ELEMENT doc (name, author, date, wg, file, abstract?)>
>        <!ELEMENT name (#PCDATA)>
>        <!ELEMENT author (#PCDATA)>
>        <!ELEMENT date (#PCDATA)>
>        <!ELEMENT wg (#PCDATA)>
>        <!ELEMENT file (#PCDATA)>
>        <!ELEMENT abstract (#PCDATA)>
>    <!ELEMENT working-group-map (group*)>
>      <!ELEMENT group (acronym, name)>
>        <!ELEMENT acronym (#PCDATA)>
>        <!ELEMENT name (#PCDATA)>
>
> Translation:
>    <internet-drafts> contains <docs> and <working-group-map>
>    <docs> contains 1 or more <doc>
>    <doc> contains a <name>, <author>, <date>, <wg>, <file> and  
> <abstract>
>    The <wg> contains a working group acronym.
>    At the end is a map from working group acronyms to spelled out  
> names.
>    <working-group-map> contains 1 or more <group>
>    Each <group> contains an <acronym> and <name>.
>
> A sample would look like this:
>
>      <?xml version='1.0' encoding='UTF-8'?>
>      <internet-drafts>
>      <docs>
>      <doc>
>       <name>Transmission of IP over Ethernet over IEEE
>        802.16 Networks</name>	
>       <author>HongSeok Jeon</author>
>       <date>18-Apr-08</date>
>       <wg>16ng</wg>
>       <file>draft-ietf-16ng-ip-over-ethernet-over-802.16-06.txt</file>
>       <abstract>
>        This document describes the transmission of IPv4 over ...
>      </doc>
>      ...
>      </docs>
>      <working-group-map>
>      <wg>
>       <acronym>16ng</acronym>
>       <name>IP over IEEE 802.16 Networks</name>
>      </wg>
>      <wg>
>       <acronym>6man</acronym>
>       <name>IPv6 Maintenance</name>
>      </wg>
>      ...
>      </working-group-map>
>      </internet-drafts>
>
> A complete sample file can be seen at
>     http://merlot.tools.ietf.org/~tonyh/internet-drafts/1id- 
> abstracts.xml
>
> For all_id.xml, I'm proposing this schema:
>
> <!ELEMENT all-internet-drafts (id*)>
>    <!ELEMENT id (file, date, status, tracker?, iesg?, by?, rfc?)>
>      <!ELEMENT file (#PCDATA)>
>      <!ELEMENT date (#PCDATA)>
>      <!ELEMENT status (#PCDATA)>
>      <!ELEMENT tracker (#PCDATA)>
>      <!ELEMENT iesg (#PCDATA)>
>      <!ELEMENT by (#PCDATA)>
>      <!ELEMENT rfc (#PCDATA)>
>
> Translation:
>    <all-internet-drafts> contains one or more <id>
>    Each <id> contains a <file>, a <date>, and a <status>
>    Depending on the value of <status>, there may be a <tracker>, a
>    <iesg>, a <by> and a <rfc>.
>
> A sample would look like this:
>
>    <all-internet-drafts>
>      <id>
>        <file>draft-adolf-dvb-urn-03</file>
>        <date>2007-12-18</date>
>        <status>In IESG processing</status>
>        <iesg>Revised ID Needed</iesg>
>      </id>
>      <id>
>        <file>draft-cain-post-inch-phishingextns-03</file>
>        <date>2007-10-25</date>
>        <status>In IESG processing</status>
>        <tracker>Publication Requested</tracker>
>      </id>
>      <id>
>        <file>draft-zorn-radius-port-type-04</file>
>        <date>2006-04-04</date>
>        <status>RFC</status>
>        <rfc>4603</rfc>
>      </id>
>      <id><file>draft-yokota-mipshop-3gfh-02</file>
>        <date>2008-03-03</date>
>        <status>Replaced</status>
>        <by>draft-ietf-mipshop-3gfh</by>
>      </id>
>    </all-internet-drafts>
>
> A complete sample file can be seen at
>     http://merlot.tools.ietf.org/~tonyh/internet-drafts/all_id.xml
>
> Thoughts?
>
> 	Tony Hansen
> 	[e-mail]
> _______________________________________________
> Tools-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tools-discuss

_______________________________________________
Tools-discuss mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/tools-discuss