PUT/POST on subrescources instead of PATCH?

[ePaul]

PATCH is not recommended by our guidelines, but often preferred by clients because they don't want to roundtrip the whole object when only a small part of it is actually editable.

An alternative might be to offer a separate endpoint for a sub-resource which allows a PUT (or POST, in case of collections), leaving the rest of the parent resource alone.

Shall we recommend this in the guideline for PATCH?

[tfrauenstein]

@tkrop will provide PR as we discussed in the Guild JF