fix bad dct:modified triples

[VladimirAlexiev]

A basic question is "when was this dataset last updated".
This is not shown on the home page, so I tried https://lov.linkeddata.es/dataset/lov/sparql:

prefix dct:  <http://purl.org/dc/terms/>
select * (max(?upd) as ?updated) {
  ?x dct:modified ?upd
}

This returned a string "May 5th, 2023"@en, which is suspect and too far in the past. So I tried this query:

prefix dct:  <http://purl.org/dc/terms/>
select * {
  ?x dct:modified ?upd
} order by desc(?upd) limit 20

There are 4 strings to be fixed to xsd:date. I understand that you probably take them from the source ontologies, but leaving them as is makes it harder to work with dct:modified. There are only a few, and you can fix them with a simple UPDATE ... VALUES

Then come the real last-updated:

• https://lov.linkeddata.es/dataset/lov "2024-09-06"^^xsd:date
• https://lov.linkeddata.es/dataset/lov/vocabs/dvia "2024-08-04"^^xsd:date

Can you explain what was updated in lov after the latest ontology lov/vocabs/dvia?