We don't include them because noone has ever wanted to constrain them,
so currently it would serve no purpose, but obviously we could include them.
- thomas
We don't include them because noone has ever wanted to constrain them,
so currently it would serve no purpose, but obviously we could include them.
- thomas
there is already an assertion in the RM. Where/how do you want to use it
in an archetype?
- thomas
I'm not sure if I have understood your question, but there isn't
already assertion support on the AOM?. just put an assertion of the
restricted and desired condition (in this case something like this:
"|event.time - history[atxxxx].origin|=P10M")
I don't really see the big issue about defining things like this
Technically there isn't. It's about clarity for modellers. The above
makes perfect sense to us technical people, but now we can't have a
simple constraint on Event.offset, which clinical people can understand,
it means we have to have some more complex UI interface in the modelling
tool, so that the constraint is comprehensible to normal mortals. That;s
why I am more interested in a simpler constraint (based on a computed
property) and putting the expression further back in the tool structure.
But that's just my view; I am interested to hear other opinions - if
everyone is against computed attributes then we need to find a clean
solution for this.
- thomas
I found that offset was a stored value at openEHR RM 0.95 (back in 2005), but then it became a computed method.
2012/1/15 Thomas Beale <thomas.beale@oceaninformatics.com>
A possible problem I can envision is that this opens the door to the creation of invalid archetypes without the possibility of validating them at design time.
A quick and dirty example just to get the idea. In an archetype, the HISTORY.origin is fixed to “T10:00:00”, a child EVENT.time is fixed to “T18:00;00”, and finally the EVENT.offset is fixed to “PT5H”. Offset is clearly not valid regarding time and origin, but we do not know it since the expression to calculate it is not explicit anywhere (only at the RM specifications).
David
2012/1/15 Thomas Beale <thomas.beale@oceaninformatics.com>
that problem can occur even with just two normal attributes, if they
happen to have a mathematical relationship...
- thomas