Re: [urn] Revised registration request for URN:NAN
Peter Saint-Andre <stpeter@stpeter.im> Thu, 03 August 2023 18:31 UTC
Return-Path: <stpeter@stpeter.im>
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 0864BC14CEFF for <urn@ietfa.amsl.com>; Thu, 3 Aug 2023 11:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level:
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.091, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b="SkCnaB91"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="wDiMhYEk"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FTOmdwJzaXA4 for <urn@ietfa.amsl.com>; Thu, 3 Aug 2023 11:31:17 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B53FC15DF52 for <urn@ietf.org>; Thu, 3 Aug 2023 11:30:49 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6597F5C0224; Thu, 3 Aug 2023 14:30:48 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 03 Aug 2023 14:30:48 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1691087448; x=1691173848; bh=NWXNFulrU/6bAjdBPzwVvKh9fjijnYCY8hl RoNQBgog=; b=SkCnaB91fMAdzkQHRuYZNZtHGUWJudTleW1zQ8k29dtMg72oZOi a/M76kAl+Ra6zKQPQ2fZYTm4xKWfQe/bYnSjN3uwvFeRfr1sFM/CfW5F2q+auVcO UaOHru/Hjep7HUFZERF5+n7UMZ0UVUlBhoNeVZ55gVTgtcs308PWm9LYRZ2ox9tP WW1+DPXrIZZG3VitIf+EroAZmjD45PjA0zXxSVHKKOh963p/0izuut6/viv/YzG1 vq4qdJglJwutDSdqOPdvcpzDQgvBn+m8FjYr+Y1CAXeLrXpPgV/SLE2P7vkAqZDQ 73GRgtVYZMIHkp3DaIxl/AWAn1ybWgyVZCg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1691087448; x= 1691173848; bh=NWXNFulrU/6bAjdBPzwVvKh9fjijnYCY8hlRoNQBgog=; b=w DiMhYEkPQk43cGeorIBHEq9LlpyirveiJIsK1bvKQeZTcKbeVeCtilGoE8TeO1et /cAzgUhtlvexZN1L3utuN1exlBHkd52hwqtNX6w/1E+zDNfM7/flfTjMhmK0WpeD kiqJxTkjuHhylljhgdoLAwlk71yfwdKd9SpMr9pNUHBMXFpwjBZWwB9/OY45ZeIi ArXm25d/VDa5s1qLjiAQZgPeQis4SUHqOn/s+xt5P9WkUGzZuuf5ApRcC/ZNIfPE xkpRmtINuO3Ke1vUv/h5gQKNPTvVyeoB1ACjudEFuxEksLPpqi+3s1xu4u1p99dw h2Tsc77kwQWyVHARH0N4A==
X-ME-Sender: <xms:V_LLZELbsJKcVfwvXFnPGYt8p25tBZZ_7pw6rOpngYBI5C_ibBvWeg> <xme:V_LLZELDGP_-Z0Ww0bp4qsJIXKhYtOTHMgJjjmv_Muhh_nzuZJXtwAOcJ9TLG5UYt pntfLFN8SLoPeZUzA>
X-ME-Received: <xmr:V_LLZEvHMBHiCTw31cet3XF9KqbviFWetI17s74LZHMdaFDzA2JxlxUrtvVTX0YG>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrkedvgdduvdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtfeejnecuhfhrohhmpefrvghtvghrucfurghinhhtqdetnhgurhgvuceoshhtphgv thgvrhesshhtphgvthgvrhdrihhmqeenucggtffrrghtthgvrhhnpeevueefjeduieeiie dtiedvfeefkeejvefgleeghfdvvddvffevgeffgedtudegteenucffohhmrghinhepihgv thhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:V_LLZBap2Sw85-Ekswgprg10BsaVYfWU9ebZRBC1508THvbRP5gYiA> <xmx:V_LLZLaGItfpVs0SU2cYog8YVRshggiB6A3xp6IWGayI97vunrPBkg> <xmx:V_LLZNB7aSO8ROal3yhEylLfkelUOsvf1l8XtA-A8K2x8WwKnuvxHQ> <xmx:WPLLZCyBmC3cwLoaJMZVSK1IuxPincKPWtwd7tQ3z1FRWpbOsnHejw>
Feedback-ID: i24394279:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 3 Aug 2023 14:30:47 -0400 (EDT)
Message-ID: <8329c875-532f-a794-42ed-23920d7036df@stpeter.im>
Date: Thu, 03 Aug 2023 12:30:46 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
Content-Language: en-US
To: KA Urnnan <urn.nan@kansallisarkisto.fi>, "urn@ietf.org" <urn@ietf.org>
References: <AS8P250MB09113A5B8D5DF3E537F16FF0E80AA@AS8P250MB0911.EURP250.PROD.OUTLOOK.COM>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <AS8P250MB09113A5B8D5DF3E537F16FF0E80AA@AS8P250MB0911.EURP250.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/YUz5bl44ww6_m6N1mYyz3OV_MDo>
Subject: Re: [urn] Revised registration request for URN:NAN
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 03 Aug 2023 18:31:22 -0000
Hello Lauri, Thank you for this note and for the updated registration request. I approve of registration. Once we hear back from other members of the expert review team, I can work with you on a few small editorial matters and ask IANA to complete the registration. Peter On 8/1/23 9:59 AM, KA Urnnan wrote: > Dear recipients, > > Thank you all for an elightening conversation and on-point corrections > to the registration request, and apologies for the tardiness of my > reply; I was on vacation, and due to technical equipment failure was > unable to access my work email. I have amended the request according to > the helpful suggestions. Please find the resubmission attached. > > On a general note, I could try to conceptualize the difference between > NBN and NAN. The main difference stems from the identified material > itself, and reflects the well established practices of division of > responsibility between libraries and archives. While the NBN is assigned > to published material that does not have publisher-issued identifier and > concerns mainly works of literary/bookish nature (e.g. master’s theses, > ephemera), the NAN will be assigned to archival material. Or in other > words unique, unpublished and often non-literary (in the strict sense) > primary sources (e.g. letters, charters, minutes, manuscripts, maps, > drawings, etc.). While NBN could be assigned to e.g. a self-published > autobiography lacking an ISBN, and it would identify the (in FRBR terms) > work-expression-manifestation -levels, NANs could be assigned to the > work’s authorial working manuscript and notes associated to it, and > similar item-level objects (again in FRBR-terms). In other words, there > should be not much conceptual or factual overlap in the material that > NBN and NAN refer to. The other main difference lies in the organisation > of materials. Archival sources are organised into hierarchical structure > consisting of archival entities, series and units, all of which can be > given unique identifiers. Thus the resource which is identified with a > NAN number is very much different from that identified with a NBN number. > > Mainly for these conceptual reasons the NBN as identifier for archival > material is out of the question. It has well established and defined > usage which does not lend itself for use with archival sources. > Assigning NBN’s for our material would only create confusion in the > field. The only main exception (that I can think of) to the division of > material described above concerns some older historical sources, mainly > of literary nature (e.g. late medieval manuscripts and letters). Such > material can be found in both libraries’ and archives’ collections for > historical reasons. Yet, this material has only rarely been assigned any > NBN:s, and the overlap remains therefore minimal in terms of magnitude > as well as conceptually. Since the practices between archives and > libaries are well established, I found it unnecessary to list this as a > restriction in the registration. While it leaves open the definition of > pertinent material, this might also mean that URN:NAN could help to fill > in the gaps left by URN:NBN in the identification of archival > collections in libraries. It also leaves the door open for national > archives to implement their own practices as they see fit. Hopefully > this attempt of clarification answers at least some of the questions raised. > > Regarding the informational RFC: at the moment I would personally see it > as an overextension of preliminary definitions. Once URN:NAN has been > implemented by us and at least a few other national archives, however, I > believe it would be definitely useful to write one. At that point in > time we would have experience of usage, understanding of the most > pertinent questions, borderline cases and problems encountered, and > would be the better able to formulate necessary clarifications to using > URN:NAN. > > Looking forward to hearing from you, > > Best regards, > > Lauri Leinonen > > > _______________________________________________ > urn mailing list > urn@ietf.org > https://www.ietf.org/mailman/listinfo/urn
- [urn] Revised registration request for URN:NAN KA Urnnan
- Re: [urn] Revised registration request for URN:NAN Peter Saint-Andre
- Re: [urn] Revised registration request for URN:NAN worley
- Re: [urn] Revised registration request for URN:NAN Hakala, Juha E
- Re: [urn] Revised registration request for URN:NAN Palek, Stephanie
- Re: [urn] Revised registration request for URN:NAN Peter Saint-Andre
- Re: [urn] Revised registration request for URN:NAN Peter Saint-Andre