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.openehr.org > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.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/attachments/20141006/a50ebb7a/attachment.html>
