Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

R5
Work Group:

FHIR Infrastructure
Related Artifact(s):

StructureDefinition
Resolution Description:

Hide

We will put a ballot comment on ElementDefinition indicating our intention to remove constraint.xpath. Provided we pass ballot with that assertion, we'll then drop it from the spec.

We will update the tooling so that Schematron no longer exposes constraints.

Show
We will put a ballot comment on ElementDefinition indicating our intention to remove constraint.xpath. Provided we pass ballot with that assertion, we'll then drop it from the spec. We will update the tooling so that Schematron no longer exposes constraints.
Resolution Vote:
Grahame Grieve/Christiaan Knaap: 13-0-0
Change Category:
Correction
Change Impact:
Non-compatible
Applied for Version:

R5

ElementDefinition.constraint.xpath is currently "TU" and xpath expressions are:

Not executed during the build
Often unreliable (e.g. these two expressions can't possibly be equivalent; I'm having trouble understanding the xpath, but it doesn't mention 'logical')

As such they are a liability. Authors don't know how to write or test them, and we discover problems later. (See history at https://jira.hl7.org/issues/?jql=text%20~%20%22constraint%20xpath%22)

Proposal: remove ElementDefinition.constraint.xpath (no need to deprecate because it's only Trial Use)