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

Tony Hansen <tony@att.com> Wed, 23 April 2008 22:40 UTC

Return-Path: <tools-discuss-bounces@ietf.org>
X-Original-To: tools-discuss-archive@megatron.ietf.org
Delivered-To: ietfarch-tools-discuss-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D26583A6C07; Wed, 23 Apr 2008 15:40:19 -0700 (PDT)
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5194A3A6C07 for <tools-discuss@core3.amsl.com>; Wed, 23 Apr 2008 15:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPtRwuI-8LBv for <tools-discuss@core3.amsl.com>; Wed, 23 Apr 2008 15:40:17 -0700 (PDT)
Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by core3.amsl.com (Postfix) with ESMTP id 697D63A67A5 for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 15:40:17 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-10.tower-203.messagelabs.com!1208990414!7372682!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.141]
Received: (qmail 29324 invoked from network); 23 Apr 2008 22:40:15 -0000
Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com) (144.160.128.141) by server-10.tower-203.messagelabs.com with AES256-SHA encrypted SMTP; 23 Apr 2008 22:40:15 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id m3NMeL5W006976 for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 15:40:22 -0700
Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11]) by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id m3NMeH7Q006955 for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 15:40:17 -0700
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m3NMeHFM031836 for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 17:40:17 -0500
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m3NMeCCO031584 for <tools-discuss@ietf.org>; Wed, 23 Apr 2008 17:40:12 -0500
Received: from [135.210.32.184] (unknown[135.210.32.184](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20080423224011gw100l7o6qe> (Authid: tony); Wed, 23 Apr 2008 22:40:11 +0000
Message-ID: <480FBB16.9020603@att.com>
Date: Wed, 23 Apr 2008 18:41:26 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: tools-discuss@ietf.org
X-Enigmail-Version: 0.95.6
Cc: Bill Fenner <fenner@gmail.com>, Henrik Levkowetz <henrik@levkowetz.com>, Glen Barney <glen@amsl.com>
Subject: [Tools-discuss] xml version of 1id-abstracts.txt/1id-index.txt and all_id.txt
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

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
	tony@att.com
_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss