[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=63004#comment-63004 ]
Nick Crossley commented on OSLCCORE-18:
---------------------------------------
The original text had at least two problems. First, if you translate the 'bad' example and the 'good' example to Turtle, you see they are exactly the same - the only difference was in the details of the XML serialization. Second, the recommendation was ruled as poor during TC discussions, since it discouraged the HTML representation of resource A from containing statements about resource B, which contradicts the "Anyone can say anything about anything" [http://www.w3.org/TR/2002/WD-rdf-concepts-20020829/#xtocid48014] principle of RDF. Note that there was nothing in the original text about blank nodes - the new anti-pattern is not a rewrite of the original, it is completely unrelated. And yes, that AAA principle indeed implies (as noted in the above reference) that "RDF cannot prevent anyone from making nonsensical or inconsistent assertions, and applications that build upon RDF must find ways to deal with conflicting sources of information".
> 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]