Mattias Forss wrote: > 2006/10/9, Mattias Forss <mattias.forss at gmail.com>: > >> 2006/10/8, Sam Heard <sam.heard at oceaninformatics.biz>: >> >>> Christoph >>> Some things have been around for a long time in our development and one was >>> to have state defined at the root level even though it applied to each >>> event. The current editor should read both but saves the correct version. >>> The result is attached, Sam >>> >> I should point out that the embedded state within each event isn't >> supported by the Java Archetype Editor (only separate state with >> history), but a new version that supports this will probably be out >> soon... >> >> Actually, when the Java editor finds a state defined at the root level >> it is transformed to a state with history because that is the closest >> thing it resembles. >> >> > > Another question related to this. Is there any need in an archetype > editor to specify different data and state for some events instead of > always creating them in the first event in the history and then let > all the succeding events reference (use_node) the data and state in > the first event? If a user decides to edit ADL manually and sets > different data and state for some events, it is not supported by > neither of the current archetype editors... > In general this should not happen, since the phenomenon being recorded in each event is supposed to be the same one, just at different time-points.
- thomas beale _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
