https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2013-02-19T02:27:50ZDataONE TasksInfrastructure - Task #3596: Fix Merritt Repository resource map typing of triple objectshttps://redmine.dataone.org/issues/3596?journal_id=153132013-02-19T02:27:50ZMatthew Jonesjones@nceas.ucsb.edu
<ul></ul><p>From KNB: <a href="https://knb.ecoinformatics.org/knb/d1/mn/v1/object/resourceMap_6000141086_2.3.2:">https://knb.ecoinformatics.org/knb/d1/mn/v1/object/resourceMap_6000141086_2.3.2:</a><br>
<br>
<br>
<br>
From Merritt: <a href="https://merritt.cdlib.org:8084/knb/d1/mn/v1/object/ark:/13030/m50000sp/1/mrt-dataone-map.rdf">https://merritt.cdlib.org:8084/knb/d1/mn/v1/object/ark:/13030/m50000sp/1/mrt-dataone-map.rdf</a><br>
<br>
<a href="ore:describes">ore:describes</a><a href="http://store.cdlib.org:35121/content/1001/ark%3A%2F13030%2Fm50000sp/1/">http://store.cdlib.org:35121/content/1001/ark%3A%2F13030%2Fm50000sp/1/</a><a href="/ore:describes">/ore:describes</a><br>
<br>
Looking at these examples, the Merritt <a href="ore:describes">ore:describes</a> is describing the string literal, rather than the resource that the string literal points to. Its a critical distinction. The two triples are different as night and day in terms of what they say semantically. The Merritt example should really be:<br>
<br>
<br>
<br>
assuming that the url literal points at the aggregation that this ORE describes. ORE is explicit about the semantics of ore:describes, which is defined quite completely here:</p>
<pre>http://www.openarchives.org/ore/1.0/datamodel.html#ReM-to-aggr
</pre>