Documentation issue PUT Composition about specifications-its-rest HOT 3 CLOSED

thanks @jakesmolka, you are right about this, I will change(fix) this in the upcoming release.

from specifications-its-rest.

I'm just now realizing that my proposal might not be correct, too.

The snippet

mentions the composition ID in the request body, which by my knowledge would need to be of type version_uid (referencing a specific version, itself). The versioned_object_uid in the URL would be of type, well, versioned_object_uid (referencing the version container). Those would never match.

Or is this how it is supposed to be, i.e. "match" is meant as "the version_uid should be a matching version of that versioned_object_uid in the URL" and not "equals"?

from specifications-its-rest.

The "match" here refers to semantic matching, i.e. the COMPOSITION.uid.value in the body should relate to that of the "owning" versioned_object_uid. It was not about exact version-matching, which is handled by that If-Match={preceding_version_uid} header.
I rephrased the text there, hopefully is more clear now.

from specifications-its-rest.