[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=68518#comment-68518 ] James Amsden commented on OSLCCORE-154: --------------------------------------- Looks like ResponseInfo was removed and replaced with LDP and/or OSLC 2.0 paging. I see the vocabulary term is still in OSLC Core 3.0, but not the shape. Could be it was suppose to be removed from the vocabulary too. Is it needed anymore? > 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]