John Kunze's comments on the paper

2 views
Skip to first unread message

Joe Hourcle

unread,
Feb 1, 2015, 5:58:18 PM2/1/15
to Tim Clark, <idmeta@force11.org>


I don't know how familiar people are with reading unified diffs, but here are the edits that I see:


In the bibliography:

He repointed his papers that we cited to the official locations for the papers, not the version that the CDL provides, and he tweaked the author lists slightly (I assume so they're consistent with other times they've been cited).

He added a citation for EZID and URNs


In the main file:

Corrected that 'DOI' is 'Digital Object Identifiers' not 'Document ...' (happens in a few places)

Formatted the DOI resolver as 'http://dx.doi.org/<doi>' (which I'm not sure I agree with until I see how it formats ... might be better to do it in TT, with 'doi' in italics to show it's a variable without confusing people about <>)

In the introduction of DataCite and CrossRef, calls them out as "the two DOI Registration Agencies of special relevance to data citation."

Provided a bit more specifics on ARKs, and better explains the relationship with n2t:

Archival Resource Keys (ARKs) are unique identifiers designed to support long-term persistence of information objects. An ARK is essentially a URL (Uniform Resource Locator) with some additional rules. For example, hostnames are excluded when comparing ARKs in order to prevent current hosting arrangements from affecting identity. The maintenance agency is the California Digital Library, which offers a hosted service for ARKs and DOIs (\cite {ARK, ARK2, ARK-IETF, EZID}).

ARKs provide access to three things - an information object; related metadata; and the provider's persistence commitment. ARKs propose inflections (changing the end of an identifier) as a way to retrieve machine-readable metadata without requiring (or prohibiting) content negotiation for linked data applications. Unlike, for example, DOIs, there are no fees to assign ARKs, which can be hosted on an organization's own web server if desired. They are globally resolvable via the identifier-scheme-agnostic N2T (Name-To-Thing, http://n2t.net) resolver. The ARK registry is replicated at the California Digital Library, the Bibliothèque Nationale de France, and the U.S. National Library of Medicine (\cite {ARK, ARK3, ARK10}).


Under NBN, replaced the statement of them being unique at the national level with:

There is a URN namespace for NBNs that includes the country code; expressed as a URN, NBNs become globally unique (\cite {NBN-IETF, URN}).


Added a sentence in the appendix:

ARK-style inflections propose an alternate way to retrieve machine-readable metadata without requiring content negotiation.

...

And to explain 'ARK-style inflections', you add some suffixes to the URI to access some other information:

URI : for the object being identified
URI? : for the metadata for the object
URI?? : for the maintenance commitment (similar to our 'persistence guarantee')

... but I think that's going to confuse things more, as part of the paper is that the ID identifies the data, but resolves to the landing page. This might confuse things:

does 'URI' resolve to the landing page, and 'URI?' give you the administrative metadata, rather than the scientific & citation metadata?
do we use it in place of extensions for web linking, so that you'd do: 'URI?xml' instead of 'URI.xml'?

...


I can make the other changes (especially all of his DOI s/Document/Digital/ fixes), citation edits, edit on DataCite/CrossRef, corrections for ARK and NRN, and find a way to set off the 'dx.doi.org' better (although maybe not his way).

I've attached the files he gave me, plus the unified diff against the version I had sent him.

-Joe


DCIG_IDMETA_jak.bib
main_jak.tex
achieving-human-machine-Kunze-comments.diff
Reply all
Reply to author
Forward
0 new messages