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-35) v2 Resource Shape vocab: oslc:Inline incorreclty mentions blank nodes

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

Martin Pain commented on OSLCCORE-35:

I'm haven't got clear in my head the usefulness of requiring something to be a blank node, but I think we should discuss that elsewhere as it is not what this ticket is about.

Arthur, so I take it that your previous comment is saying that you agree that oslc:Inline (as an oslc:representation value) should not mention blank nodes, as indeed it does not in the member submission.
And that LocalResource should go back to mentioning blank nodes. I'm not sure how the original v2 description differed from the member submission, but we should take the member submission version if they differ.

Discussion on the value and meaning of Resource/LocalResource/AnyResource (except as it relates to blank nodes) should probably stay on the mailing list or go in another ticket, to keep this ticket focused on the issue of oslc:Inline requiring/not requiring blank nodes (I was about to go off on a tangent on something else).

> v2 Resource Shape vocab: oslc:Inline incorreclty mentions blank nodes
> ---------------------------------------------------------------------
>                 Key: OSLCCORE-35
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-35
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Martin Pain
>            Assignee: James Amsden
> In the v2 vocabulary (we don't version the vocabulary, so we're not removing anything), the oslc:Inline resource (used as a value for an oslc:representation property) says:
> "An inline (RDF blank node) representation."
> I believe this is wrong, as oslc:Inline is used with oslc:Resource, which says "Resource: value is a resource at a specified URI (i.e. a URI Reference)." A value cannot be both a URI Reference and a blank node.
> The member submission of Resource Shapes to the W3C describes oslc:Inline differently, and I believe that this description correctly matches the intention: http://www.w3.org/Submission/2014/SUBM-shapes-20140211/#representation "oslc:Inline: The representation of the object resource MUST be present in the representation of the described resource."
> I suggest we change the description of oslc:Inline in the vocab to match the one from the member submission.
> This issue would probably be more correctly addressed by the v2 "maintenance mode" working group at open-services.net, but as there has been no activity there for a long time, and as we are modifying the vocab for v3 as part of this TC's work, I'm raising it here.
> (The description of oslc:Resource [the alternative to oslc:Inline] in the v2 vocab file also makes no sense: "A URI Reference representation to a resource", but I'm also not sure about the one in the member submission either: "The representaton of the object resource MUST NOT be present in the representation of the described resource." - I interpreted it more as "the representation of the object resource MUST be available by performing a GET on the object URI, irrespective of whether it is also inlined in the subject's representation". The member submission's interpretation might be more appropriate when describing the allowed body of a POST, whereas mine might make more sense when describing what gets returned from a GET.)

This message was sent by Atlassian JIRA

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