Archetype meta-data - moving foward
On 03/05/2013 11:28, Diego Bosc? wrote: > By the way, we should use the momentum to also revamp the available > metadata. A few ideas: > > - Move 'copyright' from language specific information to general > metadata (It's not being really translated at the moment). > - Move 'references' from other_details to general metadata (It's > important enough IMHO). > - Information about date of validation, validity time and who validated it. > - RM version this archetype was based on. > - etc. > Personally I would agree with all of the above. I have already added the rm_release to the ARCHETYPE class now in the AOM (not yet pushed up), but for the others, I suggest we try to create a wider discussion to do this exercise with a small amount of discipline, but still be in a crowd-sourcing mode (is that possible ;-) To that end, I added a child page to the Knowledge Artefact Identification page <http://www.openehr.org/wiki/display/spec/Development+and+Governance+of+Knowledge+Artefacts>, here <http://www.openehr.org/wiki/display/spec/Knowledge+Artefact+Meta-data>, dedicated to meta-data. I added some tables where we can potentially review the current model and propose changes. If people think this isn't sufficiently detailed, feel free to rework it in another way. - thomas -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130503/bce7c26b/attachment-0001.html>
Updated ADL, AOM 1.5 and new ODIN specifications
By the way, we should use the momentum to also revamp the available metadata. A few ideas: - Move 'copyright' from language specific information to general metadata (It's not being really translated at the moment). - Move 'references' from other_details to general metadata (It's important enough IMHO). - Information about date of validation, validity time and who validated it. - RM version this archetype was based on. - etc. 2013/4/26 Thomas Beale : > On 26/04/2013 04:17, Shinji KOBAYASHI wrote: >> >> Hi Thomas Beale, >> >> At first, I am much sorry about lacking links. >> http://www.rugson.org/pdf/PSRCPattaya2012.pdf >> In this presentation, serialisation formats were compared with >> features and metrics, such as size and (de)serialise performance. >> >> And the second, to address binary data in ODIN format, I think using >> typing system might be good. >> ex. >> my_binary_data = (Binary:Base128)<211234blurblur> >> > > that's not a bad idea at all. I need to think about that > > > - thomas > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
openEHR Subversion => Github move progress
Hey that?s really awesome! Cheers, -koray From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Roger Erens Sent: Saturday, 13 April 2013 11:44 a.m. To: For openEHR technical discussions Subject: Re: openEHR Subversion => Github move progress Hey guys, now that openEHR is on github, have you realised that WE'RE ALL REALLY WRITING HISTORY? See, e.g. http://starlogs.net/#openEHR/gdl-tools Now that's gonna baffle them at Medinfo! Cheers, On Fri, Mar 22, 2013 at 12:13 AM, Thomas Beale mailto:thomas.beale at oceaninformatics.com>> wrote: The last of what I think are the active Subversion repositories on the old openEHR.org server has been converted to GitHub now (the Archetype Editor). Repositories which appear to be inactive but could be converted if anyone wants: * liu_knowledge_tools (Linkoping has a more recent version of this AFAIK) * the original 'knowledge' repository containing a lot of old NHS archetypes * knowledge_tools_java - not sure about this one. * ref_impl_python For those who have links, checkouts or other pointers to any openEHR SVN repositories, please now refer to the Github openEHR repositories<https://github.com/openEHR>. Any questions like 'where did xxx go?', feel free to post them here. - thomas beale ___ openEHR-technical mailing list openEHR-technical at lists.openehr.org<mailto:openEHR-technical at lists.openehr.org> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org __ Information from ESET NOD32 Antivirus, version of virus signature database 8291 (20130503) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130503/250bf9d7/attachment.html>
OpenEHR Framework Project
This sound as a great idea to me too! Regards Mate - Original Message - From: "Bert Verhees" To: "For openEHR technical discussions" Cc: openehr-technical at lists.openehr.org Sent: Thursday, 2 May, 2013 11:59:54 PM Subject: OpenEHR Framework Project Op 1 mei 2013 om 15:31 heeft Thomas Beale het volgende geschreven: > most of the difficult algorithms have been worked out in existing tools, so a > fair bit of logic can be ported or re-used. Expect some announcements on this > in the near future, and be prepared to contribute! Hi Thomas, I like the idea of creating a tooling set for Eclipse, which can be used to model, combine, CKM, text, gui's, archetypes, templates, Rong's GDL, a more or less complete tooling set for OpenEhr, and also EN13606. When being build modular, it is easier for people to step into the project by signing in in a module of part of it. When the project supports also programming inside the Eclipse framework, by experiences shared, good documentation, etc, it will be interesting for people to step in, also for people more interested in Eclipse then OpenEhr. What we need to do is define the project, splitting up it in modules, organizing infrastructure, wiki, github. I am very grateful for the offer you make to share the complex algorithms, so they can be base for rewriting them in other languages. I think it is a good idea, Thomas, and we need to start with thinking and communicating. Regards Bert ___ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
