[OASIS Issue Tracker] (OSLCPROMCO-1) Simplify RDF vocabulary by eliminating redundant inverse properties

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

    [ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37309#comment-37309 ] 

Arthur Ryman edited comment on OSLCPROMCO-1 at 5/7/14 12:29 AM:
----------------------------------------------------------------

The relations between “Change” and “ManagedItem are not redundant because they define two different roles that a ManagedItem can have with a Change resource. However, the names are not good grammatically because they do not correctly describe the relation between the Change and ManagedItem. The terms describe the relations between the two ManagedItems.

A better choice of names is "before" and "after" since one ManagedItem is the before resource and the other ManagedItem is the after resource relative to the Change resource.


was (Author: ryman):
The relations between “Change” and “ManagedItem or OK because they define two different roles that a ManagedItem can have with a Change resource. However, the names are not good grammatically because they do not correctly describe the relation between the Change and ManagedItem. The terms describe the relations between the two ManagedItems.

A better choice of names is "before" and "after" since one ManagedItem is the before resource and the other ManagedItem is the after resource relative to the Change resource.

> Simplify RDF vocabulary by eliminating redundant inverse properties
> -------------------------------------------------------------------
>
>                 Key: OSLCPROMCO-1
>                 URL: https://tools.oasis-open.org/issues/browse/OSLCPROMCO-1
>             Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
>          Issue Type: Improvement
>            Reporter: Arthur Ryman
>
> The current design has many pairs of mutual inverse properties. This makes writing SPARQL queries awkward since you have to include both. If you only have one way to express a fact then the queries become easier to write.



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