Surely spaces should not be an issue here as these strings do not really
identify anything. Instead, one should be using SCTIDs as in:
terminology:Snomed?v=2002?s=135394005
Further issues include:
* the version should be specified using an ISO 8601 basic representation of
YYYYMMDD (or YYYYMMDDThhmmss Z for development versions),
* "Snomed" is insufficient - is this the International release, or SNOMED
CT-AU or ... My understanding of Release Format 2 (see 7.4.4.13 in the
Technical Implementation Guide) indicates that the moduleId (also an SCTID) is
the appropriate thing to use, and
* one may also (almost always) wish to use a ReferenceSet for terminology
binding. These are also designated by an SCTID (and would require a moduleId
and version as well)
This would then give us something like:
terminology:SNOMED?m=32506021000036107&v=20101130&s=135394005
On 21/02/11 12:22 PM, "Peter Gummer" <peter.gummer at oceaninformatics.com>
wrote:
Diego Bosc? wrote:
> and we have also to deal with spaces!
> <terminology:Snomed?v=2002?s=Antiallergenic drugs (product)>
Spaces are illegal in URIs. The correct form for the subset would be:
subset=Antiallergenic%20drugs%20(product)
- Peter
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
