Re: [Uri-review] URI Review for HELDS URI

"Frank Ellermann" <nobody@xyzzy.claranet.de> Wed, 23 April 2008 22:03 UTC

Return-Path: <uri-review-bounces@ietf.org>
X-Original-To: uri-review-archive@megatron.ietf.org
Delivered-To: ietfarch-uri-review-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E29D3A69F9; Wed, 23 Apr 2008 15:03:53 -0700 (PDT)
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E3523A6B2F for <uri-review@core3.amsl.com>; Wed, 23 Apr 2008 15:03:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 MPiZTFNfFc7c for <uri-review@core3.amsl.com>; Wed, 23 Apr 2008 15:03:51 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 254673A6888 for <uri-review@ietf.org>; Wed, 23 Apr 2008 15:03:50 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Jon4B-0001lm-7r for uri-review@ietf.org; Wed, 23 Apr 2008 22:03:51 +0000
Received: from hmbg-d9b88e16.pool.mediaways.net ([217.184.142.22]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <uri-review@ietf.org>; Wed, 23 Apr 2008 22:03:51 +0000
Received: from nobody by hmbg-d9b88e16.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <uri-review@ietf.org>; Wed, 23 Apr 2008 22:03:51 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: uri-review@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Thu, 24 Apr 2008 00:06:30 +0200
Organization: <http://purl.net/xyzzy>
Lines: 76
Message-ID: <fuobnt$kpq$1@ger.gmane.org>
References: <C27A78BC-55C1-4ADE-9A96-944352BE0929@cisco.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e16.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
Subject: Re: [Uri-review] URI Review for HELDS URI
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: uri-review-bounces@ietf.org
Errors-To: uri-review-bounces@ietf.org

Cullen Jennings wrote:
 
> The following ID contains a new URI scheme:
> http://tools.ietf.org/html/draft-ietf-geopriv-http-location-delivery-07

Hi, I tried to understand what this memo does.

== namespace ==
In 12.1 it creates an URN for the namespace,
specifying a (minimal) XHTML page in the XML
section of the registration template.

Apparently IANA does not use this as intended,
they publish the complete templates as text:

http://www.iana.org/assignments/xml-registry/ns/common-policy.txt
http://www.iana.org/assignments/xml-registry/ns/contact-1.0.txt

The latter says "XML: None.  Namespace URIs do
not represent an XML specification."  In some
cases there are no templates at all, examples:

urn:ietf:params:xml:ns:asnx
urn:ietf:params:xml:ns:caldav

If the whole point of this exercise is to get
a row in in the namespace table, then the 4th
column already is a pointer to the reference,
and IANA doesn't support the creation of XHTML
pages of registration templates in the third
column. 

== schema ==
Apparently chapter 7 could be merged into 12.2.
If BEGIN and END in chapter 12.1 help, then it
might also help in chapter 7 (?)

<http://www.w3.org/2001/03/webdata/xsv> reported
no error for the extracted schema.

== application/held+xml ==
Reviewed on the types list, "LIMITED USE" noted.

== errors ==
12.4 is apparently a registry of error codes for
the held:errorType in the schema, seeded with
seven codes specified in section 6.3.

== URI scheme ==
Finally 12.5 is the helds URI scheme registration.
For the syntax s/see section/see section 8/.  

The memo does not say that relative helds URIs are
not used, maybe it should (?)

I don't see immediately what a "helds" resource is,
is that a kind of redirection ?  "http" already has
redirections, I guess I miss the point.

AFAIK "IETF tree" is a historic term, the memo can
simply say "change controller: IETF", for an RfC 
on standards track the consequences are obvious.

 [RFC 4395 chapter 2.1]
| New URI schemes SHOULD have clear utility to the 
| broad Internet community, beyond that available
| with already registered URI schemes.

How does that fly with "LIMITED USE" for the MIME
type, what's the difference of "held" URIs from say
"http" ?  Is the limitation in 6.5 (locationUriSet)
to offer only one resource per scheme related to
the creation of an entirely new scheme ?

 Frank

_______________________________________________
Uri-review mailing list
Uri-review@ietf.org
https://www.ietf.org/mailman/listinfo/uri-review