pablo pazos wrote: > I think the URI way to define constraint bindings can be ambiguous > and hide some semantics needed to understand where to find the > terminology terms and codes. > Please correct me if I'm wrong: > > One archetype can have this: ["ac0001"] = <terminology:Snomed/2002? > subset=DrugForm> > And another this: ["ac0001"] = <terminology:Snomed/2002?s=DrugForm>
The latest Archetype Editor beta release that I mentioned before would output the first one. It wouldn't know that s=DrugForm is supposed to be a subset in the second one. As Diego mentioned before, this needs to be documented in a specification somewhere. I don't write the specs, though, so I'm not sure where that would be ;-) - Peter
