Currently if the RDF contains a literal value which doesn't agree it's type (e.g. "not a date"^^xsd:date), the API returns HTTP 500 instead of 400. This is because the EasyRdf tries to parse the value only when it's being read and not during the RDF parsing.
zozlak
commented
3 years ago
Currently if the RDF contains a literal value which doesn't agree it's type (e.g.
"not a date"^^xsd:date), the API returns HTTP 500 instead of 400. This is because the EasyRdf tries to parse the value only when it's being read and not during the RDF parsing.It should be handled by capturing errors emitted by the specialized Literal implementations of the EasyRdf (https://github.com/acdh-oeaw/easyrdf/tree/master/lib/Literal)