Answer with generic info about FIWARE and GEs
"FIWARE is based on main blocks called GEs (Generic Enablers) that you can install and use. The word "Generic" means that they are not specific to any sector but general purpose. Nearly all of the reference implementations that we provide are free to use (I can only think of one exception that we will replace in the future). These GEs are exposed via services (mainly REST interfaces) and anyone can build his own apps that would talk to and use the capabilities of the GEs of his choice.
The wiki (http://wiki.fi-ware.org/) has lots of information but part of the GEs on the wiki are no longer maintained by FIWARE. The up to date reference is the catalogue (http://catalogue.fi-ware.org/enablers). All the components there are alive and supported. The Catalogue concentrates all the pointers to the materials related to a given GE in the wiki or other places without the need to search everywhere. It also shows you the Terms and Conditions in a dedicated tab. I would go to the catalogue and see if the GEs there are useful for you.
There is a free experimentation environment called FIWARE Lab ( https://lab.fi-ware.org/). This environment allows you to deploy GEs and try them. We are progressively incorporating automated deployment facilities to easily install instances of our software on top of your virtual infrastructure on FIWARE Lab. There are quite a few GEri already there for you to deploy with a few clicks. This is the recommended approach vs downloading the software and installing it locally.
Our eLearning web site (FIWARE Academy - http://edu.fi-ware.org/) is also there for you to use. Most of the times you'll get a link to this tool from the catalogue if there is a course for the GE you are browsing on the catalogue.
The typical situation is that you find a number of GEs that are useful for you to resolve concrete problems that you find in your scenario and build an app that talks to them. This happens via REST interfaces. In a mobile app I would normally expect that you would have a back-end with our GEs and the app developed by you on a mobile device would talk to the GEs in the backend.
Summary: if you follow he links from the catalogue you will find the technical info you are looking for.
Best regards,"
extRequest
Major
Answer with generic info about FIWARE and GEs
"FIWARE is based on main blocks called GEs (Generic Enablers) that you can install and use. The word "Generic" means that they are not specific to any sector but general purpose. Nearly all of the reference implementations that we provide are free to use (I can only think of one exception that we will replace in the future). These GEs are exposed via services (mainly REST interfaces) and anyone can build his own apps that would talk to and use the capabilities of the GEs of his choice.
The wiki (http://wiki.fi-ware.org/) has lots of information but part of the GEs on the wiki are no longer maintained by FIWARE. The up to date reference is the catalogue (http://catalogue.fi-ware.org/enablers). All the components there are alive and supported. The Catalogue concentrates all the pointers to the materials related to a given GE in the wiki or other places without the need to search everywhere. It also shows you the Terms and Conditions in a dedicated tab. I would go to the catalogue and see if the GEs there are useful for you.
There is a free experimentation environment called FIWARE Lab ( https://lab.fi-ware.org/). This environment allows you to deploy GEs and try them. We are progressively incorporating automated deployment facilities to easily install instances of our software on top of your virtual infrastructure on FIWARE Lab. There are quite a few GEri already there for you to deploy with a few clicks. This is the recommended approach vs downloading the software and installing it locally.
Our eLearning web site (FIWARE Academy - http://edu.fi-ware.org/) is also there for you to use. Most of the times you'll get a link to this tool from the catalogue if there is a course for the GE you are browsing on the catalogue.
The typical situation is that you find a number of GEs that are useful for you to resolve concrete problems that you find in your scenario and build an app that talks to them. This happens via REST interfaces. In a mobile app I would normally expect that you would have a back-end with our GEs and the app developed by you on a mobile device would talk to the GEs in the backend.
Summary: if you follow he links from the catalogue you will find the technical info you are looking for.
Best regards,"