Hi,
I’ve a SECTION archetype with 3 slots:
definition
SECTION[at0000] matches { – Evaluación de vía aérea
items cardinality matches {0..; unordered} matches {
allow_archetype EVALUATION[at0002] occurrences matches {0..1} matches { – EVALUATION
include
archetype_id/value matches {/openEHR-EHR-EVALUATION.via_aerea(-[a-zA-Z0-9_]+).v1/}
}
allow_archetype ACTION[at0003] occurrences matches {0..1} matches { – ACTION
include
archetype_id/value matches {/openEHR-EHR-ACTION.via_aerea(-[a-zA-Z0-9_]+).v1/}
}
allow_archetype ACTION[at0004] occurrences matches {0..1} matches { – ACTION
include
archetype_id/value matches {/openEHR-EHR-ACTION.resumen_actuacion(-[a-zA-Z0-9_]+).v1/}
}
}
}
When I use the ADL parser to get the AOM Archetype instance and print out it’s definition as XML, I see this:
- The SECTION node has path “/”, OK!
- The SECTION has an “items” attribute, this attribute has path “/items”, OK!!!
- The first children of “items” is an ArchetypeSlot with nodeId “at0002”, so I spect that this node has path “/items[at0002]” but has path=“/items”, like the parent attribute.
- Is this correct or is a bug in the ADL Parser?
I’m using adl-parser-1.0.1.jar, the same happens with adl-parser-1.0.2-SNAPSHOT.jar
BTH, I use XStream to serialize the objects to XML.
<org.openehr.am.archetype.constraintmodel.CComplexObject>
false
/
SECTION
1
1
true
true
at0000
<org.openehr.am.archetype.constraintmodel.CMultipleAttribute>
false
/items
items
REQUIRED
<org.openehr.am.archetype.constraintmodel.ArchetypeSlot>
false
/items
EVALUATION
0
1
true
true
at0002
… the XML continues
Best regards,
Pablo Pazos Gutierrez