Is this using TDB as a backend? This is by design in TDB - see Value Canonicalization and TDB Design (http://jena.apache.org/documentation/tdb/value_canonicalization.html and http://jena.apache.org/documentation/tdb/architecture.html) - and not a Fuseki issue but rather a feature of TDB.
Since TDB inlines certain datatypes into the Node IDs in order to speed up common datatype computations it needs to normalize derived datatypes to the appropriate base type. So as in your example anything derived from xsd:integer will be canonicalized to the xsd:integer form. Rob On 7/8/13 8:50 AM, "Enrico Daga" <[email protected]> wrote: >Hi, > >I loaded some data in Fuseki and found some differences in an xsd >datatype. >Follows a test case: > >insert data { > graph <http://example/int/integer> { > _:ex <http://example.org/property/size> "28"^^< >http://www.w3.org/2001/XMLSchema#int> > }} > >Selecting data from the graph <http://example/int/integer> will show the >value as <http://www.w3.org/2001/XMLSchema#integer> instead. > >While this is not a big issue and I could live with that in principle, in >my specific situation (back-end migration to Fuseki), clients relying on >the xsd:int datatype will break (and I want the data to be consistent with >the legacy back-end). > >Any advise? Should I open a bug towards 0.2.8? ;) > >Thank you all, > >Enrico > > >-- >Enrico Daga > >-- >http://www.enridaga.net >skype: enri-pan
