Dear Tommaso
FIWARE is providing the so called Generic Enablers. Generic (as opposed to “Specific”) means that they can be applied to no matter what industry, they are general purpose artefacts. You need to see what’s in the catalogue and use those that are useful for you in whatever scenario you have. The best approach is to go to the catalogue (http://catalogue.fiware.org/enablers) and see our current offer. The catalogue concentrates the information of all the available GEs with all the pointers to the manuals, open specs, terms of use, etc.
The definition of the Open Specs and the Manuals associated to each one of the is on the wiki (http://wiki.fiware.org/). The wiki is complex and a bit difficult to navigate at first since it has loads of information. The pages you may need to look for when looking for details are here:
• FIWARE Architecture -> list of technical chapters -> Architecture of Individual GEs in each chapter
• Summary of FIWARE Open Specifications > Open specs summary of Individual GEs in each chapter
• Summary of FIWARE API Open Specifications -> Open specs APIs of Individual GEs in each chapter
• Materializing the FIWARE Vision -> list of technical chapters -> Information of Individual GEs in each chapter (including manuals)
However, these pages also include GEs that are no longer maintained by FIWARE. The safest approach is to go to the catalogue and the catalogue will (hopefully) give you the direct links to the wiki pages that are related to the GE with no need to click though wiki links. The catalogue has the pointers to all the GEs. The GEs have open specs and associated APIs.
In practical terms, you decide to create you application and identify GE implementations that provide functionality that is useful for your app (you are not very explicit but I guess that you want to use FIWARE as the basis to create apps). Your app will talk to the GE implementation via a REST interface.
May I point out that we have a free experimentation environment called FIWARE Lab (https://lab.fiware.org/) where we are progressively making available our GEs with self-deployment facilities.
We also have online eLearning courses (http://edu.fiware.org/)
We have this on our home page (http://www.fiware.org/):
[cid:part6.02040002.07020405@telefonica.com]
If you click on "FIWARE Developers" you get to http://www.fiware.org/developers-entrepreneurs/. There you have a rough explanation of all this I am telling you now plus a few highlights (high level profile GEs) and a few usage examples.
If your query is how to contribute to FIWARE, the answer is different. We intend to open it up to a future open source community but this will happen in coming months, when we create governance rules etc. This is now under internal discussion but it is a formal commitment for the FIWARE partners so it will be done!.
I hope that it helps
Miguel
El 01/04/2015 a las 14:40, Tommaso Solesin escribió:
Hi,
I have come across Fiware a lot in the past few days and I'd like to understand how to get involved.
I am reading through your website but I'd like to get some advice.
Thanks,
Tommaos
extRequest
Major
Dear Tommaso
FIWARE is providing the so called Generic Enablers. Generic (as opposed to “Specific”) means that they can be applied to no matter what industry, they are general purpose artefacts. You need to see what’s in the catalogue and use those that are useful for you in whatever scenario you have. The best approach is to go to the catalogue (http://catalogue.fiware.org/enablers) and see our current offer. The catalogue concentrates the information of all the available GEs with all the pointers to the manuals, open specs, terms of use, etc.
The definition of the Open Specs and the Manuals associated to each one of the is on the wiki (http://wiki.fiware.org/). The wiki is complex and a bit difficult to navigate at first since it has loads of information. The pages you may need to look for when looking for details are here:
• FIWARE Architecture -> list of technical chapters -> Architecture of Individual GEs in each chapter
• Summary of FIWARE Open Specifications > Open specs summary of Individual GEs in each chapter
• Summary of FIWARE API Open Specifications -> Open specs APIs of Individual GEs in each chapter
• Materializing the FIWARE Vision -> list of technical chapters -> Information of Individual GEs in each chapter (including manuals)
However, these pages also include GEs that are no longer maintained by FIWARE. The safest approach is to go to the catalogue and the catalogue will (hopefully) give you the direct links to the wiki pages that are related to the GE with no need to click though wiki links. The catalogue has the pointers to all the GEs. The GEs have open specs and associated APIs.
In practical terms, you decide to create you application and identify GE implementations that provide functionality that is useful for your app (you are not very explicit but I guess that you want to use FIWARE as the basis to create apps). Your app will talk to the GE implementation via a REST interface.
May I point out that we have a free experimentation environment called FIWARE Lab (https://lab.fiware.org/) where we are progressively making available our GEs with self-deployment facilities.
We also have online eLearning courses (http://edu.fiware.org/)
We have this on our home page (http://www.fiware.org/):
[cid:part6.02040002.07020405@telefonica.com]
If you click on "FIWARE Developers" you get to http://www.fiware.org/developers-entrepreneurs/. There you have a rough explanation of all this I am telling you now plus a few highlights (high level profile GEs) and a few usage examples.
If your query is how to contribute to FIWARE, the answer is different. We intend to open it up to a future open source community but this will happen in coming months, when we create governance rules etc. This is now under internal discussion but it is a formal commitment for the FIWARE partners so it will be done!.
I hope that it helps
Miguel
El 01/04/2015 a las 14:40, Tommaso Solesin escribió:
Hi,
I have come across Fiware a lot in the past few days and I'd like to understand how to get involved.
I am reading through your website but I'd like to get some advice.
Thanks,
Tommaos