> You start with spreadsheets with columns relating to other columns, and then you view the graph next to it as you go. We are actually starting to crystalize

> You start with spreadsheets with columns relating to other columns, and then you view the graph next to it as you go. We are actually starting to crystalize something like that in our app. It's currently more read- than write-oriented but I think we are getting there. :) > It's funny because behind-the-scenes of spreadsheets there is always big dependency graph that updates cells as changes come through. Yup! Actually one dream that I have for our platform is that we'll build a Excel importer, that will import a fully fledged spreadsheet representation, including formulas that continue working (VBA macros excluded). Our platform does already support the core pieces required for this to work, there are just a ton of nitty gritty details to work out about how this would nicely integrate into the product in a way that isn't too cumbersome for our end-users. > All the specs feel overly-complex too. Like a relic from the XML/SOAP days. Oh, I could rant about that for days... RDF itself is already a bit weird in that aspect (the provide both the possibility to specify a datatype and a language tag, but not both at the same time to specify e.g. "German Markdown"). I don't think any comparable standard today would bake in localization on such a fundamental layer.