[OASIS Issue Tracker] (OSLCCORE-18) link-guidance.html final editing issues

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

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

James Amsden commented on OSLCCORE-18:
--------------------------------------

Regarding the update to section 2.3 Anti-patterns, changing "Link with inline values of targets" to "Use of Blank Nodes", the end result is the same, but the original anti-patterns was addressing a different problem with blank nodes. If the same value were inlined more than once in the same resource, or if the inlined object also included a URI that was accessed separately, then there could be redundant, possibly inconsistent information in the same file.

> link-guidance.html final editing issues
> ---------------------------------------
>
>                 Key: OSLCCORE-18
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-18
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: James Amsden
>            Assignee: James Amsden
>            Priority: Minor
>
> 1. Anchor: a link plus information that annotates or labels that link for use when a relationship must be annotated with property-values.
> Anchors are done through reification using an ref:Statement with subject, predicate and object and rdf:ID for the assertion being annotated, and any additional properties required. 
> Additional guidance should discuss that properties on links possibly indicate missing classes in the vocabulary and associative objects could be used to model the link properties more directly.
> 2. Examples should be in Turtle and, there is no OSLC Core JSON format (Turtle only)
> 3. Anti-pattern in section 3 referes to OSLC query syntax which isn’t supported
> 4. Include guidance on storing the link information in one place and utilizing queries to traverse the link in both directions. i.e., no inverse properties or bi-directional links.



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