Re: [urn] Comments/answers to reasons for changes in PWID URN version 4 - diff version 3 and 4

Eld Zierau <elzi@kb.dk> Wed, 27 February 2019 12:59 UTC

Return-Path: <elzi@kb.dk>
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 D7F6E130EBE for <urn@ietfa.amsl.com>; Wed, 27 Feb 2019 04:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ql6haA3BwsIv for <urn@ietfa.amsl.com>; Wed, 27 Feb 2019 04:59:55 -0800 (PST)
Received: from smtp-out12.electric.net (smtp-out12.electric.net [89.104.206.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 488E2130FF7 for <urn@ietf.org>; Wed, 27 Feb 2019 04:59:55 -0800 (PST)
Received: from 1gyyoS-000cZe-UX by out12d.electric.net with emc1-ok (Exim 4.90_1) (envelope-from <elzi@kb.dk>) id 1gyyoS-000cbi-W1; Wed, 27 Feb 2019 04:59:52 -0800
Received: by emcmailer; Wed, 27 Feb 2019 04:59:52 -0800
Received: from [130.226.226.11] (helo=post.kb.dk) by out12d.electric.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from <elzi@kb.dk>) id 1gyyoS-000cZe-UX; Wed, 27 Feb 2019 04:59:52 -0800
Received: from EXCH-02.kb.dk (unknown [10.5.0.112]) by post.kb.dk (Postfix) with ESMTPS id 63DBA13A19; Wed, 27 Feb 2019 13:59:52 +0100 (CET)
Received: from EXCH-02.kb.dk (10.5.0.112) by EXCH-02.kb.dk (10.5.0.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 27 Feb 2019 13:59:52 +0100
Received: from EXCH-02.kb.dk ([fe80::b595:1a1f:5666:b29]) by EXCH-02.kb.dk ([fe80::b595:1a1f:5666:b29%7]) with mapi id 15.01.1713.004; Wed, 27 Feb 2019 13:59:52 +0100
From: Eld Zierau <elzi@kb.dk>
To: "Svensson, Lars" <L.Svensson@dnb.de>, "Dale R. Worley" <worley@ariadne.com>
CC: "urn@ietf.org" <urn@ietf.org>
Thread-Topic: Re: [urn] Comments/answers to reasons for changes in PWID URN version 4 - diff version 3 and 4
Thread-Index: AdSuc3Sm32TiMBAVSZKSdHKbD7LiBAC8br3ABZFh66AAkA1pQAEa0hiQ
Date: Wed, 27 Feb 2019 12:59:51 +0000
Message-ID: <4cbc052832f2451d818a1c461116acfc@kb.dk>
References: <0a8299a1afb643abb1466b4b0735c12c@dnb.de> <ecf37bf20f7a4dc584a90ebdda71d435@kb.dk> <93d95097d40f4bd8becf1c7a8e056ca9@dnb.de>
Accept-Language: da-DK, en-US
Content-Language: da-DK
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.226.229.95]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-IP: 130.226.226.11
X-Env-From: elzi@kb.dk
X-Proto: esmtps
X-Revdns: post-03.kb.dk
X-HELO: post.kb.dk
X-TLS: TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256
X-Authenticated_ID:
X-PolicySMART: 10573177
X-Virus-Status: Scanned by VirusSMART (c)
X-Virus-Status: Scanned by VirusSMART (s)
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/P4olvcY8mdRSVw6KV_ke0YafazU>
Subject: Re: [urn] Comments/answers to reasons for changes in PWID URN version 4 - diff version 3 and 4
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Wed, 27 Feb 2019 13:00:00 -0000

I have now uploaded a new version with clarifications. I have also had it through an additional language review, and sharpened the language.

I have plans (and allocated time) to start a process of proposing a registry, but it will be much easier to proceed this work if there is an accepted PWID URN to refer to.
Furthermore, I have spoken to the Open Preservation Foundation about hosting a PWID resolver (based on our prototype), which they are interested in. 

Hope this satisfy the comments, otherwise please let me know.

Best regards, Eld
 
-----Original Message-----
From: Eld Zierau 
Sent: Thursday, February 21, 2019 2:45 PM
To: 'Svensson, Lars' <L.Svensson@dnb.de>; Dale R. Worley <worley@ariadne.com>
Cc: urn@ietf.org
Subject: RE: Re: [urn] Comments/answers to reasons for changes in PWID URN version 4 - diff version 3 and 4

Thank you Lars

I expect to upload a new version next week which makes these clarifications

Best regards, Eld

-----Original Message-----
From: Svensson, Lars <L.Svensson@dnb.de>
Sent: Monday, February 18, 2019 6:06 PM
To: Eld Zierau <elzi@kb.dk>; Dale R. Worley <worley@ariadne.com>
Cc: urn@ietf.org
Subject: RE: Re: [urn] Comments/answers to reasons for changes in PWID URN version 4 - diff version 3 and 4

Dear Eld,



*  'precision-spec' values are not case sensitive (i.e.  "PAGE" /
         "PART" / "PaGe" / ... are valid values as well.)

On Monday, January 21, 2019 2:15 PM, Eld Zierau [mailto:elzi@kb.dk] wrote:

> Is there any particular area you  think needs approvement?

Having re-read the I-D, I'd say that there are two areas still unclear to me:
1) The syntax specification says
*  'precision-spec' values are not case sensitive (i.e.  "PAGE" /
         "PART" / "PaGe" / ... are valid values as well.) It says nothing about the other parts so I guess that case sensitiveness defaults to the specification in RFC 8141 §3 [1] which says that all parts of URNs are case sensitive except for the string "urn" and the NID. It would be helpful, though, if that was made explicit (including a reference to RFC 8141 §3).

