Re: [Jmap] JMAP for Migration and Data Portability

[Joris Baum <[e-mail]>]

Hi Neil,


Yes. You are correct. If the goal is to signal that the whole /set 
method is not supported, then using the accountReadOnly error for that 
is a good solution. Thank you for that hint. My first thought was to set 
maxObjectsInSet to 0 and then return a "tooLarge" error. I guess both 
approaches could work here.

However, I came from a different direction. My thought was that some 
JMAP methods are quite powerful on their own. For example, /set features 
create, update and destroy which other API often have as separate calls. 
It also features ifInState, which is typically not interesting for the 
data portability use case.

It would be nice to have a way to signal in a more fine-grained way that 
a server does not support things like create, update or destroy for 
/set. As far as I can see, SetError could be used for that for these 
three properties. In case a client tries to do /set with an ID and an 
object in "update", a server could place the ID in the "notUpdated" 
property along with a SetError explaining that it does not support 
update. This would not be machine-readable, however.

For /query, the errors unsupportedSort and unsupportedFilter already 
exist, which seem to be intended exactly for such a case: to signal that 
a server does not support certain aspects of the /query method.

Regards,


Joris


On 22.03.23 00:39, Neil Jenkins wrote:
> On Wed, 22 Mar 2023, at 01:43, Joris Baum wrote:
>>
>> /set
>>
>> * "maxObjectsInSet" - no support for /set
>>
>> * stateMismatch - no support for ifInState (dirty, because it signals 
>> an issue on the client side)
>>
>> * SetError - no support for create, update, destory (via description. 
>> Not machine readable)
>>
>
> Do you need to implement |/set| at all? If the only requirement is for 
> access, then you can mark the account |isReadOnly: true 
> <https://www.rfc-editor.org/rfc/rfc8620#page-11>|, and then your 
> implemenation of |/set| is just "return an |accountReadOnly| error".
>
> Cheers,
> Neil.
>
> _______________________________________________
> Jmap mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/jmap

-- 
Joris Baum
Tel: [phone]
Fax: [phone]

http://www.audriga.com  |http://www.twitter.com/audriga

--------------------------------------------------------------------------
audriga GmbH | Alter Schlachthof 57 | 76137 Karlsruhe
Sitz der Gesellschaft: Karlsruhe - Amtsgericht Mannheim - HRB 713034
Geschäftsführer: Dr. Frank Dengler, Dr.-Ing. Hans-Jörg Happel
--------------------------------------------------------------------------