Official response to RDF-ISSUE-129: xsd:integer lossless conversion

Hi Sandro,

This is an official response to RDF-ISSUE-129: xsd:integer lossless
conversion, which is being tracked here:

http://www.w3.org/2011/rdf-wg/track/issues/129

As you know, we had asked you to join the JSON-LD calls to try and
figure out a solution to the issues that you raised concerning the
potential loss of information when converting from RDF to JSON-LD and
back again. Specifically, it is possible to lose accuracy in certain
cases when transforming numbers from one RDF data format to native
implementations of numbers in JSON and back.

The group discussed the issue here:

http://json-ld.org/minutes/2013-06-04/#topic-4

and made the following two resolutions:

RESOLUTION: The default value of the useNativeTypes flag should be set
to 'false' in the JSON-LD API.

The resolution above makes it so that data loss is not possible in the
default case.

RESOLUTION: Add explanatory text to the JSON-LD API specification
explaining the risks of the useNativeTypes flag and how to do proper
conversion to/from native types using the to/from RDF method call.

The resolution above makes it more clear that there are risks to using
the useNativeTypes flag. We also now instruct the developer on how to do
proper conversion to and from native types using the toRDF and fromRDF
algorithms.

http://json-ld.org/spec/CR/json-ld-api/20130822/#data-round-tripping

The group believes that this addresses all of your concerns related to
data round tripping. Please respond to this email as soon as you can to
verify that the changes we made address your concerns adequately.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Meritora - Web payments commercial launch
http://blog.meritora.com/launch/

Received on Tuesday, 13 August 2013 18:13:18 UTC