Thank's The problem was in our builder/importer of n3 file in the graph. Sorry for the confusion
-- Jean-Claude Moissinac Le dim. 2 juin 2019 à 22:01, Andy Seaborne <[email protected]> a écrit : > Hi Jean-Claude, > > On 02/06/2019 15:58, Jean-Claude Moissinac wrote: > > Hello > > I've a graph with literals like "2019-9-15T00:00:00Z"^^xsd:dateTime > > Here, the string form is not valid for xsd:dateTime. > > > When I query fuseki for a json format, I get something like: > > { > > "head": { > > "vars": [ "label" , "description" , "datedebut" , "datefin" , "musee" , > > "link" ] > > } , > > "results": { > > "bindings": [ > > { > > "datedebut": { "type": "literal" , "datatype":" > > http://www.w3.org/2001/XMLSchema#dateTime"; , "value": > "2019-5-22T00:00:00Z" > > } > > } , > > ... > > As you can see, the day is now 5 and not 05 and many parsers for Date > > format results as null with such string, which is not conform to the > > xsd:dateTime specification - > > https://www.w3.org/TR/1999/WD-xmlschema-2-19991217/ > > (unless you consider the 5 is an acceptable truncated version of the > > canonical 05 representation) > > It is not acceptable. > > > Have you some idea or solution? > > The data probably has "2019-5-22T00:00:00Z"^^xsd:dateTime in it. > > Fuseki does not fix up in accurate data. > > Andy > > > > > > > -- > > Jean-Claude Moissinac <http://moissinac.wp.mines-telecom.fr/> > > > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > Garanti > > sans virus. www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > >
