Author: alexdma
Date: Tue Dec 13 17:18:32 2011
New Revision: 1213792

URL: http://svn.apache.org/viewvc?rev=1213792&view=rev
Log:
STANBOL-402 : more content on ontology registry language.

Modified:
    
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.mdtext

Modified: 
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.mdtext
URL: 
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.mdtext?rev=1213792&r1=1213791&r2=1213792&view=diff
==============================================================================
--- 
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.mdtext
 (original)
+++ 
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.mdtext
 Tue Dec 13 17:18:32 2011
@@ -1,6 +1,15 @@
-Title: Ontology Registry Manager
+Title: Ontology Registry Language
 
-The following RDF code (in Turtle syntax) shows how to create an OWL 
individual for a library called <tt>SocialOntologies</tt> which contains the 
ontologies of [SIOC](http://sioc-project.org/ontology) and 
[Provenance](http://trdf.sourceforge.net/provenance/ns.html).
+To create an ontology registry, simply create an ontology and upload it 
somewhere on the Web. 
+Supported formats are RDF/XML, OWL/XML, Turtle, N3, Manchester OWL Syntax and 
OWL Functional Syntax. RDF/JSON and JSON-LD are not supported.
+
+The ontology must contain individuals of type 
<[http://www.ontologydesignpatterns.org/cpont/codo/coddata.owl#OntologyLibrary]>
 (libraries) and/or 
<[http://www.ontologydesignpatterns.org/cpont/codo/codkernel.owl#Ontology]> 
(ontologies referenced by libraries). The URI that identifies an individual of 
type <tt>Ontology</tt> MUST be the (dereferenceable) physical location of the 
ontology document, no matter if it differs from the actual ontology ID (which 
is found out only after the ontology is laoded).
+
+Relations between libraries and ontologies are assertions on the properties 
<[http://www.ontologydesignpatterns.org/schemas/meta.owl#hasOntology]> (with 
subject of type <tt>OntologyLibrary</tt> and object of type <tt>Ontology</tt>) 
and <[http://www.ontologydesignpatterns.org/schemas/meta.owl#isOntologyOf]> 
(withg inverted subject and object types). It does not matter which property 
you choose.
+
+## Examples
+
+Given the prefix mappings:
 
     @prefix meta: <http://www.ontologydesignpatterns.org/schemas/meta.owl#> .
     @prefix owl: <http://www.w3.org/2002/07/owl#> .
@@ -8,18 +17,20 @@ The following RDF code (in Turtle syntax
     @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
     @prefix : <http://www.example.org/ontologies/registries#> .
     @base <http://www.example.org/ontologies/registries> .
+
+The following RDF code (in Turtle syntax) shows how to create an OWL 
individual for a library called <tt>SocialOntologies</tt> which contains the 
ontologies of [SIOC](http://sioc-project.org/ontology) and 
[Provenance](http://trdf.sourceforge.net/provenance/ns.html).
     
     :SocialOntologies rdf:type 
<http://www.ontologydesignpatterns.org/cpont/codo/coddata.owl#OntologyLibrary> ;
               rdfs:label "Social Network Ontologies"^^xsd:string ;
-              owl:versionInfo "0.1"^^xsd:string ;
               meta:hasOntology <http://rdfs.org/sioc/ns> ;
               meta:hasOntology <http://trdf.sourceforge.net/provenance/ns.rdf> 
.
 
-You can also specify Library-Ontology relations the other way around, by 
stating them in the OWL individual that represents the ontology
+You can also specify Library-Ontology relations the other way around, by 
stating them in the OWL individual that represents the ontology.
 
     <http://rdfs.org/sioc/ns> rdf:type 
<http://www.ontologydesignpatterns.org/cpont/codo/codkernel.owl#Ontology> ;
               meta:isOntologyOf :SocialOntologies .
 
 ____
 _[Back to RegistryOntology Manager](../registry.html)_
+
 _[Back to Ontology Manager](../../ontologymanager.html)_
\ No newline at end of file


Reply via email to