# FiLiP
[](https://rwth-ebc.github.io/FiLiP/master/pylint/pylint.html)
[](https://rwth-ebc.github.io/FiLiP/master/docs/index.html)
[](https://rwth-ebc.github.io/FiLiP/master/coverage)
[](https://opensource.org/licenses/BSD-3-Clause)
[](https://rwth-ebc.github.io/FiLiP/master/build/build.svg)
[](https://doi.org/10.21105/joss.06953)
FiLiP (Fiware Library for Python) is a python software development kit (SDK) for
accelerating the development of web services that use Fiware's Generic
Enablers (GEs) as backend.
It is mainly based on the [Pydantic](https://pydantic-docs.helpmanual.io/)
package which is a sophisticated library for data validation and settings
management using python type annotations.
Pydantic enforces type hints at runtime, and provides user friendly errors
when data is invalid.
We mainly use the Pydantic model to build our own data model structure required
for efficient data model parsing and validation and interaction with FIWARE
services' RestAPIs.
For API interaction, FiLiP relies on the well-known
[requests](https://docs.python-requests.org/en/latest/) package.
It is important to understand that we do not in any way restrict any
features of requests.
Furthermore, FiLiP is designed to help with the fast development of FIWARE-based
applications and avoid hundreds of lines of boilerplate, but it cannot
substitute learning the basic concepts behind the used FIWARE components.
## General Motivation
Why implement a client library when clients can be auto-generated
from openapi documentation?
A general prerequisite to do so is that the documentation is in depth and of
good quality.
While FIWARE generally provides
[openapi documentation](https://github.com/FIWARE/specifications),
here are some thoughts on the challenges of auto-generating client code from
these documents:
- Auto-generated code tends to become rather bulky and its quality strongly
depends on the provided input data.
- Manipulating generated code can result in a big hassle for maintenance if
additional features need to be integrated.
- The underlying NGSI (Next Generation Service Interface) for FIWARE is a
rather generic specification.
Hence, generated models may also be of generic types as lists
and dicts in Python. So there is no real benefit.
Furthermore, there is no chance for reasonable validation and error handling.
## Getting started
The following section shortly describes how to use the library.
### Prerequisites
Since FiLiP is designed as a client library, it requires a server that provides
the target Service-APIs.
Hence, if you do not yet have a running instance of a FIWARE based platform,
using docker is the most convenient way to set it up.
Please check [here](https://github.com/N5GEH/n5geh.platform) for a tutorial
on this.
If this is not an option for you, FIWARE also provides a testing server.
You can register for a testing account
[here](https://www.fiware.org/developers/fiware-lab/).
> **Note**: FiLiP is now compatible to [Pydantic V2](https://docs.pydantic.dev/latest/migration/). If your program still require Pydantic V1.x for some reason, please use release [v0.2.5](https://github.com/RWTH-EBC/FiLiP/releases/tag/v0.2.5) or earlier version of FiLiP. Besides, we recommended to set `pydantic~=1.10` in the `requirements.txt`, otherwise Pydantic V2 might still be installed.
### Installation
The easiest way to install the library is via pip:
````
pip install -U filip
````
If you want to benefit from the latest changes, use the following command
(This will install the current master branch from this repository):
```
pip install -U git+git://github.com/RWTH-EBC/filip
```
> **Note**: For local development, you can install the library in editable mode with the following command:
> ````
> pip install -e .
> ````
#### Install semantics module (optional)
If you want to use the optional [semantics module](filip/semantics), use the following command (This will install the libraries that only required for the semantics module):
````
pip install -U filip[semantics]
````
### Introduction to FIWARE
The following section introduces FIWARE. If you are already familiar with
FIWARE, you can skip this section and go straight to [Getting Started](#getting-started).
#### What is FIWARE?
FIWARE is a framework of open-source cloud platform components, created
to facilitate the development of smart solutions within various application
domains.
At the moment, the FIWARE
[catalogue](https://www.fiware.org/developers/catalogue/) contains over 30
interoperable software modules, so-called Generic Enablers
(GE) for developing and providing customized IoT platform solutions.
To get familiar with the APIs of the different modules we highly recommend
checking the
[step-by-step tutorial](https://fiware-tutorials.readthedocs.io/en/latest/).
It provides a good overview on FIWARE and its basic usage.
Whereas the tutorial helps to understand most of the general concepts,
for a deep dive, where you can learn about the components in more detail,
FIWARE also offers extended lessons through their
[academy](https://fiware-academy.readthedocs.io/en/latest/index.html/).
However, usually one only requires a small set of components.
Hence, we recommend using the cited pages only as needed.
#### How to set up a FIWARE platform?
The easiest way to set up a FIWARE platform is by using docker as all GEs are
open-source and distributed as docker containers on dockerhub.
However, as mentioned before, for most use cases only a subset of GEs is required.
Hence, we wrote a small [tutorial](https://github.com/N5GEH/n5geh.platform)
explaining how to set up a platform suited for most use cases within the energy
domain.
#### FIWARE GEs covered by FiLiP
FiLiP is a library developed on demand.
Hence, we do not aim to cover the APIs of all GEs that are included in the
[catalogue](https://www.fiware.org/developers/catalogue/).
This would mean an unnecessary development overhead.
Therefore, FiLiP currently only covers the APIs of the following GEs:
- NGSIv2 Context Broker for managing context data. We use its
reference implementation ORION for testing.
- [documentation](https://fiware-orion.readthedocs.io/en/master/)
- [github](https://github.com/telefonicaid/fiware-orion)
- [swagger](https://swagger.lab.fiware.org/)
- [NGSI v2 specifications](https://github.com/FIWARE/specifications/tree/master/OpenAPI/ngsiv2)
- NGSI-LD Context Broker for managing context data with Linked Data concept. The functionalities that FiLiP supports are closely aligned with the specification **_NGSI-LD V1.3.1_**, which is according to the FIWARE [catalogue](https://github.com/FIWARE/catalogue#core-context-broker-components) the latest spec version that has been implemented by all three brokers (Orion-LD, Scorpio, and Stellio). We currently use Orion-LD for testing.
- [github](https://github.com/FIWARE/context.Orion-LD)
- [swagger](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/FIWARE/specifications/master/OpenAPI/ngsi-ld/full_api.json#/)
> **Note**: `-experimental` flag need to be set for Orion-LD Context Broker to enable the full functionality. Check this [issue](https://github.com/FIWARE/context.Orion-LD/issues/1648) for more information
- IoT-Agents for managing IoT Devices. IoT agents are implemented using
the FIWARE IoT Agent Node Lib as a common framework.
- [documentation](https://iotagent-node-lib.readthedocs.io/en/latest/)
- [github](https://github.com/telefonicaid/iotagent-node-lib)
- IoT-Agent-JSON for managing devices using a JSON message payload protocol
format.
- [documentation](https://fiware-iotagent-json.readthedocs.io/en/latest/)
- [github](https://github.com/telefonicaid/iotagent-json)
- [apiary](https://telefonicaiotiotagents.docs.apiary.io/)
(*partly deprecated*)
Example payload:
{
"humidity": "45%",
"temperature": "23",
"luminosity": "1570"
}
- IoT-Agent-Ultralight for managing devices using an Ultralight 2.0 message
payload protocol.
- [documentation](https://fiware-iotagent-ul.readthedocs.io/en/latest/)
- [github](https://github.com/telefonicaid/iotagent-ul)
- [apiary](https://telefonicaiotiotagents.docs.apiary.io/)
(*partly deprecated*)
Example payload:
humidity|45%|temperature|23|luminosity|1570
- QuantumLeap for the management of time series data
- [documentation](https://quantumleap.readthedocs.io/en/latest/)
- [github](https://github.com/FIWARE-GEs/quantum-leap)
- [swagger](https://app.swaggerhub.com/apis/smartsdk/ngsi-tsdb/0.8.3)
## Structure of FiLiP
## Documentation
We are still working on the documentation.
You can find our current documentation
[here](https://rwth-ebc.github.io/FiLiP/master/docs/index.html).
## Running examples
Once you have installed the library, you can check the [examples](/examples)
to learn how to use the different components.
Currently, we provide basic examples for the usage of FiLiP for the FIWARE
GEs mentioned above.
We suggest to start in the right order to first understand the
configuration of clients.
Afterwards, you can start modelling context data and interacting with the context
broker and use its functionalities before you learn how to connect
IoT Devices and store historic data.
## Testing
We use unittests to write our test cases.
To test the source code of the library in our CI workflow, the CI
executes all tests located in the `tests`-directory and prefixed with `test_` .
## How to contribute
Please see our [contribution guide](./CONTRIBUTING.md) for more details on
how you can contribute to this project.
## Authors
* [Thomas Storek](https://github.com/tstorek)
* [Junsong Du](https://www.ebc.eonerc.rwth-aachen.de/cms/E-ON-ERC-EBC/Das-Institut/Mitarbeiter/Digitale-Energie-Quartiere/~trcib/Du-Junsong/lidx/1/) (corresponding)
* [Saira Bano](https://www.ebc.eonerc.rwth-aachen.de/cms/E-ON-ERC-EBC/Das-Institut/Mitarbeiter/Systemadministration/~ohhca/Bano-Saira/)
* [Sebastian Blechmann](https://www.ebc.eonerc.rwth-aachen.de/cms/E-ON-ERC-EBC/Das-Institut/Mitarbeiter/Team2/~carjd/Blechmann-Sebastian/)
## Alumni
* Jeff Reding
* Felix Rehmann
* Daniel Nikolay
## References
We presented or applied the library in the following publications:
- S. Blechmann, I. Sowa, M. H. Schraven, R. Streblow, D. Müller & A. Monti. Open source platform application for smart building and smart grid controls. Automation in Construction 145 (2023), 104622. ISSN: 0926-5805. https://doi.org/10.1016/j.autcon.2022.104622
- Haghgoo, M., Dognini, A., Storek, T., Plamanescu, R, Rahe, U.,
Gheorghe, S, Albu, M., Monti, A., Müller, D. (2021) A cloud-based service-oriented architecture to unlock smart energy services
https://www.doi.org/10.1186/s42162-021-00143-x
- Baranski, M., Storek, T. P. B., Kümpel, A., Blechmann, S., Streblow, R.,
Müller, D. et al.,
(2020). National 5G Energy Hub : Application of the Open-Source Cloud Platform
FIWARE for Future Energy Management Systems.
https://doi.org/10.18154/RWTH-2020-07876
- T. Storek, J. Lohmöller, A. Kümpel, M. Baranski & D. Müller (2019).
Application of the open-source cloud platform FIWARE for future building
energy management systems.
Journal of Physics:
Conference Series, 1343, 12063. https://doi.org/10.1088/1742-6596/1343/1/012063
## License
This project is licensed under the BSD License - see the [LICENSE](LICENSE) file for details.
## Copyright
<a href="https://www.ebc.eonerc.rwth-aachen.de/"> <img alt="EBC" src="https://www.ebc.eonerc.rwth-aachen.de/global/show_picture.asp?id=aaaaaaaaaakevlz" height="100"> </a>
2021-2024, RWTH Aachen University, E.ON Energy Research Center, Institute for Energy
Efficient Buildings and Indoor Climate
[Institute for Energy Efficient Buildings and Indoor Climate (EBC)](https://www.ebc.eonerc.rwth-aachen.de)
[E.ON Energy Research Center (E.ON ERC)](https://www.eonerc.rwth-aachen.de)
[RWTH University Aachen, Germany](https://www.rwth-aachen.de)
## Disclaimer
This project is part of the cooperation between the RWTH Aachen University and
the Research Centre Jülich.
<a href="https://www.jara.org/de/forschung/jara-energy"> <img alt="JARA
ENERGY" src="https://raw.githubusercontent.com/RWTH-EBC/FiLiP/master/docs/logos/LogoJARAEnergy.jpg" height="100"> </a>
## Related projects
<a href="https://n5geh.de/"> <img alt="National 5G Energy Hub"
src="https://avatars.githubusercontent.com/u/43948851?s=200&v=4" height="100"></a>
<a href="https://fismep.de/"> <img alt="FISMEP"
src="https://raw.githubusercontent.com/RWTH-EBC/FiLiP/master/docs/logos/FISMEP.png"
height="100"></a>
## Acknowledgments
We gratefully acknowledge the financial support of the Federal Ministry <br />
for Economic Affairs and Climate Action (BMWK), promotional references
03ET1495A, 03ET1551A, 0350018A, 03ET1561B.
<a href="https://www.bmwi.de/Navigation/EN/Home/home.html"> <img alt="BMWK"
src="https://raw.githubusercontent.com/RWTH-EBC/FiLiP/master/docs/logos/bmwi_logo_en.png" height="100"> </a>
This project has received funding in the framework of the joint programming initiative ERA-Net Smart Grids Plus, with support from the European Union’s Horizon 2020 research and innovation programme.
<a href="https://www.eranet-smartgridsplus.eu/"> <img alt="ERANET"
src="https://fismep.de/wp-content/uploads/2017/09/SmartGridsPlus_rgb-300x55.jpg" height="100"> </a>
Raw data
{
"_id": null,
"home_page": "https://github.com/RWTH-EBC/filip",
"name": "filip",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "iot, fiware, semantic",
"author": "RWTH Aachen University, E.ON Energy Research Center, Institute of Energy Efficient Buildings and Indoor Climate",
"author_email": "junsong.du@eonerc.rwth-aachen.de",
"download_url": "https://files.pythonhosted.org/packages/cd/15/7e738b7c51aa68fd37ff3ca5b0dd469e79645259f7a0403fc8c322e65cd4/filip-0.6.0.tar.gz",
"platform": null,
"description": "\n\n# FiLiP\n\n[](https://rwth-ebc.github.io/FiLiP/master/pylint/pylint.html)\n[](https://rwth-ebc.github.io/FiLiP/master/docs/index.html)\n[](https://rwth-ebc.github.io/FiLiP/master/coverage)\n[](https://opensource.org/licenses/BSD-3-Clause)\n[](https://rwth-ebc.github.io/FiLiP/master/build/build.svg)\n[](https://doi.org/10.21105/joss.06953)\n\nFiLiP (Fiware Library for Python) is a python software development kit (SDK) for \naccelerating the development of web services that use Fiware's Generic \nEnablers (GEs) as backend.\n\nIt is mainly based on the [Pydantic](https://pydantic-docs.helpmanual.io/) \npackage which is a sophisticated library for data validation and settings \nmanagement using python type annotations.\nPydantic enforces type hints at runtime, and provides user friendly errors \nwhen data is invalid.\nWe mainly use the Pydantic model to build our own data model structure required \nfor efficient data model parsing and validation and interaction with FIWARE \nservices' RestAPIs. \n\nFor API interaction, FiLiP relies on the well-known \n[requests](https://docs.python-requests.org/en/latest/) package. \nIt is important to understand that we do not in any way restrict any \nfeatures of requests.\n\nFurthermore, FiLiP is designed to help with the fast development of FIWARE-based \napplications and avoid hundreds of lines of boilerplate, but it cannot \nsubstitute learning the basic concepts behind the used FIWARE components.\n\n## General Motivation\n\nWhy implement a client library when clients can be auto-generated \nfrom openapi documentation? \nA general prerequisite to do so is that the documentation is in depth and of \ngood quality. \nWhile FIWARE generally provides \n[openapi documentation](https://github.com/FIWARE/specifications),\nhere are some thoughts on the challenges of auto-generating client code from \nthese documents:\n\n- Auto-generated code tends to become rather bulky and its quality strongly\n depends on the provided input data.\n- Manipulating generated code can result in a big hassle for maintenance if \n additional features need to be integrated.\n- The underlying NGSI (Next Generation Service Interface) for FIWARE is a\n rather generic specification.\n Hence, generated models may also be of generic types as lists\n and dicts in Python. So there is no real benefit.\n Furthermore, there is no chance for reasonable validation and error handling.\n\n## Getting started\n\nThe following section shortly describes how to use the library.\n\n### Prerequisites\n\nSince FiLiP is designed as a client library, it requires a server that provides \nthe target Service-APIs.\nHence, if you do not yet have a running instance of a FIWARE based platform, \nusing docker is the most convenient way to set it up. \nPlease check [here](https://github.com/N5GEH/n5geh.platform) for a tutorial \non this.\nIf this is not an option for you, FIWARE also provides a testing server.\nYou can register for a testing account \n[here](https://www.fiware.org/developers/fiware-lab/).\n> **Note**: FiLiP is now compatible to [Pydantic V2](https://docs.pydantic.dev/latest/migration/). If your program still require Pydantic V1.x for some reason, please use release [v0.2.5](https://github.com/RWTH-EBC/FiLiP/releases/tag/v0.2.5) or earlier version of FiLiP. Besides, we recommended to set `pydantic~=1.10` in the `requirements.txt`, otherwise Pydantic V2 might still be installed.\n\n### Installation\n\nThe easiest way to install the library is via pip:\n\n````\npip install -U filip\n````\n\nIf you want to benefit from the latest changes, use the following command \n(This will install the current master branch from this repository):\n\n```\npip install -U git+git://github.com/RWTH-EBC/filip\n```\n\n> **Note**: For local development, you can install the library in editable mode with the following command:\n> ````\n> pip install -e .\n> ````\n\n#### Install semantics module (optional)\n\nIf you want to use the optional [semantics module](filip/semantics), use the following command (This will install the libraries that only required for the semantics module):\n````\npip install -U filip[semantics]\n````\n\n### Introduction to FIWARE\n\nThe following section introduces FIWARE. If you are already familiar with \nFIWARE, you can skip this section and go straight to [Getting Started](#getting-started).\n\n#### What is FIWARE?\n\nFIWARE is a framework of open-source cloud platform components, created \nto facilitate the development of smart solutions within various application \ndomains. \nAt the moment, the FIWARE \n[catalogue](https://www.fiware.org/developers/catalogue/) contains over 30 \ninteroperable software modules, so-called Generic Enablers \n(GE) for developing and providing customized IoT platform solutions.\n\nTo get familiar with the APIs of the different modules we highly recommend \nchecking the \n[step-by-step tutorial](https://fiware-tutorials.readthedocs.io/en/latest/). \nIt provides a good overview on FIWARE and its basic usage.\nWhereas the tutorial helps to understand most of the general concepts, \nfor a deep dive, where you can learn about the components in more detail, \nFIWARE also offers extended lessons through their \n[academy](https://fiware-academy.readthedocs.io/en/latest/index.html/).\n\nHowever, usually one only requires a small set of components. \nHence, we recommend using the cited pages only as needed.\n\n#### How to set up a FIWARE platform?\n\nThe easiest way to set up a FIWARE platform is by using docker as all GEs are \nopen-source and distributed as docker containers on dockerhub.\n\nHowever, as mentioned before, for most use cases only a subset of GEs is required.\nHence, we wrote a small [tutorial](https://github.com/N5GEH/n5geh.platform) \nexplaining how to set up a platform suited for most use cases within the energy \ndomain. \n\n#### FIWARE GEs covered by FiLiP\n\nFiLiP is a library developed on demand.\nHence, we do not aim to cover the APIs of all GEs that are included in the \n[catalogue](https://www.fiware.org/developers/catalogue/). \nThis would mean an unnecessary development overhead. \nTherefore, FiLiP currently only covers the APIs of the following GEs:\n\n- NGSIv2 Context Broker for managing context data. We use its \n reference implementation ORION for testing.\n - [documentation](https://fiware-orion.readthedocs.io/en/master/)\n - [github](https://github.com/telefonicaid/fiware-orion)\n - [swagger](https://swagger.lab.fiware.org/)\n - [NGSI v2 specifications](https://github.com/FIWARE/specifications/tree/master/OpenAPI/ngsiv2)\n\n- NGSI-LD Context Broker for managing context data with Linked Data concept. The functionalities that FiLiP supports are closely aligned with the specification **_NGSI-LD V1.3.1_**, which is according to the FIWARE [catalogue](https://github.com/FIWARE/catalogue#core-context-broker-components) the latest spec version that has been implemented by all three brokers (Orion-LD, Scorpio, and Stellio). We currently use Orion-LD for testing.\n - [github](https://github.com/FIWARE/context.Orion-LD)\n - [swagger](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/FIWARE/specifications/master/OpenAPI/ngsi-ld/full_api.json#/)\n > **Note**: `-experimental` flag need to be set for Orion-LD Context Broker to enable the full functionality. Check this [issue](https://github.com/FIWARE/context.Orion-LD/issues/1648) for more information\n \n- IoT-Agents for managing IoT Devices. IoT agents are implemented using \n the FIWARE IoT Agent Node Lib as a common framework.\n - [documentation](https://iotagent-node-lib.readthedocs.io/en/latest/)\n - [github](https://github.com/telefonicaid/iotagent-node-lib)\n\n \n- IoT-Agent-JSON for managing devices using a JSON message payload protocol \n format. \n - [documentation](https://fiware-iotagent-json.readthedocs.io/en/latest/)\n - [github](https://github.com/telefonicaid/iotagent-json)\n - [apiary](https://telefonicaiotiotagents.docs.apiary.io/) \n (*partly deprecated*)\n\n Example payload:\n \n {\n \"humidity\": \"45%\",\n \"temperature\": \"23\",\n \"luminosity\": \"1570\"\n } \n\n- IoT-Agent-Ultralight for managing devices using an Ultralight 2.0 message \n payload protocol.\n \n - [documentation](https://fiware-iotagent-ul.readthedocs.io/en/latest/)\n - [github](https://github.com/telefonicaid/iotagent-ul)\n - [apiary](https://telefonicaiotiotagents.docs.apiary.io/) \n (*partly deprecated*)\n \n Example payload:\n \n humidity|45%|temperature|23|luminosity|1570\n \n- QuantumLeap for the management of time series data\n \n - [documentation](https://quantumleap.readthedocs.io/en/latest/)\n - [github](https://github.com/FIWARE-GEs/quantum-leap)\n - [swagger](https://app.swaggerhub.com/apis/smartsdk/ngsi-tsdb/0.8.3)\n\n## Structure of FiLiP\n\n\n\n\n## Documentation\n\nWe are still working on the documentation.\nYou can find our current documentation \n[here](https://rwth-ebc.github.io/FiLiP/master/docs/index.html).\n\n## Running examples\n\nOnce you have installed the library, you can check the [examples](/examples)\nto learn how to use the different components. \n\nCurrently, we provide basic examples for the usage of FiLiP for the FIWARE \nGEs mentioned above.\nWe suggest to start in the right order to first understand the \nconfiguration of clients.\nAfterwards, you can start modelling context data and interacting with the context \nbroker and use its functionalities before you learn how to connect \nIoT Devices and store historic data.\n\n## Testing\n\nWe use unittests to write our test cases.\nTo test the source code of the library in our CI workflow, the CI \nexecutes all tests located in the `tests`-directory and prefixed with `test_` .\n\n## How to contribute\n\nPlease see our [contribution guide](./CONTRIBUTING.md) for more details on \nhow you can contribute to this project.\n\n## Authors\n\n* [Thomas Storek](https://github.com/tstorek) \n* [Junsong Du](https://www.ebc.eonerc.rwth-aachen.de/cms/E-ON-ERC-EBC/Das-Institut/Mitarbeiter/Digitale-Energie-Quartiere/~trcib/Du-Junsong/lidx/1/) (corresponding)\n* [Saira Bano](https://www.ebc.eonerc.rwth-aachen.de/cms/E-ON-ERC-EBC/Das-Institut/Mitarbeiter/Systemadministration/~ohhca/Bano-Saira/)\n* [Sebastian Blechmann](https://www.ebc.eonerc.rwth-aachen.de/cms/E-ON-ERC-EBC/Das-Institut/Mitarbeiter/Team2/~carjd/Blechmann-Sebastian/)\n\n## Alumni\n\n* Jeff Reding\n* Felix Rehmann\n* Daniel Nikolay\n\n## References\n\nWe presented or applied the library in the following publications:\n\n- S. Blechmann, I. Sowa, M. H. Schraven, R. Streblow, D. M\u00fcller & A. Monti. Open source platform application for smart building and smart grid controls. Automation in Construction 145 (2023), 104622. ISSN: 0926-5805. https://doi.org/10.1016/j.autcon.2022.104622 \n\n- Haghgoo, M., Dognini, A., Storek, T., Plamanescu, R, Rahe, U., \n Gheorghe, S, Albu, M., Monti, A., M\u00fcller, D. (2021) A cloud-based service-oriented architecture to unlock smart energy services\n https://www.doi.org/10.1186/s42162-021-00143-x \n\n- Baranski, M., Storek, T. P. B., K\u00fcmpel, A., Blechmann, S., Streblow, R., \nM\u00fcller, D. et al.,\n(2020). National 5G Energy Hub : Application of the Open-Source Cloud Platform \nFIWARE for Future Energy Management Systems. \nhttps://doi.org/10.18154/RWTH-2020-07876 \n\n- T. Storek, J. Lohm\u00f6ller, A. K\u00fcmpel, M. Baranski & D. M\u00fcller (2019). \nApplication of the open-source cloud platform FIWARE for future building \nenergy management systems. \nJournal of Physics: \nConference Series, 1343, 12063. https://doi.org/10.1088/1742-6596/1343/1/012063 \n\n## License\n\nThis project is licensed under the BSD License - see the [LICENSE](LICENSE) file for details.\n\n## Copyright\n\n<a href=\"https://www.ebc.eonerc.rwth-aachen.de/\"> <img alt=\"EBC\" src=\"https://www.ebc.eonerc.rwth-aachen.de/global/show_picture.asp?id=aaaaaaaaaakevlz\" height=\"100\"> </a>\n\n2021-2024, RWTH Aachen University, E.ON Energy Research Center, Institute for Energy \nEfficient Buildings and Indoor Climate\n\n[Institute for Energy Efficient Buildings and Indoor Climate (EBC)](https://www.ebc.eonerc.rwth-aachen.de) \n[E.ON Energy Research Center (E.ON ERC)](https://www.eonerc.rwth-aachen.de) \n[RWTH University Aachen, Germany](https://www.rwth-aachen.de)\n\n## Disclaimer\n\nThis project is part of the cooperation between the RWTH Aachen University and \nthe Research Centre J\u00fclich.\n\n<a href=\"https://www.jara.org/de/forschung/jara-energy\"> <img alt=\"JARA \nENERGY\" src=\"https://raw.githubusercontent.com/RWTH-EBC/FiLiP/master/docs/logos/LogoJARAEnergy.jpg\" height=\"100\"> </a>\n\n## Related projects\n\n<a href=\"https://n5geh.de/\"> <img alt=\"National 5G Energy Hub\" \nsrc=\"https://avatars.githubusercontent.com/u/43948851?s=200&v=4\" height=\"100\"></a>\n\n<a href=\"https://fismep.de/\"> <img alt=\"FISMEP\" \nsrc=\"https://raw.githubusercontent.com/RWTH-EBC/FiLiP/master/docs/logos/FISMEP.png\" \nheight=\"100\"></a>\n\n\n## Acknowledgments\n\nWe gratefully acknowledge the financial support of the Federal Ministry <br /> \nfor Economic Affairs and Climate Action (BMWK), promotional references \n03ET1495A, 03ET1551A, 0350018A, 03ET1561B.\n\n<a href=\"https://www.bmwi.de/Navigation/EN/Home/home.html\"> <img alt=\"BMWK\" \nsrc=\"https://raw.githubusercontent.com/RWTH-EBC/FiLiP/master/docs/logos/bmwi_logo_en.png\" height=\"100\"> </a>\n\nThis project has received funding in the framework of the joint programming initiative ERA-Net Smart Grids Plus, with support from the European Union\u2019s Horizon 2020 research and innovation programme.\n\n<a href=\"https://www.eranet-smartgridsplus.eu/\"> <img alt=\"ERANET\" \nsrc=\"https://fismep.de/wp-content/uploads/2017/09/SmartGridsPlus_rgb-300x55.jpg\" height=\"100\"> </a>\n",
"bugtrack_url": null,
"license": null,
"summary": "[FI]WARE [Li]brary for [P]ython",
"version": "0.6.0",
"project_urls": {
"Documentation": "https://rwth-ebc.github.io/FiLiP/master/docs/index.html",
"Download": "https://github.com/RWTH-EBC/FiLiP/archive/refs/tags/v0.6.0.tar.gz",
"Homepage": "https://github.com/RWTH-EBC/filip",
"Source": "https://github.com/RWTH-EBC/filip"
},
"split_keywords": [
"iot",
" fiware",
" semantic"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "64cba4360e100c65cdb02b24c4524d65177278da3a539fb42c8d618603be182a",
"md5": "ff1f8d2060b2cba50af3a6e1e4772e9f",
"sha256": "e3bf1106a6e3f797b40a1f6825e7d437fcacccb5761d0085a298a631c14734b8"
},
"downloads": -1,
"filename": "filip-0.6.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "ff1f8d2060b2cba50af3a6e1e4772e9f",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 236585,
"upload_time": "2024-11-27T11:43:03",
"upload_time_iso_8601": "2024-11-27T11:43:03.425640Z",
"url": "https://files.pythonhosted.org/packages/64/cb/a4360e100c65cdb02b24c4524d65177278da3a539fb42c8d618603be182a/filip-0.6.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "cd157e738b7c51aa68fd37ff3ca5b0dd469e79645259f7a0403fc8c322e65cd4",
"md5": "eaac502610362f897ad1f631b25d429c",
"sha256": "3236e7788618e1b7ab856e5f425ea40589ad316bd89892b2fc362b3f89ff4452"
},
"downloads": -1,
"filename": "filip-0.6.0.tar.gz",
"has_sig": false,
"md5_digest": "eaac502610362f897ad1f631b25d429c",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 219822,
"upload_time": "2024-11-27T11:43:05",
"upload_time_iso_8601": "2024-11-27T11:43:05.637697Z",
"url": "https://files.pythonhosted.org/packages/cd/15/7e738b7c51aa68fd37ff3ca5b0dd469e79645259f7a0403fc8c322e65cd4/filip-0.6.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-11-27 11:43:05",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "RWTH-EBC",
"github_project": "filip",
"travis_ci": false,
"coveralls": true,
"github_actions": true,
"lcname": "filip"
}
JSON
