>
> As I mentioned on my previous message, my case is not when an ANY / {*}
> appears in the ADL, but when there is no definition at all, I'm talking
> this:
>
> definition
> COMPOSITION[at0000] matches {
> category matches {
> DV_CODED_TEXT matches {
> defining_code matches {[openehr::433]}
> }
> }
> }
>
> 1. I'm not sure if that is interpreted as ANY allowed in
> COMPOSITION.content.
>
> For instance the AE doesn't allow to put a "content matches {*}" there,
> which was my interpretation of what you called ANY.
>
>
Yes, if you don't constrain anything, then the underlying model rules. And
that's equivalent to saying ANY, that's why I insist on that :D
--
David Moner Cano
Web: http://www.linkedin.com/in/davidmoner
Twitter: @davidmoner
Skype: davidmoner
_______________________________________________
openEHR-clinical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
