[rpp] Re: Partial Updates

[Pawel Kowalik <[e-mail]>]

Hi Mario,

On 27.07.26 18:19, Mario Loffredo wrote:
> Hi Pawel,
>
> In my opinion, the RDAP context is quite different from the RPP context.
> The use of JSONPatch in RDAP is limited to JSContact localizations, 
> and the problem of having stable mapping keys is expected to be 
> limited to those (hopefully rare) cases where contacts have multiple 
> items in the collections used in the JSContact profile.

PK> Even if out-of-topic for this WG I have a different perspective on 
stable mapping keys. Also RDAP clients would be at minimum "confused" 
receiving different keys with each response or different data under the 
same key.

> In RPP, information about the order of items in a collection should be 
> stored in the registry database for each 1-N relationship.
PK> This is then the other topic brought up as a question to the WG. 
Shall RPP require that the order is always same and assured? "Stored in 
registry database" is likely not fulfilled by many registry systems. 
therefore would make deployments of RPP more difficult.
> Wouldn't it be simpler to use the value of the match property as a map 
> key?

PK> JSON allows only for a single string to be a map key. Match object 
may be more complex - for example: remove handle id "XXX" with role 
"adminc". We could come up with JSON representation which would define 
such unique combination as a sting, but I think the solution proposed by 
Maarten is more flexible and maybe even a valuable generic addition to 
the JSON Patch.

Kind Regards,
Pawel