2) The document refers to a (proposed) registry of archive names without giving any particulars of where this will be set up and who will manage it. If you say that there currently is no information about that, that's fine, otherwise it would be helpful to get more information on that (especially if it's going to be operated by IANA).

[1] https://tools.ietf.org/html/rfc8141#section-3.1

Best,

Lars
 
> -----Original Message-----
> From: Svensson, Lars <L.Svensson@dnb.de>
> Sent: Thursday, January 17, 2019 3:47 PM
> To: Dale R. Worley <worley@ariadne.com>; Eld Zierau <elzi@kb.dk>
> Cc: urn@ietf.org
> Subject: RE: Re: [urn] Comments/answers to reasons for changes in PWID 
> URN version 4 - diff version 3 and 4
> 
> Apologies for not commenting on this draft until now...
> 
> Version 4 of PWID has matured considerably compared to version 3 and I 
> think it needs at the most one or two more iterations until it's ready for registration.
> 
> I find the discussion about an IANA registry for names of web archives 
> very interesting and would support the creation of such a registry.
> The number of such archives will probably be of manageable size (about 
> the same size as the number of national libraries...).
> 
> I also have a number of minor editorial issues but would wait with 
> those until the contents of the draft are more stable.
> 
> Best,
> 
> Lars
> 
> > -----Original Message-----
> > From: urn [mailto:urn-bounces@ietf.org] On Behalf Of Dale R. Worley
> > Sent: Monday, November 05, 2018 2:02 AM
> > To: Eld Zierau <elzi@kb.dk>
> > Cc: urn@ietf.org
> > Subject: [Marketing Mail] Re: [urn] Comments/answers to reasons for 
> > changes in PWID URN version 4 - diff version 3 and 4
> >
> > Eld Zierau <elzi@kb.dk> writes:
> > > Here is the promised Word file with differences between version 3 
> > > and 4
> >
> > > [2:application/vnd.openxmlformats-officedocument.wordprocessingml.
> > > do
> > > cument
> > Show Save:PWID_from_V3_to_V4.docx (81kB)]
> >
> > Why not just give the URL to the datatracker's history page for the I-D:
> > https://datatracker.ietf.org/doc/draft-pwid-urn-specification/histor
> > y/ and the URL for the diff between v3 and v4, in the format that 
> > basically everybody in the IETF is familiar with:
> > https://www.ietf.org/rfcdiff?url1=draft-pwid-urn-specification-03&ur
> > l2
> > =draft-pwid-
> > urn-specification-04
> >
> > Dale
> >
> > _______________________________________________
> > urn mailing list
> > urn@ietf.org
> > https://www.ietf.org/mailman/listinfo/urn