oslc-core message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [oslc-core] Fwd: [lyo-dev] [oslc-core] Checking compliance of a resource with multiple resource shapes
- From: "Jim Amsden" <jamsden@us.ibm.com>
- To: Andrii Berezovskyi <andriib@kth.se>
- Date: Wed, 26 Jul 2017 15:46:45 -0400
Andrew,
This is a common misinterpretation of
what ResourceShapes mean. A ResourceShape does not define the structure
of an OWL Class, rather it constrains property assertions involving that
class in a context.
The reason a resource can have more
than one instance shape is because the resource could be used in different
contexts, each requiring different constraints. If there is more than one
instance shape in the same context, and they are conflicting, the this
would be considered a validation (but not structural) error or warning,
depending on the context and how the application is using the resources.
OSLC domain vocabularies are intentionally
under-specified: there are no domain and range or other assertions about
the properties. The intention was to keep the vocabularies minimal, simple,
flexible, and easily constrained for different purposes using ResourceShapes.
There are however common ResourceShape
usage patterns that are in fact intended to constrain the "shape"
of an OWL class so that it adheres to a specific structure for persistence,
marshalling to static structured classes in programming languages, building
queries, etc.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
From:
Andrii Berezovskyi
<andriib@kth.se>
To:
"OASIS OSLC Core
TC Discussion List (oslc-core@lists.oasis-open.org)" <oslc-core@lists.oasis-open.org>
Date:
07/26/2017 11:22 AM
Subject:
[oslc-core]
Fwd: [lyo-dev] [oslc-core] Checking compliance of a resource with multiple
resource shapes
Sent by:
<oslc-core@lists.oasis-open.org>
Forwarding it here as somebody might be able to provide
better feedback.
–Andrew.
(sent from my phone)
---------- Forwarded message ----------
From: "Leonid Mokrushin" <leonid.mokrushin@ericsson.com>
Date: Wed, Jul 26, 2017 at 5:02 PM +0200
Subject: [lyo-dev] [oslc-core] Checking compliance of a resource with multiple
resource shapes
To: "Lyo project developer discussions" <lyo-dev@eclipse.org>
Hello,
I just had a discussion with Andrew regarding how to correctly
interpret a following situation:
* An OSLC resource is allowed to have multiple oslc:instanceShape
properties (see https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/resource-shape.html#instanceShape).
* Imagine there are two resource shapes associated with
a resource (using oslc:instanceShape) that describe the same property (let's
say dcterms:title).
1) If these two descriptions are identical, I don't see
any problem.
2) But, what if these two descriptions contradict each
other? Let's say one declares that cardinality of dcterms:title should
be oslc:Zero-or-one and another - oslc:One-or-many.
Shall an implementation consider 1) to be an OK and 2)
to be an error, or both to be an error, or some other interpretation should
be applied?
/Leo[attachment "ATT00001.txt" deleted by Jim
Amsden/Raleigh/IBM]
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]