[OASIS Issue Tracker] (OSLCCORE-56) Need to decide if inverse labels are part of Property shapes

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

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

Martin Pain commented on OSLCCORE-56:
-------------------------------------

If you're referring to section 7.2: http://www.w3.org/Submission/2014/SUBM-shapes-20140211/#inverse-properties then I think these two things can live side-by-side, they're complimentary.

ext:isInverseProperty swaps the subject and object (although it is not backwards-compatible as existing implementations wouldn't know to look for it, so we couldn't do that - using something like oslc:inversePropertyDefinition in place of oslc:propertyDefinition might be better).
On the other hand, oslc:inversePropertyName gives the display name to use when displaying the property in the opposite direction to how the resource shape describes it. So there is a name available for both directions, even though the link is only gong in one direction.
(If we did formally describe a solution along the lines of Arthur's we'd have to decide what inversePropertyname means in that context - inverse of the triple or inverse of the oslc:Property [ I'd vote for the latter] but as we're not defining that now we don't have to decide that now... maybe.)

> Need to decide if inverse labels are part of Property shapes
> ------------------------------------------------------------
>
>                 Key: OSLCCORE-56
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-56
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> OSLC Core 3.0 core-vocab.html has a brief non-normative section on inverse labels that suggest inverse properties (backlinks) should not be used (as described in link guidance), and inverse labels should be used instead. Arthur's Resource Shapes 2.0 W3C submission discussed inverses, but took a different approach. Should we decide on an approach and add the oslc:inversePropertyName to oslc:Property in Resource Shapes?



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