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

[<[e-mail]>]

Here's a sample from the code I currently have:

<id xml:id="draft-ietf-xcon-framework">
  <id>draft-ietf-xcon-framework</id>
  <documentInfo>
    <docValidity>Active</docValidity>
    <revision>10</revision>
    <revisionDate>2007-11-09</revisionDate>
    <idTrackerTag>13106</idTrackerTag>
    <fileTypes>.txt</fileTypes>
    <title>A Framework for Centralized Conferencing</title>
    <author>
      <email>[e-mail]</email>
      <name>Mary Barnes</name>
    </author>
    <author>
      <email>[e-mail]</email>
      <name>Chris Boulton</name>
    </author>
    <author>
      <email>[e-mail]</email>
      <name>Orit Levin</name>
    </author>
    <abstract>
This document defines the framework for Centralized Conferencing.<br />
The framework allows participants using various call signaling<br />
protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange<br />
media in a centralized unicast conference.  The Centralized<br />
Conferencing Framework defines logical entities and naming<br />
conventions.  The framework also outlines a set of conferencing<br />
protocols, which are complementary to the call signaling protocols,<br />
for building advanced conferencing applications.  The framework binds<br />
all the defined components together for the benefit of builders of<br />
conferencing systems.</abstract>
    <group>xcon</group>
  </documentInfo>
  <stateInfo type="idTracker">
    <state>IESG Evaluation</state>
    <subState>Revised ID Needed</subState>
    <lastModifiedDate>2007-11-09</lastModifiedDate>
    <idTrackerToken>Cullen Jennings</idTrackerToken>
    <intendedStatus>Proposed Standard</intendedStatus>
  </stateInfo> 
</id>

Some explanation:

"docValidity" is one of: Active, Expired, RFC, Withdrawn by submitter, 
Withdrawn by IETF, and Replaced. All Internet-Drafts are in one of
these states.

The <stateInfo type="idTracker"> describes what IESG is doing 
with the document. A document could also have similar blocks
for <stateInfo type="rfcEditor"> and <stateInfo type="iana">.

Best regards,
Pasi

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of ext Tony Hansen
> Sent: 24 April, 2008 01:41
> To: [e-mail]
> Cc: Bill Fenner; Henrik Levkowetz; Glen Barney
> Subject: [Tools-discuss] xml version of 
> 1id-abstracts.txt/1id-index.txt andall_id.txt
> 
> 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