Stream: implementers
Topic: Use of XML schemata
Stephen Royce (Apr 18 2016 at 07:24):
If I wanted to include schemaLocation in my resource XML and ensure that I was always using that latest schema, is there public location I can point to that is guaranteed to be always up to date?
Stephen Royce (Apr 18 2016 at 07:26):
And, before anyone asks, while my stuff is still in development, I'm happy to be working with resource definitions that are in a state of flux. Obviously, that won't continue, but I want to make sure I go live with the most recent resource definitions that I can.
Grahame Grieve (Apr 18 2016 at 07:37):
there's a rule that says: no schema definitions in the xml
Brian Postlethwaite (Apr 18 2016 at 20:44):
Should be able to use it in creating the examples, then strip before publishing right?
Brian Postlethwaite (Apr 18 2016 at 20:45):
If that was your intension, then you can point to the continuous build, or use a local build and use the files from there.
Stephen Royce (Apr 18 2016 at 22:38):
My intension is to use is when creating and storing locally -- i.e. internal storage -- because my database gives me schema checking for free which will help me improve data quality. I didn't realise you weren't supposed to send the schema definition with the XML, but that can be easily stripped out before transmission. I assume the continuous build is here: http://hl7-fhir.github.io/; but what would be the URL for the XML Schemata?
Brian Postlethwaite (Apr 18 2016 at 22:55):
that folder, eg http://hl7-fhir.github.io/patient.xsd
Grahame Grieve (Apr 18 2016 at 23:12):
you need to use a version specific reference - so not the current version or the current build. Instead, pick a specific version from the lists here:
Grahame Grieve (Apr 18 2016 at 23:12):
http://hl7.org/fhir/directory.html
Grahame Grieve (Apr 18 2016 at 23:12):
then, reference fhir-single.xsd - that's your best option
Stephen Royce (Apr 18 2016 at 23:45):
That's the point. I don't want a specific version because that won't get updated with changes. For a specific version, I can just download the schemata and use them locally.
Stephen Royce (Apr 19 2016 at 00:11):
Which is what I've been doing to date because it's faster and more reliable, but I'm finding that it's a challenge to keep the resource definitions up to date that way.
Grahame Grieve (Apr 19 2016 at 00:55):
well, you know, we might change the schema between versions - we do, in fact. That's why I don't recommend using a version independent schema reference
Stephen Royce (Apr 19 2016 at 01:22):
While I'm still in development, I'm prepared to accept that risk and deal with it when it happens.
Last updated: Apr 12 2022 at 19:14 UTC
