Mattias Forss wrote:
> Hi all,
>
> I found there is an error at page 42 in the class description of 
> CONTENT_ITEM in the EHR specification. As you can see in the inherit 
> field, the class inherits itself, but it should inherit the class 
> LOCATABLE from the common package instead.
>
fixed - thanks
> Another thing I would like to be clarified is that the 
> archetype_details field of LOCATABLE is mandatory for all archetype 
> root points. The COMPOSITION and ENTRY classes have the following 
> invariants respectively:
>
> Is_archetype_root: is_archetype_root
> Archetype_root_point: is_archetype_root
>
> However, it should probably be pointed out that if either of the 
> classes are archetype root points, the archetype_details field 
> inherited from LOCATABLE is mandatory and must not be void. I assumed 
> that COMPOSITON classes can be archetype root points as well, but I am 
> not sure of the meaning of the term.
See the class LOCATABLE - you will see it has the invariant:

Archetyped_valid: is_archetype_root xor archetype_details = Void

this means that if is_archetype_root is True, then archetype_details /= Void

- thomas

>
> Regards,
>
> Mattias
> ------------------------------------------------------------------------
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>   


-- 
___________________________________________________________________________________
CTO Ocean Informatics (http://www.OceanInformatics.biz)
Research Fellow, University College London (http://www.chime.ucl.ac.uk)
Chair Architectural Review Board, openEHR (http://www.openEHR.org)


_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical



Reply via email to