date format error

[shinysong]

Hi! I'm using blazegraph very well. thank you for this service.

my problem is dateType format error. dateType is output strangely in the query of the blaze graph. (figure 1) I uploaded the rdf file and it was properly set up in the original file. (figure 2) rdf file was made using openrefine-skeleton(extension).

However, if you check it with a query, the format is different. If you check the same file in virtuso, it will be output like "2000-01-01" without this error.

So I thought it was a problem with blazegraph. How can i solve this error?

(figure 1) (figure 2)

[thompsonbry]

You should try curl and see exactly what you are getting back. There might be something happening in the UI with blazegraph. First make sure the actual response is correctly formatted, e.g., when received as RDF/XML.

Bryan

On Tue, Nov 23, 2021 at 2:48 AM shinysong @.***> wrote:

Hi! I'm using blazegraph very well. thank you for this service.

my problem is dateType format error. dateType is output strangely in the query of the blaze graph. (figure 1) I uploaded the rdf file and it was properly set up in the original file. (figure 2) rdf file was made using openrefine-skeleton(extension).

However, if you check it with a query, the format is different. If you check the same file in virtuso, it will be output like "2000-01-01" without this error.

So I thought it was a problem with blazegraph. How can i solve this error?

(figure 1) [image: image] https://user-images.githubusercontent.com/51478604/143010825-0f246a59-bcde-42dc-bda0-1085974f054b.png (figure 2) [image: image] https://user-images.githubusercontent.com/51478604/143010912-725db18c-e10d-479b-939c-79c9a5c7893b.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/blazegraph/database/issues/214, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATW7YFQEZYWMFWWSTZ5SYTUNNWP5ANCNFSM5ITFY6SA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[mschmidt00]

Is that text snippet in Figure 2 your input data?

What stands out is that the triples

... dct:created "20000101"^^<http://www.w3.org/2001/XMLSchema#date>
... modified "20000101"^^<http://www.w3.org/2001/XMLSchema#date>

do not look like valid xsd:date literals, (unless I am missing something here) it should be "2000-01-01", see e.g. https://www.w3schools.com/xml/schema_dtypes_date.asp. What may happen here is that Blazegraph interprets the string wrongly (not sure why it'd end up with 0101-01-01, but it seems like that's what happening), whereas Virtuoso might just have some (non-standard) extensions for invalid xsd:date formats that recognize dates in different formats.