[Fiware-iot] FIWare WP5 description

Farkas, Lorant (NSN - HU/Budapest) lorant.farkas at nsn.com
Wed Jun 8 12:42:51 CEST 2011


Ernő,

(a) The way I see is to ask for access to the other WP projects, or another one would be to look at the contributions other WP-s are submitting to the FI-WARE docman. I will try to ask around from people in the security WP because one of them sits next to me.
(b) 
	(a) 
		Avoid the functionality overlap
		the second example rather than the first
	(b) 
		You see every version in Forge. The first version was created yesterday, the second version today.
		In this document we describe the features of the generic enablers, as well as the architectural components. The interfaces will have open specifications publicised to the usage area projects. We should at least have an idea at this stage what the interface does
	(c)
		Yes, if you have a better proposal feel free to propose and we can change it. At the time I created this there was no comment from anyone
	(d)
		"Then, a number of paragraphs should come describing the GE. This will free style, but we suggest that you highlight the critical attributes of the GE and establish any relevant comparison with existing products along the description. It would be nice to have some figure which helps to understand the description."
	(e)  Example (see page 4 of https://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.4.doc)
*	Middleware component for unified access to distributed and heterogeneous repositories (with particular focus on support for multimedia repositories)
*	Provisioning of metadata format interoperability via schema transformation
*	Abstraction from heterogeneous retrieval paradigms in the underlying data bases and search engines

Br,

Lorant
		

-----Original Message-----
From: ext Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] 
Sent: Wednesday, June 08, 2011 11:42 AM
To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu
Cc: P.Barnaghi at surrey.ac.uk; ignacio.solerjubert at atosresearch.eu; Farkas, Lorant (NSN - HU/Budapest); xavier.aghina at orange-ftgroup.com; stephan.haller at sap.com
Subject: FIWare WP5 description

Thierry, all,

(a) short question: can we have a look at what other WPs are doing?
I think it could be good to see how they deal with this complex process.

Any hint where I can access that?

(b) WP5 Work

I am also not sure what is our main problem to tackle:
(a) Interactions with the other WPs?
    - Purpose of this?
    - Level of Detail (Example: Easy to say I need security, more complex
      to say I need "secure ids" or "distributed policy mng", even 
      harder to say "a cryptographic secured identification schema")
(b) WP internal architecture
     - I see pictures poping up right and left, all different, many not
       agreed on the large scope
     - internal interfaces
       You said you need to understand these internal interfaces.
       - Why? What purpose does it serve in the document?
(c) Concept View
	- You said we need to explain to the UC project what they can expect.
	  This is a highlevel concept view, ideally with some good terms and 
	  simple pictures.
(d) Detailed Enabler View
	- which enablers, which sub-systems, which APIs, wich information model
(e) Unique Selling Points
	- Again something different, and also completely different to present.


Sorry for nasty question, but I am confused.
- Ernö


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20110608/0b5a4441/attachment.html>


More information about the Old-Fiware-iot mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy