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-151) OSLC Paging, splitting a resource across pages

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

David Honey commented on OSLCCORE-151:

As discussed in the query group today. The spec isn't contradictory, but perhaps needs better wording.
Say a server returns RDF serialized in NTriple format. A resource has 5 tags, so has 5 statements using the predicate dcterms:subject. A server might return 2 of those 5 statements in one page, and the other 3 in a later page. However, if one of those tags is a very long string, that RDF literal must be included in its entirety.

Clients dsplaying paged data to a user might want to display an ellipsis where not all values of a property are shown due to paging. To detect that, a client should read the next page as well to see if there are additional values for the same property. I suspect that few existing clients would go the trouble of doing this.

> OSLC Paging, splitting a resource across pages
> ----------------------------------------------
>                 Key: OSLCCORE-151
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-151
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Core, Query
>            Reporter: David Honey
>            Assignee: James Amsden
> http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Paging includes this text:
> " A client can also request paging by adding the "key=value" pair oslc.pageSize to the query string component of the resource URI. By adding this, a client requests that the server respond with a specific number of property values. For example, oslc.pageSize=20 indicates to the server that the client would like 20 values per page. OSLC Services MAY ignore oslc.pageSize.
> When Resource Paging is used, the values of a multi-valued property MAY be split across resource pages. Each property value MUST be represented in its entirety and not split across multiple partial resource pages. "
> The last paragraph appears to be self-contradictory. It's unclear whether the spec is saying that all the values of a property MUST appear on a single page (as per the 2nd sentence) or MAY be split across multiple pages (as per the 1st sentence).

This message was sent by Atlassian JIRA

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