Closed frodeseverin closed 10 years ago
I can also reproduce this problem
According to http://www.w3.org/TR/xmlschema-2/#gYear “gYear represents a gregorian calendar year. … e.g. lexical 1999 to represent the whole year 1999 …” so it shouldn't be replaced by just one day of the year
Thanks for clarifying. This is exactly what I ment to say.
My post was a little dull on that point, and also a little bloated with details.
maybe someone can find out if this is a virtuoso issue or an ontowiki issue. Either by testing it with MySQL back-end or by loading such data directly to virtuoso.
Just stumbled over this thread (while looking for the cause of a similar problem querying DBpedia): the problem seems to be directly Virtuoso-related. See this mail: https://www.mail-archive.com/virtuoso-users@lists.sourceforge.net/msg04612.html
This is a virtuoso issue (so I will close it here). I've checked this by directly importing gYear data into virtuoso and exporting it afterwards. I could see the same behavior as described by @frodeseverin .
As a workaround I'm also reading the datatype to implement an exception in the site-extensions date helper: https://github.com/AKSW/site.ontowiki/blob/develop/helpers/Date.php
I am on OntoWiki with Virtuoso backend (virtuoso 6.1).
I use xmlshema:date and xmlschema:gYear to represent birth dates and death dates. gYear is used in cases where only the gregorian year is known. However gYear seems to be improperly imported into the database when I use 'Add data to knowledgebase'.
Upon import OntoWiki adds '-01-01T00:00:00+02:00' to the gregorian year, althoug this is not mentioned in the Turtle data source.
In my .ttl files the property is coded such:
The information is stored such after import:
Contrast this with the information for H.C. Andersen:
Source
Imported