OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Nick Crossley commented on OSLCCORE-55:

I agree it is incorrect for OSLC to attempt to define a shape for foaf:Person - or any resource class OSLC does not own.

> oslc:describes on ResourceShape should be optional
> --------------------------------------------------
>                 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: James Amsden
> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]