Hi Matteo, I like your proposal, especially how we extend (or add more details to) the DoW definition. I have one comment on the last additional feature: I am not so sure if the restriction implied in the sentence is necessary. To have FIAps accessible through ANY device would mean that they cannot be OS-, HW-, or in general Client Platform-dependent. I can imagine an Android or iOS app to be a FIAp but then that may not be available from a Linux box or vice-versa. Do we really need this? Or perhaps we can make it weaker a bit? The current sentence also has some typos: * "is ubiquitous accessible" --> "is ubiquitous; i.e., it is accessible" * "interweave" --> "interweaves" Cheers, Roozbeh From: Matteo Melideo <matteo.melideo at eng.it<mailto:matteo.melideo at eng.it>> Reply-To: Matteo Melideo <matteo.melideo at eng.it<mailto:matteo.melideo at eng.it>> Date: Mon, 13 Feb 2012 18:32:27 +0100 To: WP9_fi-ware <fiware-tools at lists.fi-ware.eu<mailto:fiware-tools at lists.fi-ware.eu>>, stefano de panfilis <stefano.depanfilis at eng.it<mailto:stefano.depanfilis at eng.it>> Subject: [Fiware-tools] FIAp definition Dear All, as agreed we have to propose a definition of FIAp necessary first of all for us to better sell what we are doing but also useful for the others. My proposal is, once we agreed, to send this to the FI-WARE coordinator. Given the inputs received (thanks to those who contributed), we arrived to the conclusion that the definition provided in the DoW is enough clear but lacks of some additional characteristics. We have extracted these characteristics from the definitions you provided and here you can find my suggestion: https://forge.fi-ware.eu/plugins/mediawiki/wiki/tools/index.php/Future_Internet_Application. Please feel free to comment and to provide any additional suggestion. We can further discuss this tomorrow during our conference call. Best, Matteo
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy