Comment by miguel.carrillopacheco@telefonica.com :
Dear Mr. Gagnon,
Thanks for contacting us and for your interest in our initiative. FIWARE
as such is a set of components called Generic Enablers (GEs). FIWARE is
providing the so-called Generic Enablers. Generic (as opposed to
“Specific”) means that they can be applied to no matter what sector,
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 general case is that each GE exposes an API interface that you
can use to avail of the GE's functionality.
So the best approach to get familiar with our technologies is to go to
the catalogue (http://catalogue.fiware.org/enablers) and see our current
offering. 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.
For instance, together with the catalogue you may want to look at the
summary of Release 4 here (note that R5 is being released at the moment
and in many place you'll see R5 components already):
you may find our Tour Guide friendly and easy to understand if you are a
developer:
More resources:
However, these wiki pages sometimes 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. 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/_) and a Q&A platform
(http://ask.fiware.org). We also tend to answer questions on specific
components (that is is to say, GEs) in StackOverflow.
Some reading of the pages on www.fiware.org that you've already visited
may help in general and provide extra pointer.
I hope that this is of help.
Best regards,
Miguel Carrillo
El 19/10/2016 a las 18:05, Kolton Gagnon escribió:
> Hi FIWARE,
>
> Our contact at UNB (University of New Brunswick) mentioned FIWARE
> yesterday during a conversation and I took some time to review your
> website. I have a few questions.
>
> How does FIWARE work?
> What are the benefits FIWARE can provide to a startup company?
>
> Looking forward to your response.
>
> Regards,
> Kolton Gagnon <http://ca.linkedin.com/in/koltongagnon/>
> CTO / Lead Developer at SimpTek Technologies <http://www.simptekinc.com/>
> Kolton.Gagnon@SimpTekInc.com <Kolton.Gagnon@SimpTekInc.com>
> Facebook <https://www.facebook.com/simptek> | Twitter
> <https://twitter.com/SimpTek>
>
>
> Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
> Please, send your messages using the new domain (Fiware-general-help@lists.fiware.org) instead of the old one.
>
Comment by miguel.carrillopacheco@telefonica.com :
Dear Mr. Gagnon,
Thanks for contacting us and for your interest in our initiative. FIWARE
as such is a set of components called Generic Enablers (GEs). FIWARE is
providing the so-called Generic Enablers. Generic (as opposed to
“Specific”) means that they can be applied to no matter what sector,
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 general case is that each GE exposes an API interface that you
can use to avail of the GE's functionality.
So the best approach to get familiar with our technologies is to go to
the catalogue (http://catalogue.fiware.org/enablers) and see our current
offering. 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.
For instance, together with the catalogue you may want to look at the
summary of Release 4 here (note that R5 is being released at the moment
and in many place you'll see R5 components already):
you may find our Tour Guide friendly and easy to understand if you are a
developer:
More resources:
<http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture>
-> list of technical chapters -> Architecture of Individual GEs in
each chapter
<http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision>
-> list of technical chapters -> Information of Individual GEs in
each chapter (including manuals)
However, these wiki pages sometimes 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. 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/_) and a Q&A platform
(http://ask.fiware.org). We also tend to answer questions on specific
components (that is is to say, GEs) in StackOverflow.
Some reading of the pages on www.fiware.org that you've already visited
may help in general and provide extra pointer.
I hope that this is of help.
Best regards,
Miguel Carrillo
El 19/10/2016 a las 18:05, Kolton Gagnon escribió:
> Hi FIWARE,
>
> Our contact at UNB (University of New Brunswick) mentioned FIWARE
> yesterday during a conversation and I took some time to review your
> website. I have a few questions.
>
> How does FIWARE work?
> What are the benefits FIWARE can provide to a startup company?
>
> Looking forward to your response.
>
> Regards,
> Kolton Gagnon <http://ca.linkedin.com/in/koltongagnon/>
> CTO / Lead Developer at SimpTek Technologies <http://www.simptekinc.com/>
> Kolton.Gagnon@SimpTekInc.com <Kolton.Gagnon@SimpTekInc.com>
> Facebook <https://www.facebook.com/simptek> | Twitter
> <https://twitter.com/SimpTek>
>
>
> Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
> Please, send your messages using the new domain (Fiware-general-help@lists.fiware.org) instead of the old one.
>