For the expression constraint language seems strange to encode the characters when there is already an official expression constraint language alternative that avoids these kinds of characters
2017-05-03 13:09 GMT+02:00 Daniel Karlsson <daniel.karls...@liu.se>: > See this page: > https://confluence.ihtsdotools.org/display/SLPG/SNOMED+CT+URI+Standard > Please consider the language used when posting. > /Daniel > > On May 3, 2017 13:03, Bert Verhees <bert.verh...@rosa.nl> wrote: > > On 03-05-17 12:53, Thomas Beale wrote: > > On 03/05/2017 11:40, Bert Verhees wrote: > > On 03-05-17 12:36, Thomas Beale wrote: > > The only missing part, now that I look at the SNOMED Compositional Grammar > <https://confluence.ihtsdotools.org/display/DOCSCG> and Expression > Constraint Language <https://confluence.ihtsdotools.org/display/DOCECL> > specs, is how to create a URI (which is the type of a term binding in ADL2 > <http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_terminology_package>) > from a post-coordinated expression or constraint expression. This should be > trivial, but I don't see where SNOMED has specified it. > > > True, I was looking for that also, a few days ago. I don't have time to > read much now, but there is a document on the SNOMED site on URI's, maybe > it is in there? > I can take a look later or look in my documentation, I have course > materials. I come back to this tomorrow if not someone else already has. > > > The URI spec is here > <https://confluence.ihtsdotools.org/display/SLPG/SNOMED+CT+URI+Standard>, > but it doesn't address URIs for expressions either. > > (All the SNOMED language specs appear to be here > <https://confluence.ihtsdotools.org/display/SLPG/SNOMED+CT+Computable+Languages> > these days - nice and convenient, and also nicely published. We probably > should go back to linking to them somewhere on the openEHR site). > > > I checked my course materials from last year, lucky I found it quickly, > there is not any mentioning of URI's for expressions, so I guess it does > not yet exist. > > Stupid. > > Bert > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > -- [image: VeraTech for Health SL] <https://htmlsig.com/t/000001C268PZ> [image: Twitter] <https://htmlsig.com/t/000001C47QQH> [image: LinkedIn] <https://htmlsig.com/t/000001C4DPJG> [image: Maps] <https://htmlsig.com/t/000001BZTWS7> Diego Boscá Tomás / Senior developer diebo...@veratech.es yamp...@gmail.com VeraTech for Health SL +34 961071863 <+34%20961%2007%2018%2063> / +34 627015023 <+34%20627%2001%2050%2023> www.veratech.es Su dirección de correo electrónico junto a sus datos personales forman parte de un fichero titularidad de VeraTech for Health SL (CIF B98309511) cuya finalidad es la de mantener el contacto con usted. Conforme a La Ley Orgánica 15/1999, usted puede ejercitar sus derechos de acceso, rectificación, cancelación y, en su caso oposición, enviando una solicitud por escrito a verat...@veratech.es.
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
