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: Re: [oslc-core] Core issue 164, OSLC paging should support POST with an application/x-www-form-urlencoded body


Jim,

I've added an oslc:postBody property to the oslc:ResponseInfo.ttl file. But I don't see it in https://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/specs/core-vocab.html#responseInfo. Is there something else that needs to be done for that change to show in the document?

Do you want me to correct 4.11 Resource Paging to reflect the proposed change?

Best regards,
David




From:        "Jim Amsden" <jamsden@us.ibm.com>
To:        "OSLC Core TC (oslc-core@lists.oasis-open.org)" <oslc-core@lists.oasis-open.org>
Date:        10/05/2018 19:01
Subject:        Re: [oslc-core] Core issue 164, OSLC paging should support POST with an application/x-www-form-urlencoded body
Sent by:        <oslc-core@lists.oasis-open.org>




David,
I don't recall the specifics of oslc:postBody in ResponseInfo. I must have missed that. Perhaps you could add it?


RE LDP vs. OSLC paging - LDP paging was never completed, and there has been no activity on it for almost three years. I'm an not aware of any implementations of LDP paging. OSLC paging is implemented in all the IBM jazz.net based products, and likely many other OSLC 2.0 based clients and servers. So I think OSLC paging is a SHOULD and LDP paging is a MAY.



Jim Amsden, Senior Technical Staff Member

OSLC and Linked Lifecycle Data

919-525-6575





From:        
David Honey1 <DavidHoney@uk.ibm.com>
To:        
Jim Amsden <jamsden@us.ibm.com>, "OSLC Core TC (oslc-core@lists.oasis-open.org)" <oslc-core@lists.oasis-open.org>
Date:        
05/10/2018 12:49 PM
Subject:        
[oslc-core] Core issue 164, OSLC paging should support POST with an application/x-www-form-urlencoded body
Sent by:        
<oslc-core@lists.oasis-open.org>




Issue
https://issues.oasis-open.org/browse/OSLCCORE-164relates to OSLC paging should support POST with an application/x-www-form-urlencoded body.

Jim, the core spec at
https://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/specs/oslc-core.html#resourcePagingand the responseInfo shape at https://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/specs/core-vocab.html#responseInfodoesn't address this issue. I think we agreed that we would include an oslc:postBody in the responseInfo.

I also think we have the emphasis of the following the wrong way round:

4.11.1 OSLC Services SHOULD support [
LDPPaging] to enable clients to retrieve large LDP resources (LDPRs) a page at a time.
4.11.2 OSLC Services MAY support a
Resource Paging Capability as defined in [OSLCCore2] to enable clients to retrieve large resources a page at a time. This capability is included to preserve compatibility with [OSLCCore2].

I think 4.11.2 should be a SHOULD, and 4.11.1 should be a MAY. I know of no query capabilities that implement LDP paging. All the ones I have seen that support paging use 4.11.2. So clients consuming query capabilities are likely to only support 4.11.2.


David.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


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