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
