suggest setting CapabilityStatement.rest.resource.versioning to versioned-update

[kmbarton423]

Found that the latest release of IBM FHIR Server CapabilityStatement does not provide information for CapabilityStatement.rest.resource.versioning. Though this element is not required, a setting of "versioned-update" would indicate full versioning support.

[lmsurpre]

I think maybe versioned would be more appropriate given the spec's definition of versioned-update from https://www.hl7.org/fhir/valueset-versioning-policy.html:

VersionId must be correct for updates (server) or will be specified (If-match header) for updates (client)

I don't think we check the Resource.meta.versionId during an update....we just overwrite that with the proper value.

However, we do support the "If-Match" header, so I'm not totally sure.

[lmsurpre]

OK, I found that https://www.hl7.org/fhir/http.html#versions has a slightly expanded definition for versioned-update:

Versioning and meta.version is supported, and version aware updates are used - Version ID must be correct for updates (server) or will be specified (If-match header) for updates (client)

The first part of that sounds like what we have: "Versioning and meta.version is supported, and version aware updates are used". My concern is with the next bit (shared by the valueset definiton): "VersionId must be correct for updates"...we might need to ask for clarificatoin on chat.fhir.org

[lmsurpre]

Asked for clarification at https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Clarification.20on.20versioned.20vs.20versioned-update

[lmsurpre]

this was done based on some new failures on the touchstone basic suite. after deploying the updates, that suite is now passing again with 100% conformance.