Stream: committers
Topic: GF#16055
Grahame Grieve (Jun 09 2018 at 13:37):
So I am working on GF#16055. it has a rather unfortunately side effect of picking up our logical inconsistencies. Take, for example, MimeTypes. About CapabilityStatement, we say:
Grahame Grieve (Jun 09 2018 at 13:38):
Binding = MimeTypes
"xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.
Grahame Grieve (Jun 09 2018 at 13:38):
so we say that xml, json and ttl are allowed... but we don't explain the mechanism by which they are. And now I need to figure out how they are legal... if they are..
Rob Hausam (Jun 10 2018 at 02:16):
Of course, this relates to the discussion here. To be consistent it seems that the mimetypes value set definition needs to be changed to also include xml | json | ttl (unless we decide we don't want that). Right now it's inconsistent.
Grahame Grieve (Jun 10 2018 at 06:02):
I guess. They'd have a different code system...?
Rob Hausam (Jun 10 2018 at 19:51):
Yes (presumably a FHIR-defined cs for those 3 codes).
Last updated: Apr 12 2022 at 19:14 UTC
