Hi,
Thanks Diego, Silje & Ian. That was helpful
As Ian points out, I was talking about ‘Node names’ and not ‘Node values’.
I think the ‘node value’ part is quite intuitive and clear. We already use it in actual practice and use a SNOMEDCT server to code data into a composition and also query them using AQL. This is done at the application where a type ahead search brings up matching values and the user chooses the most appropriate one. (BTW, India is a member of IHTSDO and so have a license to use SNOMED CT freely.)
However the coding of ‘Node names’ into composition was not something that I was not very clear about. Ian’s reply has made things a lot more clearer. So the ‘bindings’ are put there during design for reference and may be used to create ‘mappings’ on the node names at instance creation. And if this is done, they become queryable. However this coding may not be a run-time user decision, but a decision to be taken during application development.
Will test this out