Sorry Thomas, this email cross-mailed your replies. I wasn't looking for new emails while writing this one.
Bert Op 24-6-2012 14:21, Bert Verhees schreef: > Thanks, David for your answer. > > Excuse me my bit confusing email from yestrday, I was in a hurry > preparing a meal for guests, and at the same time working. > > This not about bugs but mostly about features as designed > > Although there are formal reasons for the current status of the > archetype-editors, is the situation not very satisfying for > customers/users, and does not help to get customers to choose for the > OpenEHR architecture. > Silently losing parts of archetypes, having to work with text-editors, > unpredictable behaviour. > > - The LinkEHR-editor does not accept OCEAN-editor constructs as > C_DV_QUANTITY, and thus, does not allow multiple constraints on a > DV_QUANTITY > - The Ocean-editor silently removes the DV_QUANTITY construct created > by the LINKEHR-editor, and asks the the user to save the changes. If > the user has made some changes and wants to change them, and he is > unaware of the problem, he removes without knowing his DV_QUANTITY > constructs, which are legal constructs. > - The OCEAN editor silently removes the NodeID on DataValues which are > always created by the LinkEHR editor. > - The LinkEHR editor silently adds NodeID's on DataValues as the > archetype does not have them. > > /The problem with the NodeId on ELEMENT-values is more serious than it > appears, because software can use the path to the ELEMENT-value > instead of the path to the ELEMENT itself. > After opening and saving the archetype in the OCEAN-editor, the > node-id's are gone, and this can render software to become useless, > because the paths the software used are not anymore visible. > The recreating of the NodeID's is not a solution because there is no > guarantee the node's will get the same at-codes. > / > - The LinkEHR creates per default the line: terminologies_available = > <...> which is not accepted by the Ocean-Editor > - The OCEAN editor still not is able to create Demographic archetypes, > the LINKEHR editor does. > > Solutions could be: > - Let the LinkEHR editor accept C_DV_QUANTITY and C_DV_ORDINAL as the > Ocean editor does > - Let the Ocean editor accept DV_QUANTITY constructs. > - Never change archetypes silently!!! > - Make the creation of NodeID's on datavalues in the LinkEHR editor > optional (configurable and put it default off, as it is only for > transition-purpose which isn't possible in the free version) > - Agree on the "terminologies_available = <...>"-line so this does not > give stupid error-messages > - Add Demographic archetypes to the Ocean-editor > > Also, there is a bugs, which is not mentioned above. > > A warning comes up, that the archetype_id does dif from the filename. > The LinkEHR editor offers three choices: > - Save (ignore warning) > - change the ID to the filename > - change the file name to the id > The first two options do the same, this is unexpected and is a bug. > > regards > Bert Verhees > > > _______________________________________________ > 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/20120624/3ccab94b/attachment-0001.html>
