[Esip-preserve] Fwd: ok, let's start with GCIS identifiers

Curt Tilmes Curt.Tilmes at nasa.gov
Tue Mar 27 18:58:37 EDT 2012

Talked with Chris Lynnes a bit about URI identifiers for the
entities needed for the ToolMatch semantic service the ESIP
semantic web cluster is working on.

I want to tie it in with the GCIS identifiers we've been
talking about, and proposed we come up with a common URI
scheme which we can root under globalchange.gov.

More discussion about these URIs will continue 'over there'..


-------- Original Message --------
Subject: ok, let's start with GCIS identifiers
Date: Tue, 27 Mar 2012 17:11:41 -0500
From: Lynnes, Christopher S. (GSFC-6102) <christopher.s.lynnes at nasa.gov>
To: Tilmes, Curt (GSFC-6190) <curt.tilmes at nasa.gov>
CC: esip-semanticweb at rtpnet.org <esip-semanticweb at rtpnet.org>

Consensus was that we would like to shoot for URIs with RDF content.  No 
objections to going with GCIS naming, so...let's go with it.

I would suggest that we start off with minimal properties, but one (or 
more) property we should have is a pointer to somewhere where more 
information can be gotten.   For this, I suggest gcmdDif, doi and 
datasetUrl (for dataset landing pages).

Eventually, content negotiation to fetch in RDF/XML vs. HTML would be nice.

Next question is whether service access points (WMS, WCS, OPeNDAP, 
THREDDS) should also be a property within the GCIS-hosted content. What 
do you think?

If you think no, we can always host the access point triples somewhere 
else.  We need it to try inferring which tools work with a given dataset.

As for the identifier naming scheme, my suggestion is to allow for three:

The dif_entry_id can account for nearly all NASA datasets, and a lot 
more besides.  The doi can account for DOE and possibly others, and the 
uuid can be minted by anyone that does not fall into those categories.
Dr. Christopher Lynnes     NASA/GSFC, Code 610.2    phone: 301-614-5185

More information about the Esip-preserve mailing list