ACTION-30: Define the final place where the XG ontology will be delivered

Currently the namespace used for the SSN XG ontology is:
http://www.w3.org/2009/SSN-XG/Ontologies

This does not correspond to the conventions generally used by publishers of ontologies (and for other file formats using namespaces published by W3C).

Here are some inputs for the discussion on the "final" location and namespace used for the SSN XG ontology:

- avoid paths and file names with uppper case letters (like SSN-XG and Ontologies)
- use the the physical location of the owl file containing the ontology as the base for it and for the namespace it uses
- the SSN workspace root is http://www.w3.org/2005/Incubator/ssn/

I have yet to ask Coralie if it is possible to set up some sub-folders one level under this root e.g. http://www.w3.org/2005/Incubator/ssn/ontology , http://www.w3.org/2005/Incubator/ssn/data http://www.w3.org/2005/Incubator/ssn/markup
http://www.w3.org/2005/Incubator/ssn/external
to place the XG deliverables and examples.

(Complement of discussion) To follow ontology engineering best practices, the XG needs to post the file in a physical location which corresponds to the namespace used in the ontology e.g. in a place like http://www.w3.org/2005/Incubator/ssn/ontology/ssn-ont.owl - we would also like to put some other OWL bits nearby (e.g. the examples and the external ontologies used by the examples)

The question is: can we put the XG ontology owl file (and the rest) in such a place and remotely maintain successive versions of it - if so, can someone from the XG remotely upload successive versions with a SSH-ed CVS access or is this a privilege which is only granted to Team members?

If not, can we plan to follow for the OWL file the process defined for the XG report http://www.w3.org/2005/Incubator/XGR/about.html - which is to let the W3C webmaster post it in the "right place" (the question is then: what is the "right place"? are there specific constraints to be aware of?).

The SSN XG cannot do what the URW3 XG has done which is to post the ontology as a attached file to a wiki page like http://www.w3.org/2005/Incubator/urw3/wiki/UncertaintyOntology/Uncertainty.owl because W3C is no longer using the same wiki product.

It would be good to have a tighter control on the location of the file and of the related documentation (to be able to set up hyperlinks between the OWL file content and the associated HTML page documenting it).

This is a setup which is likely to be asked by other XG developing ontologies such as the Decision XG and/or by other working groups in W3C.

Start of the discussion with W3C Team (Coralie) leading to the some important questions.

The question related to this action is what would be the best approach to reach the aimed result (to have the ontology posted in the right place). This depends on how frequently the ontology is supposed to change: if not too frequently, then it should be possible to ask someone form W3C to upload it.

At this stage of the XG, we cannot plan for more than two or three iterations on the main ontology file. But a corollary issue is how much iterations should be planned for the upload of associated examples and documentation pages. If we use tools to automatically generate the documentation then a remote access would be more convenient.

A second issue will be managed independently of this action: what will happen to the ontology after the XG is closed: see ISSUE-9 "Ontology status after the closure of the XG" http://www.w3.org/2005/Incubator/ssn/track/issues/9

Start of the discussion with W3C Team (Coralie) leading to the some important questions.

The question related to this action is what would be the best approach to reach the aimed result (to have the ontology posted in the right place). This depends on how frequently the ontology is supposed to change: if not too frequently, then it should be possible to ask someone form W3C to upload it.

At this stage of the XG, we cannot plan for more than two or three iterations on the main ontology file. But a corollary issue is how much iterations should be planned for the upload of associated examples and documentation pages. If we use tools to automatically generate the documentation then a remote access would be more convenient.

A second issue will be managed independently of this action: what will happen to the ontology after the XG is closed: see ISSUE-9 "Ontology status after the closure of the XG" http://www.w3.org/2005/Incubator/ssn/track/issues/9

Directories to put under the root of the SSN XG workspace: http://www.w3c.org/2005/Incubator/ssn

- ontology: the Semantic Sensor Network ontology: ssn.owl
(and all the generic examples and the links)
- qu: all the quantities and unit ontologies: sysml-qudv.org and qudv-ssn.org
- ext: all the other imported ontologies: cf.owl and neesmeta_1.2.owl
- examples with sub-directories e.g. agrimet, hydro, annot

- util: documentation utilities
- doc: place for generated doc

See also Action-33 on the use of PURLs

I have bundled all the ontologies together in a zip file with the following structure (all folders contains .owl files and .html files for the corresponding documentation).

ssnx (to appear as http://www.w3.org/2005/Incubator/ssn/ssnx
ssnx/ssn The SSN Ontology (ssn.owl) plus the documentation (ssn.html)
ssnx/cf The climate and forecast ontologies - Agriculture Meteorology example
ssnx/energy The energy example
ssnx/meteo The agriculture meterology example
ssnx/product The Smart Product example
ssnx/qu The Unit and Quantity ontologies - Agriculture Meteorology example
ssnx/uni The University deployment example

ssnx/weather-station The Linked Sensor data examples





In all sub-folders, I have included a .htaccess file implementing the “Cool URIs” recipe3a http://www.w3.org/TR/swbp-vocab-pub/#recipe3a

Switch the PURL to the final place done for SSN ontology
(http://purl.oclc.org/NET/ssnx/ssn now points to http://www.w3.org/2005/Incubator/ssn/ssnx/ssn)

Also (as suggested by Alexandre) the PURL setup now uses a 303 (redirect) instead of a 302

Succesful tst with Vapour:

http://validator.linkeddata.org/vapour?vocabUri=http%3A%2F%2Fpurl.oclc.org%2FNET%2Fssnx%2Fssn&classUri=http%3A%2F%2Fpurl.oclc.org%2FNET%2Fssnx%2Fssn%23Sensor&propertyUri=http%3A%2F%2Fpurl.oclc.org%2FNET%2Fssnx%2Fssn%23observes&instanceUri=http%3A%2F%2F&validateRDF=1&htmlVersions=1&defaultResponse=dontmind&userAgent=vapour.sourceforge.net