Dear Roozbeh, my replies in lined ... Il 16/02/2012 13:08, Farahbod, Roozbeh ha scritto: > Hi Matteo, > > I will try to provide more info but the deadline is too tight and I am not sure, considering the little time I have left in my calendar till Tuesday, how much I will achieve. I believe the Juanjo's example is an overkill for WP9, with little value for us considering that we are the user of most of our components in WP9 and there is only part of it that is exposed to other chapters at the code level (i.e., not through the GUIs). It would have helped of course if we had more time. The definition and identification of the methods we are going to expose can be useful also for us to understand how our components interact each other. > Can't this be done by M12? No, because the deliverables is due now (M9). Let me know when you can provide me this info at the latest. > No one is going to use these information before we (WP9) release the first version of the tools. I know but this is a contractual deadline. > > Last question, shall we provide more detail at the component level or user story level? I suggest component level, but a decision needs to be made group-wise so that we know where we put these; i.e., in separate pages each linked from the main architecture page? Perhaps subgroup leads (Tim for mine) should decide on the structure? At Component level specifying where possible the APIs I hope this answers your questions BR, M. > > 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: Thu, 16 Feb 2012 12:26:56 +0100 > To: WP9_fi-ware<fiware-tools at lists.fi-ware.eu<mailto:fiware-tools at lists.fi-ware.eu>> > Subject: [Fiware-tools] **** URGENT TO DO *** On Architecture... > > Dear All, > I read the contributions on the architecture and I have had the impression that a lot of details are missing and we provided almost the same info of M6. > > I think that it is important to provide some improvements. Specifically, we should try to be (where and when possible) more detailed in the definition of the APIs exposed, in the interactions among the various components internal to Wp9 and in the definition of the interfaces we intend to expose toward third party components (e.g. Testbed or other Chapters). > > Please try to improve this document at the very latest by next 21st of Feb EoB following Juanjo's examples\guidelines (as much as possible): > 1) https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement#Subscribing_to_creation.2Fupdates.2Fdeletion_of_Entities_.28Things_or_IoT_Resources.29 > 2) attached mail > > The deadline is too close as I assume you perfectly know which are the interfaces and the other info requested at least for those components to be exposed at M12. Then, it is just a matter of reporting these into the document in the proper format. > > Anyway, what already written is now going to be integrated into the D2.3 Architecture and reviewed also by the other people to received additional comments and suggestions. > > > Thanks a lot and regards, > > Matteo > > P.S. > Please put your priority on this now. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-tools/attachments/20120216/7c1b1266/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: matteo_melideo.vcf Type: text/x-vcard Size: 354 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-tools/attachments/20120216/7c1b1266/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy