Whatever approach you take should be easily consumable via Ajax from the current active generation of browsers...
I'm a fan of domain-specific or source-specific representations (JSON or XML, doesn't matter) rather than vague, generic structures. JSON and XML are both quite suitable for containing additional metadata. We could define this metadata in a way that would not conflict with property names on nodes and relationships. Verbosity should be a consideration as well, since adding an XML attribute or JSON object property with the name _neo4J_data_type takes up more wire capacity and memory than _ndt. I must confess to not having worked with the generic Neo REST API that much, since we've implemented our own domain-specific REST API a few levels above raw Neo access. Happy to share our experiences, though. -----Original Message----- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Jim Webber Sent: Tuesday, November 23, 2010 5:18 PM To: Neo4j user discussions Subject: [SPAM] Re: [Neo4j] Datetimes in Neo4j REST Server Hi folks, My concern about this is that we're already taking liberties with the media type application/json. Adding this kind of annotation definitely takes us into very neo4j-specific territory (which might be a good thing). I responded to the ticket, saying that perhaps we should consider a neo4j media type. In that media type we could properly define a set of programmatic types that we support, as well as the hypermedia controls (links, forms) that we'd like to see. However what if we didn't use JSON? The Clojure community are thinking about introducing the notion of URI into the core language. Once that's implemented Ian Robinson, Savas Parastatidis and me along with Stu Halloway are going to design the (hyper)media type application/clojure (which will start life as application/x.clojure) Why is this important? Because Clojure already has a sophisticated type system and sending round Clojure data structures is just as easy as sending around JSON (though admittedly the acronym AJAC does not sound so sexy). Jim _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
