ACTION-33: Investigate the use of PURL urls for the SSN ontology

Investigate the use of PURL urls for the SSN ontology

Laurent Lefort
Due on:
August 5, 2010
Created on:
July 15, 2010
Associated Product:
W3C Semantic Sensor Network Ontology
Related emails:
  1. Re: Question about the deployments, systems and devices model (from on 2010-07-22)
  2. Question about the deployments, systems and devices model (from on 2010-07-20)
  3. SSN-XG Meeting Reminder (20 July) (from on 2010-07-19)

Related notes:

Investigate if and how using PURL urls could simplify the transition from the phase where the ontology is developed as part of the XF work to the phase where it is maintained after the end of the XG.

Advantage: it would be easier to move the ontology to a different physical location in the future

Disadvantage: the fact that the ontology is the result of the SSN Incubator Activity will be less apparent

Example of ontology using purl: GoodRelations

Laurent Lefort, 15 Jul 2010, 04:30:00

A permanent URL (303) has been defined for the SSN ontology:
It is redirecting to the documentation page

This purl has been used used for all the versions of the SSN ontology delivered after mid-August 2010 (uploaded on the wiki)


Laurent Lefort, 31 Aug 2010, 11:15:25

Have tried the 302 and 303 solutions. Can have both working at the same time except when it is possible to tweak the Apache config file directly, so currently have the 302 one so that tools like Protege can load everything seamlessly.

Laurent Lefort, 26 Oct 2010, 14:25:02

Complement of information:

- the SSN ontology PURL is and not (and all the PURLs for the other SSN XG starting with the /NET/ssnx/ssn prefix are also using )

- I have not found any explanation of which option is better.

There has been a discussion on the topic of the choice of the cool URI method between Ian Davis (Talis) and David Wood (now also Talis formerly Zeiphera (PURLZ and Callimachus))

David Wood:
Ian Davis

Discussion (reverse chronological order)

- (Jan 6)
- (Dec 6)
- (Nov 9 = before David admitted he was wrong)
- (Nov 7)
- (Nov 3)

Summary: don't tweak URIs (don't use 303), it is better to separate URIs to access RDF content from URI defining a resource.

Laurent Lefort, 18 May 2011, 08:55:16

Display change log.

Laurent Lefort <>, Kerry Taylor <>, Amit Sheth <>, Chairs, Coralie Mercier <>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 33.html,v 1.1 2011/07/25 08:55:36 vivien Exp $