[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=59644#comment-59644 ]
Nick Crossley commented on OSLCCORE-18:
---------------------------------------
With regard to including triples about the target of a link - this has security issues as well as coherence issues, and in general should not be recommended. For example, the name or label of the target of a link SHOULD NOT be included in the RDF representation of the source of the link, because the user reading that source resource might not have access to the target resource, and the name itself might contain secure information. In extreme cases, the very existence of a link might be considered as information that should not be revealed unless you have access to both ends, but in most cases this degree of hiding is not necessary.
> 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]