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 for?
On Saturday, January 18, 2014 1:27:31 PM UTC-8, Jonas wrote: > > 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 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 as an example of such a schema a JSON encoding where an >> out-of-band agreement is made that field names with substring "date" refer >> to string-encoded dates. >> >> However, this is exactly the sort of thing google does. It finds dates, >> and other data types, heuristically, and not through the formats of the web >> being self-describing or extensible. >> >> >> -- -- 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 with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
