Re: IANA Update: Project to convert registries to XML

Julian Reschke <julian.reschke@gmx.de> Tue, 15 July 2008 11:18 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 84F313A686A; Tue, 15 Jul 2008 04:18:05 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F46B3A686A for <ietf@core3.amsl.com>; Tue, 15 Jul 2008 04:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level:
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599]
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 E9TRg6qqJVeL for <ietf@core3.amsl.com>; Tue, 15 Jul 2008 04:18:03 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id A52203A65A6 for <ietf@ietf.org>; Tue, 15 Jul 2008 04:18:02 -0700 (PDT)
Received: (qmail invoked by alias); 15 Jul 2008 11:18:28 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.106]) [217.91.35.233] by mail.gmx.net (mp015) with SMTP; 15 Jul 2008 13:18:28 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18I9ocmM+gIhqXH0x9Jmk/3cdcnFsbcWfvrbwCuzc gNkRG7TEcq61ru
Message-ID: <487C877F.7080101@gmx.de>
Date: Tue, 15 Jul 2008 13:18:23 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Michelle Cotton <michelle.cotton@icann.org>
Subject: Re: IANA Update: Project to convert registries to XML
References: <C4A11B67.1C74E%michelle.cotton@icann.org>
In-Reply-To: <C4A11B67.1C74E%michelle.cotton@icann.org>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.61
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi,

this looks really good; a simple XML format, XSLT provided, registry 
served both as XML and proper XHTML.

Here are a few question/suggestions though...:

1) When you say

> All existing URLs to protocol registries shall continue to work, and the new
> formats will be available from our website at http://www.iana.org/protocols/
> as they are rolled out.

...is that just for a transition period? Will the new formats eventually 
served for the old URLs?

2) I think it would be good to have stable HTTP URLs both to registries 
and individual registrations. For "simple" registries, would it be 
possible to assign predictable and stable id attributes to the XML (and 
the XHTML), so linking to fragments would work?

3) Registry format: I like registries that not only reference RFCs, but 
also tell their readers which section of the document has the reference. 
Will this be supported as an option?

4) Finally an idea for future work: use GRDDL 
(<http://www.w3.org/TR/grddl/>) to extract RDF from the registries.

BR, Julian

PS: Are people involved with this present in Dublin?
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf