Some questions from the External package (v0.9) section 4.1: assumed types. This section is very brief. It's a bit of an odd section, as important things are left unstated (i.e. what are the expectations of whitespace for the STRING type?) while trivial things such as cummutivity of + are defined.
section 5.3.1, namespace. Why doesn't the valid namespace character set include such characters as :/&+ that are valid in URI's? section 5.3.2 & 5.3.3: ACCESS_GROUP_REF and PARTY_REF inherit from OBJECT_REF but this isn't stated in the tables. is there some pattern to when things are and aren't stated in the tables? section 5.3.5.1. There's a throwaway line at the end of the section that archetypes can also be identified by ISO OID's. While I hope that I never see that ;-), it's not clear from the stated syntax how that would fit in. Nor, while we're here, is it clear whether it's valid to use some terminology based identification (such as LOINC for pathology archetypes) Grahame - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
