The idea is simple: add the "LINK" type of archetype to allow linking concepts and use those LINK archetypes in AQL to query the relationships. This can help to implement querying data and context, e.g. I want to query LINKs that link Problems and Lab Test Results, and this can be done in AQL. Without the archetype, this query can be done but in the traditional way, depending on a specific database technology (SQL, XQuery, ...).
Really need to be able to specify attributes of LINKs e.g. meaning value, to follow.
A similar idea might apply when there are relationships using OBJECT_REF like in FOLDERs referencing items, and we want the FOLDERs that contain a COMPOSITION defined by archetype XYZ.
Erik/Seref - Sub-select idea?
that was exactly what I meant.
I like this new operator idea, although we would also need to define where in the hierarchy these links could be.
Does the above mean that the link to the openEHR-EHR-EVALUATION.v1 can be anywhere in the composition structure or just exactly at the composition level?
I think we need to start with some real scenarios to better understand what we are trying to achieve. We need to think about which direction we are traversing the link (this may require more than one operator) and what criteria we want to apply to the link (e.g. the archetype of the target, the type of link, etc).
@Ian, I don't think we should be agnostic about contain or by link relationships, the latter are usually very specific semantics.
Are these kinds of LINKs the same that could be potentially used in the assertions? Can the slot benefit from this LINK improvement?