[OASIS Issue Tracker] (OSLCCORE-43) OSLC Core 2.0 Appendix A: Common Properties defines things not currently in OSLC3

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61640#comment-61640 ] 

James Amsden commented on OSLCCORE-43:
--------------------------------------

Shapes are associated with a resource by:

- Resource oslc:instanceShape ResourceShape - directly associates a constraining shape with a resource.
- Service oslc:resourceShape ResourceShape - associates a constraining shape with the request or response entity of a service (such as creation or query)
- Property oslc:valueShape ResourceShape - associates a constraining shape with the resource that is the object value of a property of a some resource.

Shapes associated with a resource apply to the resource (and therefore constrain the resource) based on the ResouceShape oslc:describes property. Shapes apply to an associated resource iff:

- The associated shape has no describes property in which case it applies to all associated resources
- The associated shape has a describes property that is the same as the rdf:type of the resource

OSLC common properties (Dublin Core, dcterms, OSLC specific) may apply to any resource. Which ones specifically apply are specified in the OSLC domain specifications.

In order to use a ResouceShape "CommonProperties" to capture common OSLC properties, we need to know:

- How is a resource associated with the CommonProperties resource shape?
- How do we know if a the CommonProperties shape applies to any given associated resource?
- What does the application of the CommonProperties to an associated resource mean?

If these questions can’t be answered in a manner that is consistent with shape semantics, then CommonProperties should not be a ResourceShape.

1. Shapes are associated with resources through instanceShape, resourceShape or valueShape. If any of these common properties should be included, then CommonProperties would need to be included in the valueShape for the resource. If it isn’t associated with any resource, CommonProperties wouldn’t be applicable to anything. Domains could define their own shapes and include whatever part of common properties they needed and associate those shapes with resources as appropriate.

2. How to know if the CommonProperties shape applies to an associated resource is easy - it applies to all associated resources since it has no oslc:describes property.

3. What it means is more difficult. In general it would mean that the shape applicable to an associated resource constraints the resource by the CommonProperties shape. Since all the properties are optional (have lower cardinality 0), all resources that don’t include any of the properties would be compatible with the constraint. Domain specifications could change the cardinality to require any of the properties if needed. If any of the properties are in the applicable resource, then the property values would have to adhere to the constraints.

I think this addresses Nick's three issues raised in the previous comment. But I may have misunderstood, or misrepresented those issues. So we can wait for Nick's alternative proposal for handling OSLC Core common properties.


> OSLC Core 2.0 Appendix A: Common Properties defines things not currently in OSLC3
> ---------------------------------------------------------------------------------
>
>                 Key: OSLCCORE-43
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-43
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> OSLC Core 2.0 Appendix A: Common Properties (http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA) defines a number of common Resource Shape properties that are not currently part of the OSLC Core 3.0 vocabulary or shapes. These properties include Dublin Core, RDF, RDFS, OSLC, and FOAF.
> Other shapes and properties for Resource Shapes, Comment, Error, etc. are covered in OSLC Core 3.0. 
> Should these be included in the oslc-core/shapes folder and the core-vocab.html document.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)