On Thu, 2009-04-30 at 16:28 +0930, Heath Frankel wrote: > Hi Koray, > > I will let others respond about translations etc, but I did want to > pick up on your point about multi-part file. This was an option > recently consider when we were looking at a mechanism to record an MD5 > Hash of the archetype. There was a desire to provide this hash > external to the ADL itself whilst making it available to the archetype > consumer locally so it was not necessary to query some external notary > service to do the integrity check. Using a multi-part file would > allow the usual PGP message and signature parts to be used. It was > thought to be quite a disruptive change, but if there are other > reasons to do this...
The MD5 for an archetype is now available in the CKM. IIRC, this was to verify the validity of the actual ADL source aas having come from the CKM. But, since archetype exports are being generated as .zip files there is no reason (that I can think of) why this couldn't be applied on the fly if a user selects only a few languages (as Hugh suggested) or if a bundle is created that includes the original language plus specific .po translation files. As I said in my response to Hugh, this is certainly a long term issue but I think it should be addressed sooner rather than later. Cheers, Tim -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090430/93b0b638/attachment.asc>
