#mkotantek: Designing for something in JSON as the source of truth is no different than designing for something in HTML except that it allows for more useful repurposing without requiring as much of a translation layer or removal of presentational elements. Separation of concerns and all that. Designing for the Portable Contacts schema is silly. We agree on that. I'm not sure why you think I like Portable Contacts. I just mentioned that
#mkoPassport uses the Portable Contacts schema as a standard for its unified profile system.
#tantekmko - those same excuses were made for XML, and will be made for whatever replaces JSON in 5-10 years. Meanwhile, HTML+microformats will endure, on the web, in archive.org etc. All programmer formats are ephemeral, and thus a poor source of truth.
#tantekalso, before XML, the same excuses were made for databases/SQL
trendynick_, KartikPrabhu, ChiefRA, tantek and philipashlock joined the channel
#tommorrisso, a simple JS implementation on an individual's site could sort of build a barrier reef to make measures more useful
#tommorrislike, if there were a simple way to mark them up *and* a simple bit of JS that let you click on them to convert them.
#tantekright, emphasis on the *simple way*, which hmeasure was not
#tommorrisinterestingly, Microsoft's F# has a type system that enables these kinds of measures quite nicely. You can declare a value to be in a particular measure type which is orthogonal to its numeric data type (int, float etc.)
#tantekand no one else cared enough to work on it to simplify it
#tantekprobably need some practical publishing examples along with some use-cases to start with
#tommorrisUse case 1: my American friends use these funny Fahrenheit things to talk about the weather. I want my computer to tell me what they are talking about in Celsius without me having to manually work out the conversion in my head. ;-)
#tommorrisMy computer is rather faster at arithmetic than I am.