removed extending DCAT section
authorfmaali
Sat, 09 Mar 2013 16:48:51 +0000
changeset 388 5fa9a44f767c
parent 387 901a10d6b01a
child 389 8036a60a8489
removed extending DCAT section
dcat/index.html
--- a/dcat/index.html	Sat Mar 09 16:43:54 2013 +0000
+++ b/dcat/index.html	Sat Mar 09 16:48:51 2013 +0000
@@ -891,16 +891,5 @@
 
 </section>
 
-<section>
-<h2 id="Extending_the_vocabulary">Extending the DCAT vocabulary</h2>
-<ul>
-  <li> As with all RDF models, the DCAT model can be extended simply by using additional RDF properties anywhere. Data catalog publishers may choose from properties in existing vocabularies or create their own custom vocabulary.</li>
-  <li> Additional classes, from existing or new vocabularies, may also be used.</li>
-  <li> Extensions used in a particular catalog should be documented to ensure that consumers of the data are aware of the additional available properties.</li>
-  <li> Creating new subclasses and subproperties of terms used in dcat, such as new types of distributions, is generally discouraged because it can break SPARQL queries that data consumers use to query the data.</li>
-  <li> As always with RDF, if you need to introduce new classes or properties, <em>do not introduce new terms in existing namespaces "owned" by someone else</em>, but set up your own namespace and define new terms in that namespace.</li>
-</ul>
-</section>
-
 
 </body></html>