More detail on internationalized strings

[howardtrickey]

In trying to redo the Best Practices Guide to use our latest decision on how to handle internationalized strings, I find I need help in identifying the relevant standards.

We have decided that we simply need say that: everywhere there is a CharacterString used, its multiplicity should be allowed to be greater than 1, and that the implementation technology (JSON, XML, etc.) will have its own mechanisms for tagging / annotating those strings with a language identifier.

I have two questions:

1. In XML, it appears the that the standard-defined way of doing this is to use an xml:lang= field on an xml element that we wish to so identify. I suppose this means that any CharacterString type equivalent in XML needs a element to enclose it, right? I guess this is OK but just wanted to check.

2. I am not able to find a standard-specified way to do this in JSON. Does someone have a reference to such a thing? If not, does that mean we have to specify in our JSON implementation spec for our standard how to do such identification? What would we be thinking of? Perhaps a structure like:
   {
   string = "some string",
   lang = "en"
   }

?

[geofizzydrink]

Need to enquire whether this issue has been discussed and/or addressed by INSPIRE

string identifiers in a POI represented as Internationalised text (i.e. multiple instances of the text object per language)

Check with Bart and Carl Reed.