Specify that DFC LDP servers must support PATCH and/or PUT

[lecoqlibre]

@simonLouvet We should specify that DFC LDP servers must support PATCH and/or PUT as the LDP spec does not require servers to support them:

4.2.4 HTTP PUT

Per [RFC7231], this HTTP method is optional and this specification does not require LDP > servers to support it.

4.2.7 HTTP PATCH

Per [RFC5789], this HTTP method is optional and this specification does not require LDP >servers to support it.

[simonLouvet]

exact. Put used because patch involves a great deal of complexity

[RachL]

@simonLouvet @lecoqlibre can we close this one?

[simonLouvet]

@RachL No, question of @lecoqlibre don't have explicit answer.

I think DFC servers have to implement PUT because it's the easiest way to update data on one platform from another. On the other hand, we can rule out PATCH, which is complex to specify. Is ok for you @lecoqlibre ?

[lecoqlibre]

I would like the standard to have a possibility to patch data. PATCH is very useful as it allows to change only a part of the data. Also it consumes less resources as we only pass the modified data and not the whole dataset.

I was thinking about using N3 patch like in the Solid protocol.

Why do you think it's complex to specify @simonLouvet?