[ https://issues.oasis-open.org/browse/OSLCPROMCO-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43143#comment-43143 ]
Kazuhiro Funakoshi commented on OSLCPROMCO-6:
---------------------------------------------
I have a question about oslc:valueShape constraint.
In our current version of spec, ScopeItem, Artifact, WorkItem have isPartOf relations.
However, they do not refer each other acrossing their types.
(e.g. isPartOf of ScopeItems only refer ScopeItem instead of other ManagedItem )
Therefore we should not state like:
oslc:valueShape oslc_promcode:ManagedItem
In this case, should I (1) write a weak condition, which allows to defined WorkItem to Artifact isPartOf relation, like:
oslc:valueShape oslc_promcode:ManagedItem
or, (2) split each of isPartOf into resource dependent relations for each resource type:
oslc:propertyDefinition oslc_promcode:WorkItemIsPartOf ;
oslc:name "WorkItemIsPartOf" ;
oslc:valueShape oslc_promcode:WorkItem
Of cause, solution (2) requires domain model modification.
> Create an OSLC Shape Document for PROMCODE Resources
> ----------------------------------------------------
>
> Key: OSLCPROMCO-6
> URL: https://issues.oasis-open.org/browse/OSLCPROMCO-6
> Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
> Issue Type: Task
> Reporter: Arthur Ryman
> Assignee: Kazuhiro Funakoshi
>
> The resources defined by PROMCODE should be documented by OSLC Resource Shapes.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
