Re: [Uri-review] Allow identifying issues with ISSN NID

David Booth <david@dbooth.org> Thu, 21 May 2009 12:20 UTC

Return-Path: <david@dbooth.org>
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 56E533A6B26 for <uri-review@core3.amsl.com>; Thu, 21 May 2009 05:20:13 -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 mPjen5bAfIHx for <uri-review@core3.amsl.com>; Thu, 21 May 2009 05:20:12 -0700 (PDT)
Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by core3.amsl.com (Postfix) with SMTP id 4C9E23A69C0 for <uri-review@ietf.org>; Thu, 21 May 2009 05:20:12 -0700 (PDT)
Received: (qmail 65623 invoked from network); 21 May 2009 12:21:48 -0000
Received: from 64.134.135.163 (HELO ?64.134.135.163?) (64.134.135.163) by relay03.pair.com with SMTP; 21 May 2009 12:21:48 -0000
X-pair-Authenticated: 64.134.135.163
From: David Booth <david@dbooth.org>
To: "Daniel R. Tobias" <dan@tobias.name>
In-Reply-To: <4A146848.2315.E7ECD29@dan.tobias.name>
References: <35A23FE7952844FBA667A306B8CDC982@POCZTOWIEC> , <B7FB6772505B40DB9AF8AA1E119240B4@POCZTOWIEC> , <1242846763.4093.167.camel@dbooth-laptop> <4A146848.2315.E7ECD29@dan.tobias.name>
Content-Type: text/plain
Date: Thu, 21 May 2009 08:21:49 -0400
Message-Id: <1242908509.446.57.camel@dbooth-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
Content-Transfer-Encoding: 7bit
Cc: uri-review@ietf.org
Subject: Re: [Uri-review] Allow identifying issues with ISSN NID
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
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>
X-List-Received-Date: Thu, 21 May 2009 12:20:13 -0000

On Wed, 2009-05-20 at 20:30 -0400, Daniel R. Tobias wrote:
> On 20 May 2009 at 19:12, David Booth wrote:
> 
> > The owner of a URI space can define whatever syntactic conventions are
> > desired for minting URIs in that URI space, and can publish these
> > conventions just as the conventions for URNs were published.
> 
> How does any of this become normative, authoritive, and binding on 
> anybody including the issuer him/herself?  

The same way it does for standards organizations.  For the most part,
standards organizations only have as much authority as people choose to
give them: most standards are voluntary.  When W3C issues a standard --
what it calls a "Recommendation" -- it has garnered enough community
support, and the W3C has enough respect as a standards body, that many
implementers *choose* to follow it.  When W3C -- and I'm only taking W3C
as an example -- publishes a specification it creates a social
expectation that if others choose to use it, they will do so in
accordance with the specification.  The big difference between you (as
an individual) issuing a specification and the W3C issuing a
specification is one of degree, not kind: the W3C specification is more
authoritative only because people know W3C's reputation.  This, in turn,
creates the social expectation that people *will* faithfully follow the
specification when they claim to be following it.

See the Architecture of the World Wide Web on URI ownership:
http://www.w3.org/TR/webarch/#uri-ownership

> I own the domain dan.info, 
> and I can issue whatever proclamations I want about URIs within it, 
> like "http://dan.info/dogs/fido" refers to a dog named Fido, but why 
> should anybody regard this as having any standards-level authority, 
> and if the following day I said I was only kidding about that dog 
> stuff, which statement would have more authority?

By doing so dan.info would be establishing itself as unreliable, so
people would be unlikely to use that URI to refer to Fido.

The point is that URNs are not the only *mechanism* that can be used to
establish the URI convention that you want.  http URIs are (in my view)
a superior mechanism to URNs.  But the mechanism is only one part of
establishing the convention.  The important part is to gather sufficient
community support and institutional commitment to back it up, so that it
will have credibility and people will choose to follow it.  And this is
independent of mechanism.


-- 
David Booth, Ph.D.
Cleveland Clinic (contractor)

Opinions expressed herein are those of the author and do not necessarily
reflect those of Cleveland Clinic.