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

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

re: A. Are you suggesting to just remove "you don't want to inline any summary of the target" from that sentence?

re: B. I think we should clarify the sentence. This is related to how ReSpec uses the shapes files to generate the properties. The meaning of the columns in the property table need to be defined somewhere. Nicks text could be included too.

re: C. Since this is informative and a Committee Note, maybe these additional sub-sections aren't needed?

re:D. I can expand on this section.

re:F. I think this meant to say that you have potentially included the title property in two places in the RDF/XML, one inlined, and possibly another that isn't inlined - and they could be different.

re: G. See you D. Isn't this it?




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