[Fiware-cloud] Fw: [Fiware-wpl] Next steps regarding the FI-WARE High-level Description (Product Vision)

[Alex Glikson]

FYI, see Juanjo's email below elaborating on the M5 deliverable.

Let's resume our periodic conf calls after we get further clarifications 
regarding the Wiki and the Backlog.

Meanwhile, we can exchange by email some thoughts regarding assets 
applicable to each GE.

Regards,
Alex

----- Forwarded by Alex Glikson/Haifa/IBM on 18/07/2011 09:27 AM -----

From:   Juanjo Hierro <jhierro at tid.es>
To:     "fiware-wpl at lists.fi-ware.eu" <fiware-wpl at lists.fi-ware.eu>, 
"fiware-wpa at lists.fi-ware.eu" <fiware-wpa at lists.fi-ware.eu>
Date:   18/07/2011 01:47 AM
Subject:        [Fiware-wpl] Next steps regarding the FI-WARE High-level 
Description (Product Vision)
Sent by:        fiware-wpl-bounces at lists.fi-ware.eu



Hi all,

  Some of you have asked me about what is expected for the second release 
of the FI-WARE High-level Description (Product Vision) document as 
compared to the first release we have produced.    Let me elaborate here 
on this matter as well as what to do (regarding the FI-WARE High-level 
Description) once we have generated the official deliverable.

  The first thing I would like to point out is that we wish to manage 
publication and maintenance/evolution of this deliverable rather 
differently than in standard european FP7 projects.    It doesn't make 
sense to generate a .pdf, make it publicly available and then, end of the 
story.   Many people simply won't download such a big document.   We will 
also probably need to update some parts of it from time to time ... are we 
going to generate an updated version of it every few weeks in order to 
allow third parties to get access to the most updated version of its 
contents ?   It has no sense.

  How are we going to do then ?    Well, the idea is to create the 
contents of the public Wiki of the project and make it a substantial piece 
of the website.   WPLs and WPAs will have the rights to edit contents of 
the Wiki and will also have the right to assign editing rights to those 
members of their teams they find appropriate.   Translating contents of 
the FI-WARE High-level Description (Product Vision) in a public Wiki help 
to achieve several goals.   In the first place, it will help us to enhance 
our website with a rather useful complete description of what the project 
is about.   Nowadays, many people today have a look at web pages rather 
than downloadable documents when they try to evaluate whether some project 
is of their interest or not.   Therefore, transforming contents of the 
FI-WARE High-level Description into web content (through a Wiki) is 
helpful.   Secondly, having a Wiki would allow each team to introduce 
small and frequent changes (mostly enhancements) in a very straightforward 
manner and all the potential audience will benefit (we don't need to 
notify them they should download a new version of the document because 
they will access the Wiki anytime the wish to access the contents). 
Indeed, our plan is to forward the EC an URL to the Wiki for the first 
official review of this deliverable, whenever it happens.   Indeed, the 
second release of this deliverable should already be just the URL to the 
(updated) Wiki.

  We hope to setup the public Wiki instance for FI-WARE soon (hopefully 
during next week).   We need to setup the infrastructure and, most 
importantly, think about the structure of contents in the Wiki (since it 
won't just include the contents of the FI-WARE High-level Description). 
Your input on this matter is welcome.

  Now, going to the question about the "second release" of the FI-WARE 
High-level Description let me first formulate it the right way: What 
should be new there in the FI-WARE High-level Description content of the 
Wiki by the end of September ?  ... Well ... this is my vision:
We will update some of the contents because we feel like something can be 
better described: in response to some comments we wish to address, because 
we have got the answer to some question that we had just formulated at the 
time the first release was generated (some of them already listed in the 
"Question Marks" section), because we may have decided to add some GE or, 
simply, because we wish to update some part.   I do not expect these will 
be changes that will change radically what we will deliver this week.  It 
will be just the result of applying a number of enhancements over time. 
For those chapters (e.g., IoT Service Enablement) where we have described 
sub-chapters and haven't provided so much information about GEs, I would 
also expect a little bit of more detail about GEs.   The target length of 
the description of a GE would be that followed in chapters like the Cloud 
Hosting or the Data/Context Management chapters.
We will add sections indicating what assets we plan to rely on to develop 
a first working reference implementation of each of the GEs we have 
identified.  I still do not intend to produce too much paperwork here 
because it will not be a matter of "re-editing" existing documentation 
about assets to make it comply with FI-WARE templates or anything like 
that.   We should just include links (URLs) to publicly available and 
already existing documentation about these assets. 

  Based on the the above, I do not expect that we will produce too many 
new pages (i.e., new content in the Wiki) in addition to the existing ones 
already produced for the initial release of the FI-WARE High-level 
Description.  It will be mostly the result of keeping contents of the Wiki 
up to date and include a number of sections dealing with links to 
available documentation on assets we plan to rely on (we will have to 
discuss how to format this in our plenary meeting in September in order to 
decide, e.g., whether we should include a section at the same level as 
"target usage" or "GE description" per each of the GEs or have a single 
section per chapter, describing all the assets and how we plan to 
integrate them)

  Also based on the above, the activities on which we should concentrate 
now and until at least our plenary at mid September are related to 
actually agreeing on what assets we plan to rely on, how we plan to evolve 
and integrate them, and solve some of the questions we have left pending 
for discussion (some of them related to dependencies about chapters). 
Therefore, actual discussions, no paperwork.  This activities should be 
carried out in parallel to definition of the FI-WARE backlog (I will 
elaborate on this in the following email).  Each team is free to organize 
these activities the way they prefer, but I would suggest to define a 
number of Task Forces, each focused on some particular topic and carried 
out through a number of workshops (they may be virtual, based on the usage 
of some kind of confcall+webex facilities) where topics are discussed and 
final decisions/action-points agreed.
 
  Please share contents of this message with your respective teams.

  Cheers,

-- Juanjo

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar 
nuestra política de envío y recepción de correo electrónico en el enlace 
situado más abajo.
This message is intended exclusively for its addressee. We only send and 
receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx[attachment "jhierro.vcf" 
deleted by Alex Glikson/Haifa/IBM] 
_______________________________________________
Fiware-wpl mailing list
Fiware-wpl at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-wpl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20110718/0fe41fc7/attachment.html>