- From: cdr <_@whats-your.name>
- Date: Thu, 21 Feb 2008 07:57:30 -0500
- To: public-rdf-ruby@w3.org
hi Keith, sorry i didnt mean to imply you sounded like youre sellign a platform. you dont! just that someone who was engineering one would proably want to think about whether they want to necessitate string<>integer casting in their servers in PHP, and the client in Javascript. it may well be completely trivial in terms of performance, in light of other things like runtime of SPARQL queries or even DOM generation.. on '3.000'^^XSD:float. i think its fair game to treat that as a float, and if it gets converted to 3.0, or 2.9999999999999, so be it. the risk you take using floats :) im a bit skeptical on camping out on application/rdf+json MIME type. i could use application/json+rdf, but i know at least Garrett Wilson has his own ideas of how RDF should be serialized in JSON different than either of our own. MIME types arent a URI anwyays. i guess the ultimate solution is the N3 header field explicitly saying the body of the request being RDF in JSON in http://purl/n2/json+rdf, or whatever.. this is not realy ruby specific, maybe its time i subscribe to the TAG lists?
Received on Thursday, 21 February 2008 17:04:22 UTC