[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=60476#comment-60476 ]
Nick Crossley commented on OSLCCORE-18:
---------------------------------------
At least in Configuration Management, we do require that some resources are returned inline. The resource type does not adequately define that: Resource is expected to be a reference in most cases, LocalResource is one that cannot be a persistent URI (must be a blank node or hash URI), and AnyResource can be either, but does not imply it must be inline. So I think we still need the extra column, and that its absence is a deficiency of the current ReSpec Javascript. I'd like the Javascript to generate the column IF any of the properties in the shape use a value other than a default of oslc:Reference.
> 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]