Stream: terminology
Topic: Operation Definitions
Peter Jordan (Sep 10 2020 at 23:29):
Recent Touchstone testing has highlighted that some Terminology Server implementations are placing the definitions of operations defined by resource type (e.g. $expand, $lookup, etc.) in the rest.system element of their Capability Statement, rather than (or in addition to) the rest.resource element. As far as I can see the only definition of a terminology operation listed as a 'resource' type that has a system setting of true is $closure. Do others see this is a significant conformance issue?
Michael Lawley (Sep 10 2020 at 23:35):
We inherit our CapabilityStatement behaviour from HAPI and thus have three operations defined at system level ($closure, $versions, and $convert), with everything else attached to the Resource. I'm unaware if this has caused problems with Touchstone?
Michael Lawley (Sep 10 2020 at 23:39):
@Peter Jordan is there a specific Touchstone test I should run to check this?
Peter Jordan (Sep 10 2020 at 23:58):
@Michael Lawley if you run any of the TS operation tests in Touchstone, you will see a pink ('c') (capability) flag against the Test Script Name and Destination if it considers that "one or more interactions in this test script are not supported by the capability statement". On of the possible warnings is based on where the operationDefinitions are placed in the Capability Statement.
@Richard Ettema was going to investigate further. For example Touchstone is looking at rest/server/operation/definition/reference/valueset-expand and reporting that it can't be found it the operation definition isn't in the rest.system element (c/f rest/server/resource/valueset/read which can be found).
Grahame Grieve (Sep 11 2020 at 02:04):
I can speak to intent here. It's wrong to list an operation under a resource if it is not linked to a resource, but it's not wrong to list an operation under a resource even if it also operates at the system level, when that is still linked to a particular resource
Grahame Grieve (Sep 11 2020 at 02:04):
it would probably be good to clarify this
Last updated: Apr 12 2022 at 19:14 UTC
