Archetyping links

Rong Chen wrote: I would say our use case for the link is also between compositions. For the reasons you mentioned, it would be nice to just use the archetypeId in the constraint for the value (URI) of the link. Then it starts to look like a mini query. It starts looking like a kind of

subscribed to openehr-announce mailing list?

Please consider subscribing to the openehr-announce mailing list (http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-announce) if you are not already. Key openEHR announcements are made only on this list, and it is very low traffic (no posting, only broadcast); this list includes notices

Announcement of the release of Opereffa by the openEHR Foundation

. -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090610/2b525726/attachment.html

Announcement of the release of Opereffa by the openEHR Foundation

Congratulations! /Rong 2009/6/10 Stef Verlinden stef at vivici.nl: Dear Tony, David and Seref, Congratulations to you (and to the openEHR community). This is truly very good news, great work and a major milestone for the openEHR community. I'm confident that this will boost many efforts

Archetyping links

Yes, indeed! It's a choice between composition versus association. Cheers, Rong 2009/6/10 Peter Gummer peter.gummer at oceaninformatics.com: Rong Chen wrote: I would say our use case for the link is also between compositions. For the reasons you mentioned, it would be nice to just use the