Loading...

XML

Word

Printable

Proposal:

Hide

Since its usage seems to be intended solely for the query result, it should be described in the Query spec, and be included in examples. A new predicate oslc:responseInfo should be defined, and the object should a resource that can be oslc:Either.

Show
Since its usage seems to be intended solely for the query result, it should be described in the Query spec, and be included in examples. A new predicate oslc:responseInfo should be defined, and the object should a resource that can be oslc:Either.
Resolution:

Hide

ResponseInfo is already defined in the core 3.0 vocabulary, but the shape was missing because OSLC Core 3 prefers LDP paging over OSLC 2.0 paging (which is a MAY for backward compatibility). Added the shape to core-vocab.html.

Show
ResponseInfo is already defined in the core 3.0 vocabulary, but the shape was missing because OSLC Core 3 prefers LDP paging over OSLC 2.0 paging (which is a MAY for backward compatibility). Added the shape to core-vocab.html.

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.