JervenBolleman opened a new issue, #3990: URL: https://github.com/apache/jena/issues/3990
### Version 6.1.0 ### What happened? Since upgrading to version 6.1.0 from 4.10.0 riot --validate has started to fail for the file available at https://ftp.uniprot.org/pub/databases/uniprot/current_release/rdf/void.rdf With a minimal reproducer to validate ```rdfxml <?xml version='1.0' encoding='UTF-8'?> <rdf:RDF xmlns="http://purl.uniprot.org/core/"; xmlns:dcat="http://www.w3.org/ns/dcat#"; xmlns:dcterms="http://purl.org/dc/terms/"; xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:xsd="http://www.w3.org/2001/XMLSchema#";> <rdf:Description rdf:about="http://purl.uniprot.org/void#UniProtDescription_2026_01";> <dcterms:title rdf:datatype="http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"; xml:lang="en">Void description of the UniProt datasets</dcterms:title> </rdf:Description> </rdf:RDF> ``` This validates with release 4.10.0 and not with 6.1.0. Removing the explicit datatype langString allows the lang attribute to be picked up correctly in 6.1.0 ```rdfxml <?xml version='1.0' encoding='UTF-8'?> <rdf:RDF xmlns="http://purl.uniprot.org/core/"; xmlns:dcat="http://www.w3.org/ns/dcat#"; xmlns:dcterms="http://purl.org/dc/terms/"; xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:xsd="http://www.w3.org/2001/XMLSchema#";> <rdf:Description rdf:about="http://purl.uniprot.org/void#UniProtDescription_2026_01";> <dcterms:title xml:lang="en">Void description of the UniProt datasets</dcterms:title> </rdf:Description> </rdf:RDF> ``` ### Relevant output and stacktrace ```shell ``` ### Are you interested in making a pull request? None -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
