oslc-core message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Core Vocabulary and Resource Shapes ready for TC review
- From: "Jim Amsden" <jamsden@us.ibm.com>
- To: oslc-core@lists.oasis-open.org
- Date: Tue, 22 Dec 2015 11:16:36 -0500
OSLC Core 3.0 draft documents are ready
for TC review:
1. Core Vocabulary: https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/core-vocab.html
This update includes the ResourceShapes
for common properties from OSLC Core 2.0 and other OSLC Core 3.0 common
properties. It also provides the complete OSLC Core 3.0 vocabulary.
The approach used to capture common
Dublin Core, RDF, RDFS, FOAF and OSLC properties was to use a resource
shape CommonProperties which has no oslc:describes property. This is supported
by OSLC Resource Shapes 2.0, and is intended to describe properties that
could be applied to any resource. This is a proposed resolution to issue
OSLCCORE-43 that:
1. doesn't define any root OSLC resource
2. doesn't require any of the properties
- they are all optional
3. uses a uniform way of displaying
properties in the specs using ReSpec
4. provides the common properties in
a machine readable Turtle file like any other shape properties.
Unfortunately ReSpec does not yet support
ResourceShapes that do not include oslc:describes, see issue OSLCCORE-55.
As a work around, CommonProperties oslc:describes is set to oslc:Any in
order to get the shapes tables to render properly. That will be removed
when the ReSpec defect is fixed.
2. OSLC Resource Shape 3.0: https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/resource-shape.html
We decided that in order to maintain
compatibility with OSLC v2.0, and recognizing significant use by existing
products, we must continue to support OSLC Resource Shapes, with other
LDP constraint languages such as SHACL as additional options. I had considered
how best to include ResouceShapes into the OSLC Core 3.0 specifications
including:
1. simply referencing the current OSLC
Core 2.0 Common Properties
2. migrating OSLC
Core 2.0 Common Propertiesinto the OSLC Core 3.0 vocabulary: core-vocab.html
3. utilizing the W3C Resource
Shape 2.0 draft specification
with the updated content and descriptions
I compared the W3C Resouce Shape 2.0
draft with OSLC Core 2.0 Common Properties and found them to be completely
compatible. In order to leverage the great work Arthur did in cleaning
up Resource Shapes 2.0, I decided to migrate the W3C draft to OASIS and
include it as part of the OSLC Core 3.0 multi-part specifications. I also
extracted the resource shapes and properties from the two documents into
new ResouceShapes-shape.ttl and resource-shape-vocab.ttl files. These files
are used in the resource-shape.html draft specification to generate the
properties tables using ReSpec.
Core Vocabulary as well as Core Overview
now refer to the new OSLC Resource Shape 3.0 draft.
This completes the TC draft specifications
for OSLC Core 3.0 and OSLC Change Management 3.0 which refers to OSLC Core
3.0 and represents a use of Core for further validation. Once the TC reviews
are done and the final edits are completed, these working drafts can be
submitted for public review.
As always, send editorial comments to
this mailing list, and raise any significant issues in the issues list:
https://issues.oasis-open.org/browse/oslccore.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]