Re: GVAT registration request
"Miksa, Tomasz" <[email protected]>
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
Thanks again for the careful review of our specifications. You helped us improve it. I enclose hopefully the final revision. I made the following changes: 1. Fixed the notation for the object as suggested by Dale. It is now: 1*(%x41–5A / %x61–7A / %x30–39 / %x2D). I know that it allows a situation in which the object consists of "-" only, which may not be ideal, but I believe it is better to keep the formulation simple, rather than come up with something more complex like 1*(%x41–5A / %x61–7A / %x30–39) (%x41–5A / %x61–7A / %x30–39 / %x2D) 2. Rephrased the Resolution section as suggested by @Juha. It captures very well the gist of what we are up to. Apart from this, no other changes were made. Cheers Tomasz -----Original Message----- From: Lars G. Svensson <[email protected]> Sent: piątek, 21 kwietnia 2023 11:26 To: Peter Saint-Andre <[email protected]>; Dale R. Worley <[email protected]>; Miksa, Tomasz <[email protected]> Cc: [email protected] Subject: Re: [urn] GVAT registration request Having read the specification, I have no comments and agree with the registration of GVAT as a urn namespace. Best, Lars Am 18.04.2023 um 22:38 schrieb Peter Saint-Andre: > On 4/18/23 12:43 PM, Dale R. Worley wrote: >> I have only one remaining comment. There appears to be a typo: >> >> "Miksa, Tomasz" <[email protected]> writes: >> ... >>> Ad. object >>> Yes, we are aware of the lack of German characters. We really intend >>> to ensure no semantics in the identifiers. One change we did was to >>> introduce the "-", to have better overlap with UUID and DOIs, in >>> case any of them is used in the future. Now it is: >>> 1*(%x41–5A / %x61–7A / %x30–39 ) %x2D >> ... >>> object = 1*(%x41–5A / %x61–7A / %x30–39 ) %x2D >> ... >> >> As written, this means one or more alphanumeric characters, then >> always followed by "-". I assume that the intent is >> >> object = 1*(%x41–5A / %x61–7A / %x30–39 / %x2D >> ) >> >> that is, alphanumerics arbitrarily mixed with "-". > > Good catch, and agreed. > > Peter > > _______________________________________________ > urn mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/urn _______________________________________________ urn mailing list [email protected] https://www.ietf.org/mailman/listinfo/urn
GVAT-template.txt
(text/plain, 2.7 KB)
Namespace Identifier: GVAT
Version: 1.0
Date: 2023-05-01.
Registrant:
Bundeskanzleramt der Republik Österreich
Ballhausplatz 2, 1010 Wien, Austria
[email protected]
Purpose:
The GVAT URNs identify all types of digital objects of Austrian government institutions and organizations in the possession of the Austrian administration.
The GVAT URNs allow unambiguous identification of digital objects, thus improving their findability and reusability. The GVAT URNs also help internal systems to better track provenance and object evolution.
The GVAT URN namespace is independent of any existing URN namespaces, URI schemes, and non-URN identifier systems.
The resolution mechanism is anticipated for URNs assigned within the GVAT namespace. The Austrian Federal Chancellery will operate an internal resolution service.
The GVAT URN namespace is not expected to become a constituent part of a standard being developed in the IETF or some other recognized standards body.
Syntax:
The syntax for the GVAT URN namestring is defined using the Augmented Backus-Naur Form (ABNF) below.
namestring = assigned-name
assigned-name = "urn:gvat:" NSS
NSS = delegation-area-number "/" object
delegation-area-number = 1%x31–39 3%x30–39 1%x31–39
object = 1*(%x41–5A / %x61–7A / %x30–39 / %x2D)
Assignment:
The registration of URNs within the GVAT namespace is limited to Austrian government institutions and organizations in the possession of the Austrian administration. The Austrian Federal Chancellery decides which further institutions or organizations get the right to assign URNs within the GVAT namespace, that is, to become delegated authorities.
Each delegated authority gets its own delegation area number, a unique part of the NSS. Thus, there are no collisions among URNs minted by different delegated authorities. Each delegated authority is individually responsible for the uniqueness of URNs assigned by it and for conformance with the syntax of the GVAT URN namespace.
Security and Privacy:
The identifiers do not include any semantics. There is no public resolution service. There are no specific security and privacy constraints stemming directly from the GVAT URN syntax and assignment strategy.
Interoperability:
No interoperability issues are known at this stage.
Resolution:
A resolution mechanism is anticipated for URNs assigned within the GVAT namespace, but primarily for internal and non-public use.
Documentation: None
Additional Information: None
Revision Information: None