--- a/ldp-ucr.html Tue Sep 24 11:49:13 2013 +0100
+++ b/ldp-ucr.html Tue Sep 24 12:05:19 2013 +0100
@@ -112,6 +112,10 @@
title: "Best Practices for HTTP-CoAP Mapping Implementation",
href: "http://tools.ietf.org/html/draft-castellani-core-http-mapping-07",
publisher: "IETF"
+ },
+ "CHANGESET": {
+ title: "Changeset",
+ href: "http://vocab.org/changeset/schema.html"
}
}
};
@@ -1086,14 +1090,13 @@
<section id="s4.2">
<h3>Alternative scenario: selective update of a resource</h3>
<p>
- This relates to user story <a>Data Catalogs</a>, based on the <a href="http://vocab.deri.ie/dcat"
- title="http://vocab.deri.ie/dcat"
- rel="nofollow">Data Catalog Vocabulary</a>. A catalogue is
- described by the following RDF model.
+ This relates to user story <a>Data Catalogs</a>. A catalogue is
+ described by the following RDF model, based on the Data Catalog Vocabulary [[vocab-dcat]] which provides a standard format for representing the metadata held by organizations.
</p>
<pre class='example'>
-@prefix dcat: <http://www.w3.org/ns/dcat#> .
+@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
+@prefix : <> .
:catalog a dcat:Catalog ;
dcat:dataset :dataset/001;
@@ -1102,10 +1105,7 @@
<p>
A catalog may contain multiple datasets, so when linking to new
datasets it would be simpler and preferable to selectively add
- just the new dataset links. For example, a <a
- href="http://docs.api.talis.com/getting-started/changesets"
- title="http://docs.api.talis.com/getting-started/changesets"
- rel="nofollow">Talis changeset</a> might be used to add a new <tt>dc:title</tt> to the
+ just the new dataset links. For this example, a Changeset [[CHANGESET]] might be used to add a new <tt>dc:title</tt> to the
dataset. The following update would be directed to the catalogue
to add an additional dataset.
</p>