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

Nick Crossley commented on OSLCCORE-18:

I think inlined resources and inlined values of target attributes are orthogonal issues. Yes, we agreed inlining values of attributes of the target of a link is an anti-pattern. However, there are good reasons why we sometimes want to to require inlining an entire resource. One reason is efficiency; if a resource (such as a configuration) has a potentially large number of small dependent resources (the contributions) which are separate only in the RDF subject sense, but really part of one data structure, you want to have that structure returned in one HTTP resource. Another reason is to remove the need for server persistence. Suppose you have a resource that describes the multiple possible matches for a concept resource in a global configuration. If you do not return this inline with the resource itself, the server would have to persist the possible matches for some indeterminate length of time - and might have to do so for multiple GET requests for the same concept resource, since the version matches may change quickly over time. Having the matches returned inline in the same HTTP resource (same REST request) avoids the issue.

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