[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=37035#comment-37035 ] 

Sean Kennedy commented on OSLCPROMCO-1:
---------------------------------------

@Arthur - thanks for the great responses to both these questions.

One other thing - with concern that this is opening another can of worms ...

While I agree that we don't need both "validates" and "isValidatedBy" in the vocabulary, does it make sense to do anything to give hints to the UI layer?
Say, in the case where "<testcase-137> :validates <requirement-42>" is viewed from a screen that is primarily about requirement-42, that the UI could display the relationship as "Is Validated By: ${title-of-testcase-137}"?

Those bi-directional UI hints, i.e. both "validates" and "is validated by" in this case, would also be translateable ...

I have a vague recollection about there being discussion about something like this, but the recollection doesn't include the right keywords that would help me find it on Google.

> 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.1.1#6155)