Updating open-services.net namespaces for OSLC Core v3.0

["Jim Amsden" <jamsden@us.ibm.com>]

The OSLC namespaces are currently published
at http://open-services.net/wiki/core/Vocabulary-index/.
These pages need to be updated in order to publish the OSLC Core v3.0 updated
vocabulary and to add the shapes. I have no specific instructions on how
to update these pages. 

Steve, Sam, Lee, do any of you have
any notes on how to publish the vocabularies to open-services.net? I don't
want to break anything!


I propose the following to update
this page http://open-services.net/wiki/core/Vocabulary-index/:

Page updates:

* Contents - links should be to sections
for each OSLC vocabulary that lists the shapes that constrain that vocabulary.
When the new sections are updated with the shapes, the diagrams can be
removed since they have not be updated and are replaced by images in the
specifications. 
* Update the Spec names and versions
for Core 3.0 and CM 3.0, leave the others alone for now.
* Add a row for Configuration Management
* Add a Constraints column that links
to the same sections as the Contents

Table column updates:

* Spec
- link to specification, use
OASIS latest: http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/oslc-core-v3.0-part1-overview.html,
only provide a link to Part 1 of multi-part specifications, users can navigate
from there to other parts.
* Namespace:
http://open-services.net/ns/core#- this is the URL that should support content negotiation - application/html
should link to the published vocabulary document, http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/oslc-core-v3.0-part7-core-vocabulary.html,
one of the parts of the OLSC Core multi-part specification. This is the
whole OSLC Core 3.0 vocabulary, but doesn’t include the shapes. There
are in separate documents.
* OWL
Schema - Should be OWL Schema
not RDF, and would be a link directly to the text/turtle representation
of the http://open-services.net/ns/core#namespace
* HTML
Same as the application/html
content type for the http://open-services.net/ns/core#namespace. OWL Schema and HTML columns are just conveniences for the namespace
URI that don’t require the user to include an Accept header to get the
right content.
* Constraints
- there will be many files
here. For core they will be: http://open-services.net/ns/core/shapes/3.0/*-shape.ttl.
These can’t go in a single table column. Have it be a link to an anchor
in the file for each vocabulary and its shapes. Use the TOC links for this.


Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575