Local resolution service for URN resolution

[cessda-bitbucket-importer]

Original report on BitBucket by Taina Jääskeläinen.

---

The resolution of the URN requires things:

1. registry of agency in the DDI Agency Registration (done)
2. link from that registered agency ID to the local resolution service supporting use of the CVs at either of those locations
3. ARPA registration of the DDI URN (this is in process but is not yet complete)

Wendy has asked Dan Smith to confirm that both of these agency ID's have filed links. Achim is working on #3.

Developer to work on issue 2.

[cessda-bitbucket-importer]

Original comment by John Shepherdson (GitHub: john-shepherdson).

---

For information (received 2020-11-05)

‌

From: Wendy Thomas 

Sent: torstai 5. marraskuuta 2020 18.09

To: Taina Jääskeläinen (TAU) ; Joachim Wackerow 

Subject: Agency identification for CV's re: TC-218 and TC-219

 

Taina and Joachim,

TC-218:

There is a long trail of discussion on the agency identifier for DDI CVs. It was clarified at least by September 2020 that the agency identification is:

int.ddi.cv

It is filed in registry.ddialliance.org as the main agency only

int.ddi

Sub agency resolution handled by the main agency int.ddi

It was also recommended in September that Cessda use a similar structure filing int.cessda and using .cv as a sub-agency which they handle.

Both DDI and CESSDA have filed their main agency identification in the DD agency registry. 

It seems to be a matter of implementing the use of the agency identification by both CESSDA and DDI Controlled Vocabulary.  

TC-219:

TC is working on this workaround information and relaying it to the DDI community in general. While we will keep Taina appraised of this work you might want to follow this issue to stay informed about the progress and comment on the work as it progresses.

‌

Wendy

[cessda-bitbucket-importer]

Original comment by John Shepherdson (GitHub: john-shepherdson).

---

Not required for current version

[cessda-bitbucket-importer]

Original comment by Taina Jääskeläinen.

---

‌

[cessda-bitbucket-importer]

Original comment by Taina Jääskeläinen.

---

For interoperability and linked data, resolvable URIs needed also at concept level, see the attached document.

And related user comment:

---

I still have some questions about the choice of URLs for the terms in the vocabularies in the SKOS version. I know this is not an issue in the XML and XSLS formats, but in the linked data world the choice of the persistent identifier for the terms is as important as that of the vocabulary itself.

For the term Sum, the persistent id for the skos version is now:

https://ddialliance.org/Specification/DDI-CV/AggregationMethod_1.1.html#Sum

Note that this url includes the .html suffix, which makes the RDF version refer to the HTML version and that resolving the url results in a 404 error.

I would have expected the url to be something like

https://ddialliance.org/Specification/DDI-CV/AggregationMethod/1.1/Sum

or even

urn:ddi:int.ddi.cv:AggregationMethod:1.1:Sum

Jacco van Ossenbruggen (ODISSEI community, Netherlands)

‌

[cessda-bitbucket-importer]

Original comment by Taina Jääskeläinen.

---

There are other issues related to URN/URLs to use. All need to be looked at together.

[cessda-bitbucket-importer]

Original comment by Carsten Thiel (GitHub: schildwaechter).

---

There are still a number of open questions of what the DDI Alliance actually can and will offer for resolution. There is work to start up in autumn do define that (Which I am chairing, btw).

[cessda-bitbucket-importer]

Original comment by Taina Jääskeläinen.

---

Related to #256 and #267

[cessda-bitbucket-importer]

Original comment by John Shepherdson (GitHub: john-shepherdson).

---

We will need a detailed specification for URI structuring and versioning, before development work can begin.

The work that the DDI Alliance is doing to create a short-term fix for CVS URIs may feed into this.

DDI 2.6 will allow more granular URIs (for PIDS and vocabulary items) - this needs to be taken into account.

[cessda-bitbucket-importer]

Original comment by Carsten Thiel (GitHub: schildwaechter).

---

I suggest you have a meeting with Darren on versioning, he knows a lot more about this and has very clear suggestions

DDI URNs will always have three parts: [Uu][Rr][Nn] : [Dd][Dd][Ii] : : :

See specification here: https://datatracker.ietf.org/doc/draft-urn-ddi/

It is not clear whether we use the same DDI-URN-agency for all CVs or if each CVS-agency has to have their own DDI-URN-agency.

[cessda-bitbucket-importer]

Original comment by John Shepherdson (GitHub: john-shepherdson).

---

@Joshocan Please get Darren’s input and prepare a specification, so it is clear to IISAS what they need to do here.

[cessda-bitbucket-importer]

Original comment by Joshua Tetteh Ocansey (GitHub: Joshocan).

---

Duplicate of #368.