[Oslc-communications] OSLC ontologies (OWL)

[Steve K Speicher]

> From: Uri Shani <SHANI at il.ibm.com>
> To: oslc-communications at open-services.net, 
> Date: 04/11/2012 08:28 AM
> Subject: [Oslc-communications] OSLC ontologies (OWL)
> Sent by: oslc-communications-bounces at open-services.net
> 
> The OSLC name-spaces like http://open-services.net/ns/am# or 
http://open-
> services.net/ns/core# do not have a formal ontology such as in the OWL 
> specifications.. 
> Rather, these URLs lead to the specification html page for these 
name-spaces. 
> 
> That is fine for people, yet it seems to me that as a formal name-space, 

> these URLs should actually contain the OWL rdf document. 
> For example and comparison, see the dcterms URL (
http://purl.org/dc/terms/). 
> That will allow one to create new ontologies extending the OSLC ones 
using 
> OWL editing tools such as Protege. 
> 
> How does this idea fits into the OSLC formal specifications plans? 
> 

Uri,

This idea is already supported.  Since you are requesting a representation 
from a browser it requests text/html, so for example with the namespace 
http://open-services.net/ns/core# you are redirected to 
http://open-services.net/bin/view/Main/OslcCoreVocabulary and if you 
request application/rdf+xml (using a tool like curl or REST client or 
poster) you are redirect to http://open-services.net/ns/core/core.rdf

This document describes how we do this: 
http://open-services.net/bin/view/Main/OSLCCoreURINamingGuidance

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645