- From: François REMY <francois.remy.dev@outlook.com>
- Date: Mon, 1 Jul 2013 14:50:16 +0200
- To: "Robin Berjon" <robin@w3.org>
- Cc: <public-nextweb@w3.org>
> In other words, let people innovate in apps in small chunks, rather than > require someone take over a large project (or even find unlikely extension > points in an existing one). It's not just the technology that should be > extensible. Okay, this is quite interesting. I didn't see it in that way. I think this is not the exact same thing as web intents, which I really see as a way to launch a new app, but in fact a way to create a GAC (global assembly catalog) of Web Components with a standardized set of interaction contracts among them so that apps can simply rely on existings components instead of shipping their own. In a sense, it looks a lot like COM/ActiveX for web. This is indeed very innovative and interesting, and I can clearly see how this can fit in the spectrum of this CG. The difficulty here is probably not so much defining the meta API (Wish/Intent/...) that handles the communication between the components, but probably the specific contracts because those contracts are really dependent on the specifics of the interaction expected from the web component. Even a text editor would probably surface rather complex contract with things like selection capabilities, getting the text back, context menu actions, tooltips...
Received on Monday, 1 July 2013 12:50:46 UTC