OyvindLGjesdal opened a new issue, #1929:
URL: https://github.com/apache/jena/issues/1929

   ### Version
   
   4.8.0
   
   ### Feature
   
   We have data created by an external RDF-editor , which can store data which 
gives warnings in riot. Often you don't want to fix it in the RDF file, but in 
the source system, where it was exported from. This would be made easier by 
having context available when validating the data.
   
   some example outputs we get when validating
   ```
   $JENA_HOME/bin/riot --validate file.rdf-xml.owl 
   ```
   
   ```
   18:13:09 WARN  riot            :: Lexical form '190-01-01' not valid for 
datatype XSD date
   18:13:10 WARN  riot            :: Lexical form '5,356890' not valid for 
datatype XSD double
   18:12:58 WARN  riot            :: Lexical form '1831-04-1831' not valid for 
datatype XSD gYear
   18:12:58 WARN  riot            :: Lexical form '19.jan.1921' not valid for 
datatype XSD gYear
   ```
   current version used for testing:
   ```
   $JENA_HOME/bin/riot --version
   Jena:       VERSION: 4.8.0
   Jena:       BUILD_DATE: 2023-04-20T08:38:51Z
   ```
   
   I made a small XSLT script for getting human readable output on our data  
for us to look up and correct, which now gives output on our data like:
   
   > subject https://marcus.uib.no/instance/photograph/ubb-bs-fol-00992 
contains a bad value: "193-01-30" for datatype xs:date  in predicate: 
ubbont:madeBefore
   
   This solves our internal issue of having a simple way to look up data with 
warnings to correct, but I thought it would also be useful if possible to have 
something similar available from riot?
   
   ### Are you interested in contributing a solution yourself?
   
   Yes


-- 
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]

Reply via email to