That would be even better. A static document with an URL. Then you "swipe" the URL from your phone/pad to the baking machine, which fetches the URL and reads th

That would be even better. A static document with an URL. Then you "swipe" the URL from your phone/pad to the baking machine, which fetches the URL and reads the marked up recipe. You then confirm the ingredients on the baking machine, and it starts baking I however want both "apps" and semantic "documents". Launching an app by typing an URL is powerful. And on Android you can now add an web app to the home screen. We might not want the recipe to have the same capabilities as the "app". Maybe the apps should be closer to the OS, and "documents" opened in a reader app (browser). One problem with the "semantic web" is that the added markup feel alien and too verbose. It was designed to be used with web page builder apps. But I and many others still prefer to code the HTML manually, with the help of a powerful editor (with autocomplete and macros). "Structured data" gets too hard to read by source. An idea is to replace the many span and div elements with actual semantic elements. In another post I ranted that nothing had really changed for "documents" on the web in the last 20 years. We are practically standing still, without any innovation. Probably due to browsers being overly complex and hard to develop. I think the time is ripe for a "document only" web browser, and we can start innovating again! For example, the enterpise market is still using word documents, some use alternatives like Google docs. But web "documents" would be far more powerful. Instead of e-mailing files, you should just share a URL. I'm currently working on an Editor for making web documents (but also for making web apps). I've put a lot of thoughts to how enterprise can use my editor to make web documents instead of word files and PDF's. Almost everyone are using the web today, but very few people actually make web "documents".