OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

James Amsden commented on OSLCCORE-56:

The current proposals for backlink support are:

1. IBM Jazz Reporting Service uses ResourceShape Property lqe:reversePropertyDefinition to define the inverse property. The value is the URI of the backlink Property definition (not a label)

2.  OSLC Core 3.0 core-vocab.html references non-normative Inverse Link Labels, but this is not adequately described in the specification. core-vocab.ttl includes oslc:inverseLabel rdf:Property: "Provides a human-readable label for the inverse of the subject property." ex: oslc_qm:validatesRequirement oslc:inverseLabel "validatedBy". Looks like ReSpec handles these properties.

3. OSLC Core 3.0 Resource Shape suggests Extensions Vocabulary (which may be removed) that describe two other approaches
    - Use a Property definition for the backlink property, but mark it with ext:isInverseProperty true. These properties describe incoming links for the ResourceShape that owns the Property.
    - Extend Property with ext:inversePropertyName String - which is sort of a combination of 1 and 2. This approach wouldn’t support as much information on the inverse property as a URI to a Property

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]