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

Martin Pain  commented on OSLCCORE-18:
--------------------------------------

A: Yes, to just remove that bit.

B: Quick suggestion as to clarification: "For example, here is a property terms:subscribesTo that you might find inside a customer resource, it links to a resource that is "subscribedTo" by the customer: (example here) ¶In RDF terminology, a link is called a URI Reference.¶In OSLC specifications' resource tables, a link is expressed as a property with OSLC value-type of "Resource" and OSLC representation of "Reference"."

C: I think it's useful to have the headers break the text up, and if we have headers they might asw well be numbered.

F: If we change the examples to Turtle, I believe that there will not be two locations.

G: I think the thing from point 4 that I felt was missing was "utilizing queries to traverse the link in both directions". The text just says "using a simple query", but it's not neceserily simple to know where or how to query, especially if the other resource is on another server. Especially as at v3 we don't have a single query format to rely on. Perhaps we need a "querying guidance" doc or section somewhere (which we can update once LDP querying gets sorted), which we can link to from here.

> 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)