Re: [urn] Request for the NID 'ddi'

Joachim Wackerow <> Mon, 08 February 2021 20:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 522043A150F for <>; Mon, 8 Feb 2021 12:53:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Status: No, score=-2.119 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id V-gg2gtXJfBD for <>; Mon, 8 Feb 2021 12:53:10 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 89BC13A15CB for <>; Mon, 8 Feb 2021 12:52:41 -0800 (PST)
Received: from submission ( []) by (Postfix) with ESMTPS id 5B16016005C for <>; Mon, 8 Feb 2021 21:52:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=2017; t=1612817558; bh=KhVGrefGmjkBWVzu58Vp+lKPiXrrFi+hWYxx5ft41xI=; h=From:To:Subject:Date:From; b=Q0brpxjuvzbeT6UQhEZ3YJPjCy/93d5D/njYY7/Vx88DJ5RD7b/OHpABzhDcwTUgQ 1qzMlYKPhTt6Jd35DBHGSEUXXykZUG0J2/o//ya10UIw2kVTqMWxCjVu4oa/rmUBG9 U6nj0T9BGf3uGScpMSkOoJZNDANMZPV0n+JKBIvr90Dx1ltM9B00uRoyg8aYXxGmwo ne2JtTwuabvFd3DHFxGkNizd75o/JDtbPjoS5FCR/IbBcTsHVLLgmpbKqwJ24BGZGP oQ0TeluFgOJwjTfZpq2D8nlUFI3JjpE7Npa/5QJfhP/lnxaCMQWWCO4DIYyZDCma93 lO1gUXqLfcpnQ==
Received: from customer (localhost []) by submission ( with ESMTPSA id 4DZJBB1R2zz9rxB for <>; Mon, 8 Feb 2021 21:52:33 +0100 (CET)
From: Joachim Wackerow <>
References: <009101d6effb$79e26c00$6da74400$> ( <> <> <03a401d6f427$2fbf33d0$8f3d9b70$>
In-Reply-To: <03a401d6f427$2fbf33d0$8f3d9b70$>
Date: Mon, 08 Feb 2021 21:52:33 +0100
Message-ID: <00e201d6fe5c$534efc60$f9ecf520$>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_00E3_01D6FE64.B5164A90"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHW8HHSs/jTBhoHTVS4R3ZNnD7+eaozSH6AgAckbPCAFGBDcA==
Content-Language: de
Archived-At: <>
Subject: Re: [urn] Request for the NID 'ddi'
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Feb 2021 20:53:19 -0000

Hello Dale, Juha and all,

Attached is the new version with changes according to your comments.
Thanks again for the detailed hints.

The Word version can be viewed in review mode to see easily all the changes
in the document.

Please look at my comments (starting with "[JW]") below in the text
regarding the individual topics.

Please tell me if there are any open issues.


-----Original Message-----
From: urn <> On Behalf Of Joachim Wackerow
Sent: Dienstag, 26. Januar 2021 22:07
Subject: Re: [urn] Request for the NID 'ddi'

Hello Dale and Juha,

Thank you very much for your quick response and detailed advice. I'll look
into this and make changes accordingly.


-----Original Message-----
From: urn <> On Behalf Of Hakala, Juha E
Sent: Freitag, 22. Januar 2021 10:01
To: Dale R. Worley <>; Joachim Wackerow
Subject: Re: [urn] Request for the NID 'ddi'


I agree with Dale that the document is well done overall, but contains some
glitches. IMO this registration will be very useful, since urn:ddi URNs will
make easier to understand DDI metadata and resources. I hope that other
metadata initiatives will follow DDI's example and register their own
namespaces in the future, or use urn:meta, if and when it is approved. 

The Word version of the request is complete, unlike the txt version.
[JW] Sorry, something was broken. It should be resolved now.

I have comments about agency-identifier part of the DDI NSS. The request

"The left-most label of agency-identifier conveys the top-level domain. It
SHOULD be a country code corresponding to ISO 3166 alpa-2 codes [ISO3166] or
another top-level domain."

There are no other options than ISO 3166-1 country code or something else,
so SHALL is more appropriate than SHOULD. 
[JW] Changed accordingly in the document.

The request does not describe how uniqueness of top-level domains is
ensured. There are at least two simple solutions for this. Either the
request provides a list of non-country code top-level domains, or says that
the DDI Alliance or some other organization maintains a registry of such
[JW] Additional wording on DDI Alliance registry in the document.

I suppose non-county code top-level domains include "int" for international
organizations, or acronyms of such organizations, like FAO or UNESCO, or
other acronyms relevant in the research data context. In order to avoid
problems in the future, you may want to say that all two-letter top-level
domains are reserved for current and future ISO 3166 codes.  
[JW] Additional wording regarding TLDs and suggested sentence in the

Description in 3.4.1 does not say that within agency-identifier the
top-level domain and subdomains are separated by full stop. This is shown in
the syntax in 3.4.3, but could be mentioned in 3.4.1 too. You might also
want to say in the description that full stop is not allowed within
top-level domain names or subdomain names. 
[JW] Addition wording in the document.

Registration of DDI namespace and usage of URN:DDI identifiers are separate
but interlinked issues. I took a look at your examples, and found it
interesting that US translation of PISA questionnaire is identified with URN


Finnish translation of the PISA questionnaire will certainly get a different
URN. But these translations could also share a URN like
urn:ddi:int.PISA_QS:1 to indicate the common semantics between Finnish and
U.S. PISA questionnaires. 
[JW] The DDI agency which publishes the metadata item provides the agency
identifier independently of the language of the content and independently of
the original author of the content. This kind of information can be
mentioned in specific metadata fields. The translation can either be in the
same document (by means of xml:lang) - this would trigger a new version - or
can be in another document where the source (including the original URN) of
the translation is mentioned.

All examples of version identifiers in the registration and linked documents
are numbers. Do you want to / need to allow other options? 
[JW]  Yes, the ABNF and the regular expression define the allowed characters
which include other options.

I suppose the actual usage of URNs in the DDI Alliance specifications is
still work in progress, since some documents have URNs which are not
compliant with this request. For instance, DDI Controlled Vocabulary for
Aggregation Method version 1.0
has URN urn:ddi-cv:AggregationMethod:1.0. According to the registration,
version 1.1 will have correct URN,
As an aside, the link (which is not functioning)  is for version 1.0.   
[JW] Yes, this is right. The CVs must be updated according to the definition
her. The mentioned URL is corrected in the document.

Best regards, 


-----Alkuperäinen viesti-----
Lähettäjä: urn <> Puolesta Dale R. Worley
Lähetetty: perjantai 22. tammikuuta 2021 5.51
Vastaanottaja: Joachim Wackerow <>
Aihe: Re: [urn] Request for the NID 'ddi'

"Joachim Wackerow" <> writes:
> Please find attached an URN namespace registration request for DDI, 
> Data Documentation Initiative (NID 'ddi').

The document draft-urn-ddi-01.txt was attached to your message, but that
document contains only sections 3.4.4 and following.
[JW] Sorry, something was broken. It should be resolved now.

Based on the draft-urn-ddi-01.pdf:

Generally, the document is quite well done.  Some specific issues are:

    ; agency-identifier is case-insensitive. See [RFC4343] section 2.
    ; For allowed characters see [RFC1035] section 2.3.1.
    ; For length restrictions see [RFC2181] section 11.
    agency-identifier = 1*255( top-level-domain
                               sub-separator ddi-authority-id
                               *(sub-separator ddi-sub-authority-id)
    top-level-domain = dns-label
    ddi-authority-id = dns-label
    ddi-sub-authority-id = dns-label

I think you want to remove the "1*255( ... )" -- that means "repeat the
stuff inside the parentheses from 1 to 255 times".  I think you're trying to
use it to mean "the total length of this string must be from 1 to 255
characters", but that's not what it means.  You would need to state a length
limit in a comment, or leave it to be implied by the reference to RFC 2181.

    dns-label = 1*63( (ALPHA / DIGIT) [
                      *(ALPHA / DIGIT / "-")
                      (ALPHA / DIGIT)
                      ] )

I think this is another example of the same issue.
[JW] "1*255" and "1*63" are removed in the document. Related comments
regarding the length limits and reference to RFC 2181 are added to the ABNF.

    resource-identifier = restricted-string
                          *(restricted-string / "/")
    version-identifier = restricted-string
                         *(restricted-string / "/")
    restricted-string = 1*( unreserved / sub-delims / "@")

I don't think the first two definitions are what you mean.  What they mean
is "a restricted-string, followed by zero or more things which are either
restricted-strings or slashes".  When you sort it all out, it is equivalent

    resource-identifier = ( unreserved / sub-delims / "@" )
                          *( unreserved / sub-delims / "@" / "/")

In particular, that allows two slashes to be adjacent in resource-identifier
(as long as they aren't the first two characters).

It's more likely you want:

    resource-identifier = restricted-string
                          *("/" restricted-string)
[JW] Changed accordingly in the document.

That is, a resource-identifier is a sequence of one or more
restricted-strings, separated by slashes.

Parallel changes would be needed in section 3.4.3.
[JW] Changed accordingly in the document.

In section 3.4.4 "Examples", it might be useful to note that the DDI URNs of
Represented Variables etc. are not syntactically distinct.
Although if the distinction between these categories of resources is
important in the DDI universe, you might mention how, if one possesses a DDI
URN, one would determine what category it belongs to.
[JW] Clarifying wording added in the document.


urn mailing list

urn mailing list

urn mailing list