On Sunday, January 19, 2014 12:48:36 PM UTC-6, Brian Craft wrote:
That helps, thanks. It's still unclear to me that this is important enough
to worry about. What application or service is hindered by string encoding
a date in JSON? An example would really help. It's not compelling to
I read these self-describing, extensible points in the context of EDN,
which has a syntax/wire format for some types- maps, strings, etc- and also
has an extensibility syntax:
#myapp/Person {:first Fred :last Mertz}
These tagged elements are extensions because they allow values of types
not
That helps, thanks. It's still unclear to me that this is important enough
to worry about. What application or service is hindered by string encoding
a date in JSON? An example would really help. It's not compelling to assert
or imagine some hypothetical application that benefits from knowing a
Hmm, here's a date field that says 090715. I wonder what it means...
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient
finds dates, and other data types, heuristically -- I'm sure Google would
rather not, but that's life on the web.
Google also supports JSON-LD which is a W3 standard for semi-structured and
linked data. JSON-LD defines in-band syntax for dates, all XSD data
types, and arbitrary data types
Regarding Rich's talk (http://www.youtube.com/watch?v=ROor6_NGIWU), can
anyone explain the points he's trying to make about self-describing and
extensible data formats, with the JSON and google examples?
He argues that google couldn't exist if the web depended on out-of-band
schemas. He gives
IIRC in that particular part of the talk he was specifically talking about
(non-self describing) protocol buffers and not JSON.
On Saturday, January 18, 2014 10:00:09 PM UTC+2, Brian Craft wrote:
Regarding Rich's talk (http://www.youtube.com/watch?v=ROor6_NGIWU), can
anyone explain the
Ok, so consider a different system (besides google) that handles the JSON
example. If it has no prior knowledge of the date field, of what use is it
to know that it's a date? What is a situation where a system reading the
JSON needs to know a field is a date, but has no idea what the field is