Re: [urn] Revised registration request for URN:NAN

"Palek, Stephanie" <S.Palek@dnb.de> Fri, 04 August 2023 07:05 UTC

Return-Path: <S.Palek@dnb.de>
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 0ABE6C1519AD for <urn@ietfa.amsl.com>; Fri, 4 Aug 2023 00:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 v_qt3HVX9bHZ for <urn@ietfa.amsl.com>; Fri, 4 Aug 2023 00:05:46 -0700 (PDT)
Received: from mail.dnb.de (mail.dnb.de [193.175.100.144]) (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 CB71AC15109C for <urn@ietf.org>; Fri, 4 Aug 2023 00:05:44 -0700 (PDT)
Received: from dnb-tmg.ad.ddb.de (tmg.dnb.de [10.69.66.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.dnb.de (Postfix) with ESMTPS id D466044F2AAE; Fri, 4 Aug 2023 09:05:41 +0200 (CEST)
Received: from dnb-tmg.ad.ddb.de (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 976B0A4056; Fri, 4 Aug 2023 09:05:41 +0200 (CEST)
Received: from dnb-tmg.ad.ddb.de (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 82A6BA4055; Fri, 4 Aug 2023 09:05:41 +0200 (CEST)
Received: from dnbf-ex2.AD.DDB.DE (unknown [10.69.63.216]) by dnb-tmg.ad.ddb.de (Postfix) with ESMTPS; Fri, 4 Aug 2023 09:05:41 +0200 (CEST)
Received: from dnbf-ex1.AD.DDB.DE (10.69.63.215) by dnbf-ex2.AD.DDB.DE (10.69.63.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.7; Fri, 4 Aug 2023 09:05:41 +0200
Received: from dnbf-ex1.AD.DDB.DE ([fe80::3518:9c6b:49b8:3f94]) by dnbf-ex1.AD.DDB.DE ([fe80::3518:9c6b:49b8:3f94%15]) with mapi id 15.02.1118.007; Fri, 4 Aug 2023 09:05:41 +0200
From: "Palek, Stephanie" <S.Palek@dnb.de>
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>, Peter Saint-Andre <stpeter@stpeter.im>, KA Urnnan <urn.nan@kansallisarkisto.fi>, "urn@ietf.org" <urn@ietf.org>
Thread-Topic: [urn] Revised registration request for URN:NAN
Thread-Index: AdnEe3a68Z27IC1LSKiP9P75ltX60gBrGQAAABZeXoAACCj2xQ==
Date: Fri, 04 Aug 2023 07:05:41 +0000
Message-ID: <f34dbacb283e4d979be79867f0305ce2@dnb.de>
References: <AS8P250MB09113A5B8D5DF3E537F16FF0E80AA@AS8P250MB0911.EURP250.PROD.OUTLOOK.COM> <8329c875-532f-a794-42ed-23920d7036df@stpeter.im>, <HE1PR07MB31965D4A33300FA58887959AFA09A@HE1PR07MB3196.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB31965D4A33300FA58887959AFA09A@HE1PR07MB3196.eurprd07.prod.outlook.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.10.62.20]
Content-Type: multipart/alternative; boundary="_000_f34dbacb283e4d979be79867f0305ce2dnbde_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27792.005
X-TM-AS-User-Approved-Sender: Yes
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27792.005
X-TMASE-Result: 10--37.960500-10.000000
X-TMASE-MatchedRID: LRBaXANrGXUNUiaAWwmuxpKLzY5ZrthjQPyBMHbx9hDJp5KLMM+APMEF 2dna2cy2vROWIJWaJeiUI512D01p9AjKq2eYHyXoCtzGvPCy/m74uJ1REX4MHY2cB1+t/hle8Jg qp/3e7hcTev6ffZr1JUamcsBmD02oJRswfCj8+JoB6/aPodnUlvZqI0nPzd0HZRL+gCLSlhdbSq bRYRhask0XjoveWX5i1C/tIUW+pI/bNA9j/y5B6xwbN4ob6DCIW+HVwTKSJIa2HpC95B+yo1kxG kh/RUoEwl89VZlzFaKkh51KSUs/hYinnDXTBDFzxqtsVI8KrJoHivd5s4SnRf3WejIIgb2agCSs 04iA5GmO147yBvPXlZU3joA9t6uXkMfljouhjsEI8o+oRtTdk6EetkTb5LzrLX3qyf3ewG+yOf3 T1hTX8yTXv8i+fF1n0Pb29MNs8EDL1IusN7305Bqkhv3OdF4DltF+xW+zhUh0Tsch72XSbNAJqU aPKd8T9kNGk0VfW+xZVLW7lIwJG7iMqFcspGv3L09GQoaNa5f2TYt281WiziDMMrn5euRZ1lZR6 zMFxpDvRWVG2VJhQHdNoXv6UJm+CXBdHc83YVm1PiMh4ZF39XzIY7d2+Tz9StFk/81wIJID86Cs Xb/sJnbkRTu4+B9NEEliPV4b9y50ihL2oMtB41ICmG2RRehoXxwZhwnDGWpWcVQdwdqmz+l5Hsz 52t/e0CxNzIrWQH5ffyFrK1eRJNSxXbZonmxOYrc32n84WHq87rU89eLPKbrECTa0H+9MIeIBv2 Vzhzo0IXF7YXZ/Cy6wIaekxCtkxJlOCgB0mldANB89sV0bJ30tCKdnhB58r10pknZXGJrkNFVV6 EQ08vf+rQTw1K5q33fj+sMArfMaMUyeC0staEkVAPr0TXS8
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/iJJLqk-LQEOKJ6D6cjoX02a3kBc>
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: Fri, 04 Aug 2023 07:05:50 -0000

Dear all,


I approve as well and have no further comments.


All the best,

Stephanie

________________________________
Von: urn <urn-bounces@ietf.org> im Auftrag von Hakala, Juha E <juha.hakala@helsinki.fi>
Gesendet: Freitag, 4. August 2023 07:11:15
An: Peter Saint-Andre; KA Urnnan; urn@ietf.org
Betreff: Re: [urn] Revised registration request for URN:NAN

Hello,

I approve of this registration, and look forward to the co-operation between the National Library and the National Archive in the implementation of this new identifier system.

Juha

-----Alkuperäinen viesti-----
Lähettäjä: urn <urn-bounces@ietf.org> Puolesta Peter Saint-Andre
Lähetetty: torstai 3. elokuuta 2023 21.31
Vastaanottaja: KA Urnnan <urn.nan@kansallisarkisto.fi>; urn@ietf.org
Aihe: Re: [urn] Revised registration request for URN:NAN

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 mailing list
urn@ietf.org
https://www.ietf.org/mailman/listinfo/urn
_______________________________________________
urn mailing list
urn@ietf.org
https://www.ietf.org/mailman/listinfo/urn