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-18) link-guidance.html final editing issues

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

James Amsden commented on OSLCCORE-18:

A: removed the text: you don't want to inline any summary of the target

B: This is referring to the oslc:ResourceShape Resource in OSLC 2.0, and the columns of the tables in the Resource Constraints sections. But oslc:representation is only used in the Comment (creator and inReplyTo) and Discussion (comment) shapes, and does not appear in the generated table in OSLC 3 specs. Looks like there was a decision to not indicate whether a representation is in-lined or a URL. This is still in section 6.2.2 of the Resource Shape 2.0 member submission.

Note Comment property inReplyTo has oslc:valueType oslc:Reference - it should probably be oslc:Resource. These shape .ttl files were created for OSLC 3, so this is likely a typo. 

C: Added the clause subsections, and labeled the examples

D: expanded the section and included much of Martin's text

F: There are two assertions about the title, and they could have different values. Clarified that section.

G: Added some text about using queries using subject or object to navigate the relationship in either direction so the inverse property isn't needed.

> 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

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