On Mon, Sep 2, 2013 at 11:56 AM, Denny Vrandečić
denny.vrande...@wikimedia.de wrote:
OK, based on the discussion so far, we will add the data type to the snak in
the external export, and keep the string data value for the URL data type.
That should satisfy all use cases that have been brought
Am 03.09.2013 11:50, schrieb Lydia Pintscher:
On Mon, Sep 2, 2013 at 11:56 AM, Denny Vrandečić
denny.vrande...@wikimedia.de wrote:
OK, based on the discussion so far, we will add the data type to the snak in
the external export, and keep the string data value for the URL data type.
That should
OK, based on the discussion so far, we will add the data type to the snak
in the external export, and keep the string data value for the URL data
type. That should satisfy all use cases that have been brought up.
2013/9/2 Daniel Kinzler daniel.kinz...@wikimedia.de
Am 02.09.2013 00:57,
Am 30.08.2013 17:21, schrieb Denny Vrandečić:
I do see an advantage of stating the property datatype in a snak in the
external JSON representation, and am trying to understand what prevents us
from doing so.
Not much, the SnakSerializer would need access to the PropertyDataTypeLookup
service,
Just following up on some discussion I had with DanielK and Jeroen today on
this, and summarizing it for the mailing list.
I still fail to see what the advantage would be to use the IRI datavalue -
especially when it is basically stripped down to be a string datavalue, as
Jeroen suggests in the
