If that is the valid way of defining in an URI form, it is undocumented. the example should be put on the ADL specs.
And again not that difficult to support both kind of bindings. In my opinion, <ORGANIZATIONXXXXX::DrugFormSubset> is way more human readable and needs the same degree of 'computer interpretation' than the URI <terminology:...> 2011/2/21 Peter Gummer <peter.gummer at oceaninformatics.com>: > Diego Bosc? wrote: > >> I know it is on ADL specs, but why limit it to an URI? Second approach >> could also be used to identify a subset > > The URI approach is able to specify subsets, Diego. Here is an > example, generated by the current Archetype Editor beta release > (available from > http://www.openehr.org/svn/knowledge_tools_dotnet/TRUNK/ArchetypeEditor/Help/index.html) > : > > ? ? ? ?constraint_bindings = < > ? ? ? ? ? ? ? ?["Snomed"] = < > ? ? ? ? ? ? ? ? ? ? ? ?items = < > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?["ac0001"] = > <terminology:Snomed/2002?subset=DrugForm> > ? ? ? ? ? ? ? ? ? ? ? ?> > ? ? ? ? ? ? ? ?> > ? ? ? ?> > > - Peter > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >
