"Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We *should* forget about small efficiencies, say about 97% of the time: *premature optimization is the root of all evil*"
Knuth, Donald E. "Structured Programming with go to Statements." *ACM Computing Surveys (CSUR)* 6.4 (1974): 261-301. On Tue, Oct 7, 2014 at 9:46 PM, William Goossen <wgoossen at results4care.nl> wrote: > Take care of a big caveat please: all health information systems start and > end with the human being. We should use the IT support that Thomas suggests > where possible, but.... to the extend that humans cannot make mistakes. And > the governance of archetypes / DCMs / valuesets / etc does require human > intervention and hence human understanding. So naming conventions are > important and are a different beast than the versioning of the file / > content. > Thomas' trick with the software reading the meta information is fine for > one > specific purpose eg a record handling 100 archetypes or a composition of 88 > DCMs. However, what if that same system must do this for all 100 archetypes > for 25 - 100 diseases per specialty, with 30 specialties (100 x 25 x 30) > and > allowing all kinds of combinations so x n. Beside the safety and quality > also performance comes into the picture. And I am not speaking yet of each > use of these combinations, e.g. for screens / data entry, storage, > communication, querying, aggregation, decision support etc. > > All the best, > > William Goossen > > -----Original Message----- > From: openEHR-technical [mailto: > openehr-technical-bounces at lists.openehr.org] > On Behalf Of openehr-technical-request at lists.openehr.org > Sent: Tuesday, October 07, 2014 18:00 > To: openehr-technical at lists.openehr.org > Subject: openEHR-technical Digest, Vol 32, Issue 31 > > Send openEHR-technical mailing list submissions to > openehr-technical at lists.openehr.org > > To subscribe or unsubscribe via the World Wide Web, visit > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.or > g > > or, via email, send a message with subject or body 'help' to > openehr-technical-request at lists.openehr.org > > You can reach the person managing the list at > openehr-technical-owner at lists.openehr.org > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of openEHR-technical digest..." > > > Today's Topics: > > 1. Re: Archetype Naming proposals - do we need V0? (Thomas Beale) > 2. Re: Archetype Naming proposals - do we need V0? (Thomas Beale) > 3. Re: Archetype Naming proposals - do we need V0? (Shinji KOBAYASHI) > 4. Re: Archetype Naming proposals - do we need V0? (Ian McNicoll) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 06 Oct 2014 17:00:45 +0100 > From: Thomas Beale <thomas.beale at oceaninformatics.com> > To: openehr-technical at lists.openehr.org > Subject: Re: Archetype Naming proposals - do we need V0? > Message-ID: <5432BCAD.3090902 at oceaninformatics.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 03/10/2014 22:08, Bert Verhees wrote: > > On 03-10-14 22:28, Thomas Beale wrote: > >> Filename is irrelevant, and has been freely choosable for 5-10 years > >> in all archetype modelling tools that I know of. > > Except from CKM, it offers, when I click "Export Archetype (ADL)" a > > file named after the archetypeId with extension ADL or XML, if I click > > on the other. > > > well that's normal - that's on download - the file has to be called > something ;-) > > - thomas > > > > ------------------------------ > > Message: 2 > Date: Mon, 06 Oct 2014 17:40:46 +0100 > From: Thomas Beale <thomas.beale at oceaninformatics.com> > To: openehr-technical at lists.openehr.org > Subject: Re: Archetype Naming proposals - do we need V0? > Message-ID: <5432C60E.6060007 at oceaninformatics.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 06/10/2014 16:52, Shinji KOBAYASHI wrote: > > Hi Thomas Beale, > > > >> openEHR-EHR-ADMIN_ENTRY.encounter.v1 => > >> org.openEHR::openEHR-EHR-ADMIN_ENTRY.encounter.v0.0.1 => review & > >> changes => org.openEHR::openEHR-EHR-ADMIN_ENTRY.encounter.v1.0.0 > > Would file name nomenclature be changed? There is no spec for file > > name of archetype, but archetype ids have been assigned to file names. > > Whereas, : is not available for file name in Windows OS (and old Mac OS). > > > > well, as mentioned before, filenames don't matter, but of course when a > tool > generates a file, it should use an obvious name, something related to the > id. And you are right - ':' won't work on Windows (we'll never stop cursing > the stupid Windows directory and file-naming will we....). > So it will need to be something else, maybe just using the '-' > character. So for that reason, we had better add a file-system friendly > variant of the full id... > > I'll repeat to make it very clear to everyone: tools shouldn't care what > the > filenames, are, they're only there for humans to understand, e.g. if > emailing a file manually. Tools should all do what the AE, TD and AWB do > today: look in a configured directory (tree) for .adl or .adls files, and > read the first couple of non-comment lines to get the meta-data. In the AWB > at least I do this in a 'fast parse' phase, with a dumb mini-parser that > reads file headers. It never looks at the file names at all - every > filename > that matches the regex '.*\.adl' or '.*\.adls' is matched. > > - thomas > > > > ------------------------------ > > Message: 3 > Date: Tue, 7 Oct 2014 02:36:44 +0900 > From: Shinji KOBAYASHI <skoba at moss.gr.jp> > To: For openEHR technical discussions > <openehr-technical at lists.openehr.org> > Subject: Re: Archetype Naming proposals - do we need V0? > Message-ID: > < > CAOMPyp-JnMEPhDy-XPqGb3jZRcF8pTv5_UwwcXAr0nJAXXzttw at mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Thank you for kind explanation. > I was afraid about conflict of file name and file name conversion between > OSs, but it looks no matter. > > Shinji > > 2014-10-07 1:40 GMT+09:00 Thomas Beale <thomas.beale at oceaninformatics.com > >: > > On 06/10/2014 16:52, Shinji KOBAYASHI wrote: > >> > >> Hi Thomas Beale, > >> > >>> openEHR-EHR-ADMIN_ENTRY.encounter.v1 => > >>> org.openEHR::openEHR-EHR-ADMIN_ENTRY.encounter.v0.0.1 => review & > >>> changes => org.openEHR::openEHR-EHR-ADMIN_ENTRY.encounter.v1.0.0 > >> > >> Would file name nomenclature be changed? There is no spec for file > >> name of archetype, but archetype ids have been assigned to file names. > >> Whereas, : is not available for file name in Windows OS (and old Mac > OS). > >> > > > > well, as mentioned before, filenames don't matter, but of course when > > a tool generates a file, it should use an obvious name, something > > related to the id. And you are right - ':' won't work on Windows > > (we'll never stop cursing the stupid Windows directory and file-naming > > will we....). So it will need to be something else, maybe just using > > the '-' character. So for that reason, we had better add a file-system > friendly variant of the full id... > > > > I'll repeat to make it very clear to everyone: tools shouldn't care > > what the filenames, are, they're only there for humans to understand, > > e.g. if emailing a file manually. Tools should all do what the AE, TD > > and AWB do > > today: look in a configured directory (tree) for .adl or .adls files, > > and read the first couple of non-comment lines to get the meta-data. > > In the AWB at least I do this in a 'fast parse' phase, with a dumb > > mini-parser that reads file headers. It never looks at the file names > > at all - every filename that matches the regex '.*\.adl' or '.*\.adls' is > matched. > > > > - thomas > > > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.open > > ehr.org > > > > ------------------------------ > > Message: 4 > Date: Mon, 6 Oct 2014 18:53:02 +0100 > From: Ian McNicoll <ian at mcmi.co.uk> > To: For openEHR technical discussions > <openehr-technical at lists.openehr.org> > Subject: Re: Archetype Naming proposals - do we need V0? > Message-ID: > <CAG-n1KyHp1mtKn2ANFRw21-0r27= > VK80iQtd2MCZo4s2qenuVQ at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Shinji, > > It is a fair question. I do think Bert makes a good case for moving away > from filenames that are a copy of the archetypeId, and I also think that > any > file naming patterns should be advisory rather than compulsory. I don't > think I would want to carry the namespace in a human readable file name. > > Ian > > > On 6 October 2014 18:36, Shinji KOBAYASHI <skoba at moss.gr.jp> wrote: > > > Thank you for kind explanation. > > I was afraid about conflict of file name and file name conversion > > between OSs, but it looks no matter. > > > > Shinji > > > > 2014-10-07 1:40 GMT+09:00 Thomas Beale > > <thomas.beale at oceaninformatics.com > > >: > > > On 06/10/2014 16:52, Shinji KOBAYASHI wrote: > > >> > > >> Hi Thomas Beale, > > >> > > >>> openEHR-EHR-ADMIN_ENTRY.encounter.v1 => > > >>> org.openEHR::openEHR-EHR-ADMIN_ENTRY.encounter.v0.0.1 => review & > > >>> changes => > > org.openEHR::openEHR-EHR-ADMIN_ENTRY.encounter.v1.0.0 > > >> > > >> Would file name nomenclature be changed? There is no spec for file > > >> name of archetype, but archetype ids have been assigned to file names. > > >> Whereas, : is not available for file name in Windows OS (and old > > >> Mac > > OS). > > >> > > > > > > well, as mentioned before, filenames don't matter, but of course > > > when a > > tool > > > generates a file, it should use an obvious name, something related > > > to the id. And you are right - ':' won't work on Windows (we'll > > > never stop > > cursing > > > the stupid Windows directory and file-naming will we....). So it > > > will > > need > > > to be something else, maybe just using the '-' character. So for > > > that reason, we had better add a file-system friendly variant of the > > > full > > id... > > > > > > I'll repeat to make it very clear to everyone: tools shouldn't care > > > what > > the > > > filenames, are, they're only there for humans to understand, e.g. if > > > emailing a file manually. Tools should all do what the AE, TD and > > > AWB do > > > today: look in a configured directory (tree) for .adl or .adls > > > files, and read the first couple of non-comment lines to get the > > > meta-data. In the > > AWB > > > at least I do this in a 'fast parse' phase, with a dumb mini-parser > > > that reads file headers. It never looks at the file names at all - > > > every > > filename > > > that matches the regex '.*\.adl' or '.*\.adls' is matched. > > > > > > - thomas > > > > > > > > > _______________________________________________ > > > openEHR-technical mailing list > > > openEHR-technical at lists.openehr.org > > > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.open > > ehr.org > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at lists.openehr.org > > > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.open > > ehr.org > > > > > > -- > Dr Ian McNicoll > office / fax +44(0)141 560 4657 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > ian at freshehr.com > > Clinical modelling consultant freshEHR > Director openEHR Foundation > Honorary Senior Research Associate, CHIME, UCL BCS Primary Health Care > www.phcsg.org > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > < > http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/atta > chments/20141006/a50ebb7a/attachment-0001.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.or > g > > ------------------------------ > > End of openEHR-technical Digest, Vol 32, Issue 31 > ************************************************* > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at 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/20141007/409b52a8/attachment-0001.html>
