Re: [scim] Update pagination draft

Anuradha Karunarathna <anuradha199528@gmail.com> Sat, 03 December 2022 02:29 UTC

MIME-Version: 1.0
References: <CA+OkT=-hkZi2m4oWqk04D9fnrBGGmuk5iqzdO3GMqAYAd=wUig@mail.gmail.com> <PH8PR19MB69529B421BE1BBFBD12A1063E1129@PH8PR19MB6952.namprd19.prod.outlook.com>
In-Reply-To: <PH8PR19MB69529B421BE1BBFBD12A1063E1129@PH8PR19MB6952.namprd19.prod.outlook.com>
From: Anuradha Karunarathna <anuradha199528@gmail.com>
Date: Sat, 03 Dec 2022 07:59:26 +0530
Message-ID: <CA+OkT=9yV82qZb6N-YNS=g9sd61eQL1F8VA=8gj4ZDYyQ9pt5A@mail.gmail.com>
To: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>
Cc: "scim@ietf.org" <scim@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cb489205eee339fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/hAIYkZrcOFwPYJA0no1FX-FIvxs>
Subject: Re: [scim] Update pagination draft
Precedence: list

Hi Matt,

I believe including previousCursor usage explanations in the specification
is a must, having an example is easier for the reader to follow it and
avoid confusion.

Thanks,
Anuradha Karunarathna
SSE - WSO2

On Tue, Nov 29, 2022 at 10:21 AM Matt Peterson (mpeterso) <
Matt.Peterson@oneidentity.com> wrote:

> Anuradha
>
>
>
> I have delayed publishing draft version 02 as I wait or feedback on a few
> topics.  Thank you for your feedback on previousCursor.  Are you proposing
> that we should add use of previousCursor in the examples, or simply better
> explanation of how to use it.
>
>
>
> Thank you for noticing the typos, I will make sure these are addressed in
> draft version 02
>
>
>
> --
>
> Matt Peterson
>
>
>
> *From:* scim <scim-bounces@ietf.org> *On Behalf Of * Anuradha Karunarathna
> *Sent:* Wednesday, November 23, 2022 9:42 PM
> *To:* scim@ietf.org
> *Subject:* Re: [scim] Update pagination draft
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> follow guidance, click links, or open attachments unless you recognize the
> sender and know the content is safe.
>
>
>
> Hi Matt and Danny,
>
>
>
>    1.
>    2.
>    3. We don’t see any update on moving backward using the previousCursor
>    in this published
>    4. cursor pagination draft version-01, even though it is mentioned in
>    the IETF-115 meeting
>    5. https://www.youtube.com/watch?v=XnnYKEVz5Yg&t=2960s
>    <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXnnYKEVz5Yg%26t%3D2960s&data=05%7C01%7Cmatt.peterson%40quest.com%7C6699731a6da6430d37f408dacdd63f57%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C638048617321402458%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WTqJmN0Pd86RBVPAVHJHGmWmVnD2IYyXhqWOQegd9o0%3D&reserved=0>
>    6. as a published change in version 01.
>    7.
>
> If the previousCursor is an attribute that could be included in the
> response (even if it is OPTIONAL), the specification should mention how to
> use that previousCursor and move backward.
>
> We hope this will be updated in version 02 of the draft.
>
> 2.
>
> 3.
>
> 4.      Also just want to note there are typos in
>
> 5.
>
> [Page4] When using  "./search", the client would pass the parameters
> defined in Section 2 -> "./search" should be changed to "/.search"
>
> [Page5] POST /User.search -> should be changed to POST /Users/.search
>
>
>
> Thanks,
>
> Anuradha Karunarathna
>
> SSE - WSO2
>

[scim] Update pagination draft Matt Peterson (mpeterso)
Re: [scim] Update pagination draft Anuradha Karunarathna
Re: [scim] Update pagination draft Matt Peterson (mpeterso)
Re: [scim] Update pagination draft Anuradha Karunarathna