...
will be treated as the same triple and only stored once in your triple store. As a result, when using the procedure described below to upgrade your triple store, you may find that the number of triples in your triple store after the upgrade is lower than the number before the upgrade.
Any code, tools, parsers, utilities, or utility queries that expect to differentiate between these two triples will fail – produce results different than produced previously – RDF 1.1 no longer distinguishes between these two triples. In particular, queries that limit results based on the xsd:string datatype will likely produce larger result sets, as previously untyped triples are now typed as xsd:string internally.
Another way of saying this – any triple loaded into VIVO or Vitro that does not have a type will be typed as xsd:string internally.
...
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.
Code, tools, parsers, and utilities based on RDF 1.0 should not be used with Vitro and VIVO 1.10.
...