David Lloyd at CHIME, UCL in London was responsible for the enormous task of entering the model and customising the publishing scripts so that we could have this site, and I am sure it will be highly appreciated by the whole community.
Also, Thomas Beale writes today:[W]e are very close to being able to publish Release 1.0.1 of openEHR. Recent changes have mostly been to do with making openEHR compliant to ISO 8601, the standard for dates and times. We have made quite a few changes to improve the documents in this regard, including:- moving the assumed ISO 8601 semantics to the support IM document (http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/rm/support_im.pdf)- simplifying the class model in the date/time part of the data types IM (http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/rm/data_types_im.pdf)- slight corrections to date/time specificaiton part of the ADL documents- allowing a deviation from official ISO 8601 to support durations that are a mixture of weeks and days (commonly used to define length of pregnancy)Another improvement to openEHR for the new release is to adopt openPGP as they method of digital hashing and signing. This is described in the Common IM (http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/architecture/rm/common_im.pdf). The advantage of openPGP is that it allows for different algorithms to be used (e.g. MD5, SHA-1 for hashing) and the result is always just a self-describing string. See http://www.faqs.org/rfcs/rfc2440.html for openPGP specification. Feedback is welcomed from anyone with expertise in PGP and security in general.The Architecture Overview has been significantly improved, and we would welcome feedback . See http://svn.openehr.org/specification/BRANCHES/Release-1.1-candidate/publishing/index.htmlThe total changes for Release 1.0.1 can be seen at http://svn.openehr.org/specification/TRUNK/history.htm . Don’t be mislead by the number of CRs here – most of these are quite fine-grained, we have opted for small detailed CRs now in order to help implementers as much as possible.
Thomas Beale’s affiliations:
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)