You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why does Virtuoso change on the fly the GeoSPARQL datatype being used in the data by its own specific datatype? One can see this behavior when DESCRIBE-ing this resource or by simply running this query (see the results):
SELECT *
WHERE {
<http://data.linkedevents.org/location/028f1b02-d121-46f9-bff7-b5e5509a356c/geometry> ?p ?o
}
The text was updated successfully, but these errors were encountered:
This issue seems also related to #195#274#295 and very recently #455. In several of those issues, all commenter have reported that they (must?) use the datatype virtrdf:Geometry. We do expect instead to use the GeoSPARQL datatype gsp:wktLiteral which is later on a pre-condition for some interlinking tools such as SILK to work.
This is really a blocker for us too. This issue is still not resolved in the latest Virtuoso release. @HughWilliams do you know when it will be resolved?
Consider the following triples and load them into a Virtuoso installation:
Regardless of how this data is loaded into Virtuoso, we always get the following behavior which is the transformation of the triple
into
Why does Virtuoso change on the fly the GeoSPARQL datatype being used in the data by its own specific datatype? One can see this behavior when DESCRIBE-ing this resource or by simply running this query (see the results):
The text was updated successfully, but these errors were encountered: