In the specifications there are two different classes for binding: Term_binding_item and Query_binding_item. When using the second one, you can point to arbitrary URIs. Any character can be included in a URI, as long as it is encoded. e.g.
http://diebosto2.pc.upv.es:8888/SnomedQuery/ws/JSONQuery?query=%3C%3C118234003%20%7C%20%20%7C%20MINUS%20(%3C%20404684003%20%20%7C%20%20hallazgo%20cl%C3%ADnico%20%20%7C%20%20:%7B%20[3..*]%20363698007%20%20|%20%20sitio%20del%20hallazgo%20%20|%20%20=%20%3C91723000%20%20|%20%20estructura%20anat%C3%B3mica%20%20|%20%20%7D)&cache=true 2017-01-24 13:19 GMT+01:00 Bert Verhees <bert.verh...@rosa.nl>: > > > Op di 24 jan. 2017 om 12:55 schreef Diego Boscá <yamp...@gmail.com>: >> >> Yes, as you say ADL1.4 doesn't support this, so we opted to go the URI way > > > Hi Diego, I wonder how you get SNOMEDpostcoordinated expressions to fit into > the specs of ADL 1.4.x. > > I think an URL even has more illegal characters. > > Bert > > _______________________________________________ > openEHR-implementers mailing list > openEHR-implementers@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org _______________________________________________ openEHR-implementers mailing list openEHR-implementers@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
