[Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki

[Leidig, Torsten]

Hi Juanjo,

Now we have at least some guidelines. After looking at some of the existing OpenSpec pages from different chapters I found that no two pages look similar.
So I still recommend to provide a template in order to ensure a common uniform style.

Some comments to the instructions:

You write the target audience are developers of applications or other GEs.

Call me stupid but I still have the feeling that I don't get the meaning of GE concept right.  My understanding is that a GE is describing a general functionality (such as  a "network printing") for which a number of technical realizations can exist (several technical protocols for network printers). So a developer will not use the GE to build applications, he/she rather looks for implementations of the GE which match his/her requirements in terms of non-functional requirements such as cost, interoperability, performance, scalability, SLA, legal, .and so on.

What we actually do in FI-WARE is defining the GE on a level that abstracts from concrete technical realizations. How do we describe GE? I think in terms of their interaction behavior, composition, dependencies, etc. which need to (or may) be provided by a GE implementation. Following this interpretation nobody develops GE, people rather should be able to implement components that conform to GE. The Open Specification must be written in a way to allow developers to implement a GE on its own.

Also no one develops applications on top of GE, applications are developed on top of GE implementations exposing a GE conformant technical interfaces. There could be a catalog of GE implementations that can be used by application developers, which is organized around the GE model. For example as an application developer I look for a implementation of the "Network Printing" enabler, which satisfies my requirement in my situation. Via the catalog (or Marketplace) I can find it.

So an Open Specification for a GE should  only describe what it is used for and how one can interact with it, in a technology neutral way.  It must not prescribe concrete  technical interfaces. Nevertheless, FI-Ware can list or even recommend example technical interfaces in order to harmonize the platform architecture.

In the example of the Apps Repository Enabler I tried to separate the generic part of the GE and the technical part of its implementation by keeping the GE specification neutral and linking to specific technical interfaces (of implementations) at the end of the article.

If this doesn't make sense to you, please take another try to enlighten me.

Regards,
Torsten

PS:
According to the style suggestions you made (italic bold) I recommend to use MediaWiki templates again. I provided and used a couple of them in the Repository pages (e.g. {{Parameter}} ), we could provide more of them. The advantage would be that you can change the rendering and style later without having all people to change every page. 



-----Original Message-----
From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro
Sent: Donnerstag, 2. Februar 2012 09:15
To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: [Fiware-wpa] Guidelines section for Architecture Description deliverable available on the Wiki

Hi all,

   I have published a set of guidelines to be followed for the
development of the Architecture Description deliverable:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Instructions_on_how_to_develop_FI-WARE_Chapter_Architecture_Descriptions

   This how-to will be enriched during the following days, including a
complete example.   However, I believe it contains already enough
detailed instructions about how to proceed.

   Of course, your feedback is welcome.  Answering your concrete
questions may help to enrich the how-to material.

   Cheers,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es
email: jhierro at tid.es
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
   website:  http://www.fi-ware.eu
   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
   twitter:  http://twitter.com/FIware
   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


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
_______________________________________________
Fiware-wpa mailing list
Fiware-wpa at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-wpa