EN/ISO 13606 & openEHR - harmonisation possibilities

Technical (archive)
21

ADL parser.
and I am not saying it should be allowed, just that this kind of
things happen :slight_smile:

22

Diego,

I am still not clear on the actual problem - if it is the ADL workbench parser, would you mind reporting it here? If it is the Java parser, you should report it on the ref_impl_java mailing list.

  • thomas
23

yes, what I mean is attributes like ID or even invalid characters in
the names (like ':'). This is a problem with the parser (and also with
classes identifiers)

24

':' are not valid as names in most operating systems, so it would be a
problem even for adl file names. That's why I don't think it is wise
to allow this one in particular.
The other issue was already 'discussed' on the list
http://www.openehr.org/mailarchives/openehr-technical/msg05294.html

I have also checked the ISO norm and you were right with the attribute
names. I suppose that scopingOrganisation was changed to underscores
to keep the same style, but I think that we should fit to the
standard. I have fixed it and will inform the 13606 association so
they can update it to a new version

25 
':' are not valid as names in most operating systems, so it would be a
problem even for adl file names. That's why I don't think it is wise
to allow this one in particular.

I don’t remember anywhere in ADL/AOM where filenames are specified, and ‘:’, certainly would not work - can you point me to the part of the specification you are talking about - I don’t remember ay part that talks about filenames.

The other issue was already 'discussed' on the list
[http://www.openehr.org/mailarchives/openehr-technical/msg05294.html](http://www.openehr.org/mailarchives/openehr-technical/msg05294.html)

My response would still be the same :wink: David has created this issue on the tracker, which is all we need to remember it.

I have also checked the ISO norm and you were right with the attribute
names. I suppose that scopingOrganisation was changed to underscores
to keep the same style, but I think that we should fit to the
standard. I have fixed it and will inform the 13606 association so
they can update it to a new version

there are a lot of attributes with this problem…

  • thomas