Multi-level modelling - what does it mean?

2013-04-08 Thread Thomas Beale
s.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130408/bd0b192f/attachment.html>

The Truth About XML was: openEHR Subversion => Github move progress [on behalf of Tim Cook]

2013-04-08 Thread Randolph Neall
ailman/listinfo/openehr-** > technical_lists.openehr.org<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org> > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130408/84293f5b/attachment.html>

The Truth About XML was: openEHR Subversion => Github move progress [on behalf of Tim Cook]

2013-04-08 Thread Thomas Beale
I am always somewhat surprised as well. Thanks by the way for your clarifying notes, that is exactly how I would summarise the discussions. - thomas On 07/04/2013 22:08, Randolph Neall wrote: > Hi Thomas, > I'm surprised that at this advanced stage of openEHR's maturity you'd > still have to d

The Truth About XML was: openEHR Subversion => Github move progress [on behalf of Tim Cook]

2013-04-08 Thread Ian McNicoll
Hi Randy, I take your point about there being two threads in this discussion but I think they *are* closely related. The nub of Tim's argument, if I understand it correctly, is that a two-level model is appropriate but that a three-level model (i.e openEHR specialisations and templates) , allowin