Not all properties of dataType xs:string are multi-language, for example those of type dcterms:identifier. Even more, those must not have multiple languages; Otherwise information is largely obscured.
A user interface must know whether a property may or may not have multiple languages, so the proposal is to add a native boolean attribute 'multiLanguage' to a propertyClass, similar to 'multiple'. This attribute is only meaningful for properties of dataType xs:string.
The values of a property are unchanged: In case a propertyClass specifies "multiple": false and "multiLanguage": false, the values are represented by two nested arrays with a single text value ... without language attribute:
Not all properties of dataType xs:string are multi-language, for example those of type dcterms:identifier. Even more, those must not have multiple languages; Otherwise information is largely obscured.
A user interface must know whether a property may or may not have multiple languages, so the proposal is to add a native boolean attribute 'multiLanguage' to a propertyClass, similar to 'multiple'. This attribute is only meaningful for properties of dataType xs:string.
The values of a property are unchanged: In case a propertyClass specifies "multiple": false and "multiLanguage": false, the values are represented by two nested arrays with a single text value ... without language attribute: