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-154) oslc:ResponseInfo defined as a shape but not mentioned in query spec


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

David Honey commented on OSLCCORE-154:
--------------------------------------

It's a MUST for an OSLC paged response as its properties give the URI for getting the next page. RTC seems to include it even for a non-paged response.

What I dislike is that we don't link to the oslc:ResponseInfo from the query result container. It's just some resource mixed in with all the other RDF content. If we had a predicate such as oslc:responseInfo, we can specify in its shape that is has cardinality Zero-or-one. I think that's clearer.

> oslc:ResponseInfo defined as a shape but not mentioned in query spec
> --------------------------------------------------------------------
>
>                 Key: OSLCCORE-154
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-154
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Core, Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> OSLC Core 3.0 vocabulary defines a class fpr oslc:ResponseInfo, but that shape is not referenced by any core spec or the query spec. The original shape at http://open-services.net/bin/view/Main/OslcCoreSpecification#Response_Information seems to be missing.
> There does not appear to be any predicate to refer to an oslc:ResponseInfo. Examples in https://web.archive.org/web/20151031160403/http://open-services.net/bin/view/Main/OSLCCoreSpecRDFXMLExamples#Specifying_the_shape_of_a_query seem to show that it should use a subject URI of the full query URI including query parameters, but I cannot see this described anywhere. It would be better to have the query container reference any oslc:ResponseInfo using a oslc:responseInfo predicate, and allow that reference to be inline, such as a blank node.



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