RT @slicknet: New blog post: Using #HTML5 semantic elements today http://bit.ly/i8VIGn (via @dalmaer) // Great post. Thanks! #SemanticWeb
Microsoft Research project #ProBase: http://bit.ly/g7UzJM, http://bit.ly/hwEInC. Data in ProBase not facts, but claims or beliefs. via @RWW
Got 3G/UMTS working on #Cr48 following http://bit.ly/gQ4DEA. Worked out-of-the-box w/ #TMobile DE. Hard-coded carriers: http://bit.ly/gA4muC
@kansandhaus Nice. Thanks! Have you guys considered becoming #CORS enabled (http://www.w3.org/TR/cor…)?
Linus Torvalds: #Android does not violate the #GPL (no quote!): http://bit.ly/eLhEXW (via @greenrobot_de, @heiseopen)
Filed a #Safari bug b/o ISO8601 date parsing. Works in #WebKit, but not in Safari (all 5.0.4). Covered in #ECMAScript5, not in #ECMAScript3.
Yet another bug fix release for mediafragments.js: Object.keys wasnt handled natively by some browsers: http://bit.ly/e0obEK #MediaFragments
@kansandhaus OK, thanks. Makes sense now. Didnt think of that, sorry! Any chance you could get rid of /*comments*/ to have valid #JSON? Thx.
@kansandhaus Hi. Are there (technical?) reasons for escaping forward slashes ‘/‘ in @nytimesi#LinkedDataD#JSONJSON serialization? Thanks!
Thinking #RDF in #JSON (part of #W3C RDF WG charter http://bit.ly/hpBbRV), I think more|less @nytimes JSON http://bit.ly/gibiVo //CC: @webr3
RFC4627 (#JSON, http://bit.ly/fP18n9) says nada about comments. Yet the @nytimes #LinkedData has /*some*/ http://bit.ly/gibiVo @kansandhaus