Re: [urn] Of RFC3187bis, RFC3188bis and namespace registrations in general
Juha Hakala <juha.hakala@helsinki.fi> Thu, 22 December 2011 12:04 UTC
Return-Path: <juha.hakala@helsinki.fi>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAE421F8B5A for <urn@ietfa.amsl.com>; Thu, 22 Dec 2011 04:04:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.159
X-Spam-Level:
X-Spam-Status: No, score=-4.159 tagged_above=-999 required=5 tests=[AWL=2.440, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOJ9s2IjYXPq for <urn@ietfa.amsl.com>; Thu, 22 Dec 2011 04:04:29 -0800 (PST)
Received: from smtp-rs1-vallila2.fe.helsinki.fi (smtp-rs1-vallila2.fe.helsinki.fi [128.214.173.75]) by ietfa.amsl.com (Postfix) with ESMTP id ED2A821F8B59 for <urn@ietf.org>; Thu, 22 Dec 2011 04:04:27 -0800 (PST)
Received: from [128.214.91.90] (kkkl25.lib.helsinki.fi [128.214.91.90]) by smtp-rs1.it.helsinki.fi (8.14.4/8.14.4) with ESMTP id pBMC4MxM014795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 22 Dec 2011 14:04:22 +0200
Message-ID: <4EF31CC5.3060704@helsinki.fi>
Date: Thu, 22 Dec 2011 14:04:21 +0200
From: Juha Hakala <juha.hakala@helsinki.fi>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4E96C9EA.8070605@helsinki.fi> <4EEBBE82.3090004@stpeter.im> <4EF1CAE2.7000900@helsinki.fi> <B671A4FF-EAD0-4C2B-AE8C-A5C449C0F8ED@hxr.us> <4EF20EF3.8060605@stpeter.im>
In-Reply-To: <4EF20EF3.8060605@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] Of RFC3187bis, RFC3188bis and namespace registrations in general
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 12:04:30 -0000
Hello, Issue tracker has been actively (and I think productively) used in the IRI group. So I am in favour of this suggestion, in principle. In practice isolating and formulating the issues can be complicated to those of us (including myself) who have no first hand experience of such working method. Perhaps IETF veterans could extract a few tangible issues from the discussions we've had on the list of late. Moreover, I would rather not formulate the issues myself since IETF folks may have more objective view on problems that still need to be solved. There are cases in which the document level (small) issues and architectural principles we have discussed are intertwined. For instance, if we agree that URNs can be applied to works, then we should also outline a model of how works and their manifestations are connected to one another, and derive some conclusions as regards what kind of impact this model may have to URN services. Of course we could also start the discussion from the top, agree on a model and then start deriving practical conclusions from there. But this approach would require more faith than the bottom - top -one. Juha Peter Saint-Andre wrote: > <hat type='AD'/> > > On 12/21/11 7:28 AM, Andy Newton wrote: >> Juha (and the WG), >> >> One of the problems I see with these discussions is that these >> threads intertwine noted issues with the documents and larger >> architectural or philosophical issues. That can get confusing. >> >> I would like to ask you, as a document editor, and the working group >> if we should use the issue tracker for dealing with document issues >> so that they do not get lost in the larger debates. Comments? >> >> As for the larger issues, we can discuss them and after there is >> consensus on how to move forward with addressing those issues will be >> able to knock them out through documents. >> >> What say you? >> >> -andy > > Andy, I think that would indeed be helpful. Although the more > "philosophical" issues are interesting and important, we also need to > focus the discussion down to specific text proposals to be incorporated > into the specificuations under consideration. Using the issue tracker > might help move us in that direction. > > Peter > > -- > Peter Saint-Andre > https://stpeter.im/ > -- Juha Hakala Senior advisor, standardisation and IT The National Library of Finland P.O.Box 15 (Unioninkatu 36, room 503), FIN-00014 Helsinki University Email juha.hakala@helsinki.fi, tel +358 50 382 7678
- [urn] Of RFC3187bis, RFC3188bis and namespace reg… Juha Hakala
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… Peter Saint-Andre
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… SM
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… Peter Saint-Andre
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… Juha Hakala
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… Andy Newton
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… Peter Saint-Andre
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… SM
- Re: [urn] Of RFC3187bis, RFC3188bis and namespace… Juha Hakala