re the pipe- symbol - it’s not just an attribute marker, I think it implies a leaf-node not just any RM attribute.
‘tokens’ - quite probably a bad term. I mean the stringified version of a datatype object.
All I am really suggesting is whether there is value in making the ‘stringified_value’ (also horrible but at least the meaning is clear!!), a RM function, and therefore clearly identifiable whether in JSON or anything else.
So instead of just
“/context/setting”:“openehr::227|emergency care|”,
we make it explicit as
“/context/setting|stringified”:“openehr::227|emergency care|”,
Maybe it is not necessary ]. I guess I am just wary of getting stringified terms disambiguated from ordinary text values.
Where a DV_TEXT can take either a coded_term or plain text, it would be nice to have a neat way of making the datatype/usage clear.
Sorry - went off on a tangent - too hot 