openehr / reference-models Goto Github PK

Instead, the name attribute is currently on CONTEXT_VARIABLE, which is contrary to the published spec.

I'm talking about the BMM file models/openEHR/Proposed/BMM/openehr_proc_task_planning_110.bmm, of course

Ref: https://github.com/openEHR/reference-models/blob/master/models/openEHR/Release-1.0.2/XSD/Content.xsd#L125-L131

Currently modeling tools like the AR are generating archetype_node_id for the ISM_TRANSITIONs, and that generates invalid paths in the RM since we can't store the nodeID in the ISM_TRANSITION.

I'll do a fix to my merged XSD https://github.com/ppazos/cabolabs-ehrserver/blob/master/xsd/Version.xsd
When the issue on the RM is solved, we can make the change on the official XSDs.

Raised a JIRA issue for that: https://openehr.atlassian.net/browse/SPECPR-222

@wolandscat In basic types bmm, mapping property of DV_TEXT is defined as follows:

["mappings"] = (P_BMM_CONTAINER_PROPERTY) <
				name = <"mappings">
				type_def = <
					container_type = <"Set">
					type = <"TERM_MAPPING">
				>
				cardinality = <|>=0|>
				is_im_runtime = <True>
			>

According to specs, type_def has type P_BMM_CONTAINER_TYPE and this type has a mandatory type_def field . Based on the definition, it feels like type_def should not be mandatory. If I'm wrong, then it should be written in the bmm file but I have no idea what purpose it would serve here...

@wolandscat Should not the definition of TERM_MAPPING in basic types bmm file have any as its ancestor?