...
As a result, we recommend that input process for VIVO do not include xsd:string datatypes on literals. While they may be correct, and will result in the literal value being typed as xsd:string internally, export processes will not include the xsd:string on output.
In RDF 1.0, a type could not be asserted with a language identifier. In RDF 1.1, a type can be asserted with a language identifier. Untyped input with language identifiers were left as untyped internally in RDF 1.0. In RDF 1.1, untyped input with language identifiers are assumed to have type xsd:langString. Exports from VIVO for triples with language tags will never include the xsd:langString datatype. Literal values with language tags are always assumed to be xsd:langString.
As a result, we recommend that input process for VIVO do not include datatypes on triples with language types. While asserting xsd:langString is correct, and will result in the literal value being typed as xsd:langString internally, export processes will not include the xsd:langString on output.
Code, tools, parsers, utilities based on RDF 1.0 should not be used with Vitro and VIVO 1.10. All code, tools, parsers, and utilities must support RDF 1.1.
...