[OASIS Issue Tracker] (OSLCCORE-139) ResourceShape valueShape and valueType have incorrect cardinality

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

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

Nick Crossley commented on OSLCCORE-139:
----------------------------------------

Do we have any reason to change the existing 2.0 standard here? I am not aware of any discussions that would require us to do so. So until/unless we have such a reason, compatibility strongly suggests the Core 3.0 spec is wrong here.
The 2.0 spec is saying: a property can have a value that is any one of the following types (e.g., integer or resource). If it is a resource, I can specify a single shape that describes the format of that resource.

> ResourceShape valueShape and valueType have incorrect cardinality
> -----------------------------------------------------------------
>
>                 Key: OSLCCORE-139
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-139
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Core
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> In OSLC 2.0, http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA#oslc_ResourceShape_Resource:
>  * oslc:valueType is Zero-or-many but is Zero-or-one in OSLC Core 3.0
>  * oslc:valueShape is Zero-or-one but is Zero-or-many in OSLC Core 3.0
> Which is correct?



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