...
Proposed solution discussions, in reverse chronological order
2019.11.30 draft "info" inflection specification
The "info inflection" is a string, "?info", that may be added to an ARK before resolving it in order to request, not the identified object, but the return of human- and machine-readable metadata describing the object and the commitment made to it by its provider.
For the sake of discussion, we assume that resolution of a given ARK may be a multi-stage process starting with the resolver (HTTP server) appearing in the URL form of the ARK when it is submitted for resolution. That first resolver may actually return content directly, making resolution a one-stage process. If not, the first resolver forwards to a second resolver, which may in turn forward to another, and so forth. The last resolver is the HTTP server that returns content without forwarding. The first resolver may in some cases be the last resolver.
The response may take several forms:
- Unsupported: THUMP header xxx "unsupported inflection"
- THUMP header
The result of resolving an ARK without an inflection is indistinguishable from an HTTP response from the last resolver.
causes the followingreturns HTML with embedded JSON-LD
a) embedded GeoJSON, which allows foreign members from JSON-LD
why? because of high integration with widespread tools, like google search and instant map integration is visually powerful
b) embedded HTML meta tags
why? because not everyone is extracting JSON-LD tags
c) metadata elements formatted for human reading per provider preference
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "Dataset",
"@id": "https://n2t.net/ark:/12345/x408001.v2",
"who": "National Cancer Institute; ICPSR - Interuniversity Consortium for Political and Social Research",
"what": "Cancer Surveillance and Epidemiology in the United States and Puerto Rico, 1973–1977",
"when": "1984-05-03",
"where": "https://n2t.net/ark:/12345/x408001.v2",
"how": "(:mtype data) Dataset",
"kids": [
"https://n2t.net/ark:/12345/x408001.v2/file.xsl",
"https://n2t.net/ark:/12345/x408001.v2/file.csv",
"https://n2t.net/ark:/12345/x408001.v2/file.pdf"
],
"parent": "https://n2t.net/ark:/12345/x408001",
"cite-as": "https://n2t.net/ark:/12345/x408001.v2",
"stickiness": [
"_see: https://datascience.codata.org/articles/10.5334/dsj-2017-039/",
"indefinite", "keeping", "intraversioned", "standard", "NR", "OP"
],
"name": "Cancer Surveillance and Epidemiology in the United States and Puerto Rico, 1973–1977",
"author": "National Cancer Institute",
"publisher": "ICPSR - Interuniversity Consortium for Political and Social Research",
"datePublished": "1984-05-03",
"dateModified": "2015-08-06T11:20:58Z",
"version": "v2",
"Description": "This dataset was produced as part of the Surveillance, Epidemiology, and End Results (SEER) Program to monitor the incidence of cancer and cancer survival rates in the United States, thus carrying out the mandates of the National Cancer Act. The SEER Program had several objectives: to estimate the annual cancer incidence in the United States, to examine trends in cancer patient survival, to identify cancer etiologic factors, and to monitor trends in the incidence of cancer in selected geographic areas with respect to demographic and social characteristics..."}
</script>
<!-- why? because not everyone recognizes JSON script metadata -->
<meta name="DC.identifier" content="ark:/12345/x408001.v2" scheme="DCTERMS.URI"/>
<meta name="DC.title" content="Cancer Surveillance and Epidemiology in the United States and Puerto Rico, 1973–1977"/>
<meta name="DC.creator" content="National Cancer Institute"/>
<meta name="DC.publisher" content="ICPSR - Interuniversity Consortium for Political and Social Research"/>
<meta name="DC.date" content="1984-05-03" scheme="DCTERMS.W3CDTF"/>
<meta name="DC.type" content="Dataset"/>
2019.11.26 strawdog JSON
Returns HTML with
a) embedded GeoJSON, which allows foreign members from JSON-LD
why? because of high integration with widespread tools, like google search and instant map integration is visually powerful
b) embedded HTML meta tags
why? because not everyone is extracting JSON-LD tags
c) metadata elements formatted for human reading per provider preference
...