Meeting minutes
Adding validation to the Playground
houcemeddine: Shex doesn't work without BASE.
dbooth: Without BASE it's looking from where the playground was loaded.
dbooth: Should we have a settable BASE in the playground?
eric: Shex is generated internally from the structure defs.
dbooth: Leaning toward only having user select the FHIR version, and the playground uses those schemas that are internally generated.
eric: ok
(Eric shows Houcemeddine where to find the internal shex that was generated.)
HAPI
dbooth: What's remaining to do?
eric: Need to geek w Grahame or someone about how to lay out the tests. Need to make all my changes parametric for the version.
… Then need to figure out how to test it.
dbooth: Probably shouldn't bug grahame yet.
rob: Also try James Agnew.
What's new in FHIR RDF R5
dbooth: Could do a page describing what's new, a webinar? Would be nice to update Harold's tutorial to R5.
eric: Should finish our bug fixes first.
… Shex can do minimal checking, but could be extended for more checking.
… E.g., could point it to a profile, and validate against that.
… Deepak already parses the extensions, but we disabled that because it's hard to say what use case it fits.
… Hard to imagine someone using all the FHIR-defined extensions.
… That code is most useful if you point it at your own profile.
rob: Typicaly people require certain extensions, but do not restrict others.
rob: IG = Implementation Guide
dbooth: Need to follow up w Deepak about whether he could take this on.
ACTION: David to ask deepak whether he could extend the shex effort for specified profiles/extensions
rob: should be able to specify what profile to use, in validating.
Validation parser
jim: No progress at the moment. Grahame's busy. I'll come back to it at some point.
eric: Should ask FHIR folks whether we could make shex files case sensitive.
ACTION: Eric to ask Grahame about using mixed case shex filenames
ADJOURNED