Stream: implementers
Topic: Forge schemaLocation / schematron
Alexander Henket (Oct 31 2016 at 16:57):
Forge ditches the schema/schematron references upon save. Would love to keep those... Known? @Michel Rutten
Lloyd McKenzie (Oct 31 2016 at 18:00):
Schema/Schematron references are actually prohibited in valid instances, so Forge's behavior is reasonable and an appropriate default. Adding a configuration parameter that allows you to retain them might not be a bad idea though.
Alexander Henket (Oct 31 2016 at 18:03):
I never thought of StructureDefinitions as instances, but you are right obviously. On the other hand: aren't almost all examples in the build checked in with schemaLocation?
Grahame Grieve (Oct 31 2016 at 18:13):
people add them for their schema editor. but they are not published that way
Alexander Henket (Oct 31 2016 at 18:45):
That's right, and I guess that is fair
Stephen Royce (Nov 01 2016 at 01:18):
I also keep them internally to enable schema-aware generation of JSON. Having to get rid of them on publication is a nuisance, but I totally understand it's the only way.
Michel Rutten (Nov 01 2016 at 09:03):
@Alexander Henket interesting request. Forge delegates (XML/JSON) serialization to the .NET FHIR API. There is no specific logic to handle/maintain XSD schema references in Forge. So if I understand correctly, you would like to have a configuration option in Forge that allows you to maintain existing XSD references in a StructureDefinition?
Alexander Henket (Nov 01 2016 at 09:04):
/processing-instruction() and /*/@schemaLocation
Last updated: Apr 12 2022 at 19:14 UTC
