Changes for document General approach

Last modified by Arjan Loeffen on 2015/06/01 09:28
From version 15.1
edited by Arjan Loeffen
on 2015/05/30 13:37
To version 16.1
edited by Arjan Loeffen
on 2015/05/30 13:56
Change comment: There is no comment for this version

Content changes

... ... @@ -19,3 +19,17 @@
19 19 1. Note that within a context ontology a **Building **may be further specified in line with the domain of interest, such as “design” or “construction” by adding all kinds of properties. The context ontology may introduce part-of relations or enforce that a **Building **must have a **Height**. The CB-NL does not support identity of these information structures, but only of the constructs that make up these structures: the concepts (OWL classes) and the relations (OWL object properties). Again, as a metaphor, "the CB-NL doesn't match sentences, it matches words".
20 20
21 21 The way the CB-NL is constructed is founded on the Open world assumption (OWA). CB-NL only records what //must// be stated about a construct, and avoids constraining the statements. As a sideline: the CB-NL does not use domains or ranges (in the OWL sense), as these limit the applicability of a relation (realized as an OWL ObjectProperty).
22 +
23 +== Software access ==
24 +
25 +Taking the nature of the CB-NL as a mix of core concepts and context mappings into account, the question remains on how to access the CB-NL.
26 +
27 +It should be understood that the CB-NL is a formal OWL specification, not a software system or a server. So, first and foremost, it may be downloaded as a file. This typically takes the form of an OWL RDF file (http:~/~/ This ontology then in integrated into more elaborate RDF/OWL contexts, local to any application.
28 +
29 +As the specification evolves (additional contexts added, concepts changed, added, removed) new releases are created. Such releases are notified.
30 +
31 +In general, in a linked data world, it is good practice to keep the information where it is maintained; there should be one point of reference for any knowledge base. Technically this means that the CB-NL should be served from a single triple store. This triple store is available as http:~/~/ and may be accessed using SPARQL, passing queries in a REST fashion. The SPARQL queries may access graphs that conform to a specific release.
32 +
33 +Currently not all software engineers are familiar with OWL or RDF. The need for an XML and JSON interface has been formulated. Therefore, any release is also available using a REST interface which serves XML or JSON on request (http:~/~/ This API provides access to the OWL specification, but the information is modelled in accordance with an information model expressed in UML.
34 +
35 +Again, as the CB-NL is not a service or software system, the availability of these services (OWL, XML, or JSON) is not fully guaranteed.

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 5.3 - Documentation