[OASIS Issue Tracker] (OSLCCORE-55) oslc:describes on ResourceShape should be optional in ReSpec

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

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

James Amsden commented on OSLCCORE-55:
--------------------------------------

Resolution to this issue depends on the resolution to OSLCCORE-43 OSLC Core 2.0 Appendix A: Common Properties defines things not currently in OSLC3. If that issue is addressed in some way that does not depend on ResourceShape having no oslc:describes property, then this issue, while still a ReSpec defect, would not necessarily need to be fixed.


> oslc:describes on ResourceShape should be optional in ReSpec
> ------------------------------------------------------------
>
>                 Key: OSLCCORE-55
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-55
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: Nick Crossley
>
> The ResourceShapes specifications indicates that oslc:describes is an optional property of ResourceShape (Zero-or-many) and that if it is unspecified, then the shape can apply to any resource.
> This is what we should use to capture the OSLC common properties - a oslc:CommonProperties ResouceShape that doesn't represent anything, therefore not implying there is some root OSLC resource type.
> The Shape Checker only creates a warning on this, and that's probably the right thing to do. 
> However, ReSpec cannot process a ResourceShape if oslc:describes is not specified or refers to an RDF class that is not defined in any vocabulary (e.g.,foaf:Person).



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