Hi,
Happy to hear from you.
Could you elaborate a bit more about your specific area of interest?
We are very aware about the PSD2 directive and its implications.
Indeed, we believe that our core API, FIWARE NGSIv2 could be adopted as
open standard API for supporting this directive (accompanied with a
proper standard information model). In favor of this we believe there
are two interesting questions to mention:
- The FIWARE NGSIv2 API specification
<http://fiware.github.io/context.Orion/api/v2/latest/> has been the
basis of the soon-to-be-published NGSI-LD specifications created
under the umbrella of an ETSI Industry Specification Group
<https://docbox.etsi.org/ISG/CIM/Open/ISG_CIM_NGSI-LD_API_Draft_for_public_review.pdf>.
NGSI-LD is backward compatible with FIWARE NGSIv2, introducing
certain new features like support to JSON-LD. The FIWARE Community
is committed to bring an open source reference implementation of
this API through the core component of the FIWARE platform: the
Orion Context Broker.
- The Orion Context Broker component of FIWARE has recently been
adopted as CEF Building Block by the EC
<https://ec.europa.eu/digital-single-market/en/news/connecting-europe-facility-cef-telecom-work-programme-2018-adopted>
with the announcement of the CEF Telecom programme 2018. As a
result, Public Administrations from EU member states are recommended
to use it for the development of Digital Service Infrastructures
(e.g., infrastructures for publication of open data) which can bring
support to Digital Services that can work in every member state and
cross-frontier. Of course, the adoption of this recommendation by
private organizations is welcomed and fostered. In this respect, we
believe that support of the PSD2 directive is a good example of
directive enabling the creation of Digital Service Infrastructures
supporting the development of services that can work
cross-frontier. Consequently, creating a link between the PSD2 and
the CEF Digital Building Blocks program maybe an opportunity.
Bottom line: the PSD2 directive leads to definition of Open APIs by
banks. Should they invent a new one or could they leverage on one that
already exists and has got the endorsement by ETSI and the EC?
In addition to that, several components have been developed as part
of the FIWARE platform to bring support to access control on FIWARE NGSI
API resources, following standard XACML architecture concepts
(PEP+PDP+PAP) as well as the publication and monetization of these
resources. Work regarding publication has been developed supporting
publication through extended open data portals (e.g., we have developed
the extensions which enable CKAN open data portals to transform into
data marketplaces). Monetization aspects have been developed in
collaboration with TM Forum
<https://www.tmforum.org/press-and-news/myfiwarestory-tm-forum-partnership-creating-data-economy-infrastructure/>,
supporting TM Forum Open APIs for the modeling and publication of
commercial offerings on digital resources. Overall looking towards
bringing support to Data Economy concepts.
Hope this information helps you to gain even more interest in
FIWARE. As mentioned, a bit more info on your side would be helpful to
explore how we can help you.
Cheers,
–
Juanjo Hierro
Chief Technology Officer
juanjose.hierro@fiware.org <juanjose.hierro@fiware.org>
www.linkedin.com/in/jhierro <https://www.linkedin.com/in/jhierro>
Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro
<https://twitter.com/JuanjoHierro>
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-collaboration-req mailing list
Fiware-collaboration-req@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-collaboration-req
Hi,
Happy to hear from you.
Could you elaborate a bit more about your specific area of interest?
We are very aware about the PSD2 directive and its implications.
Indeed, we believe that our core API, FIWARE NGSIv2 could be adopted as
open standard API for supporting this directive (accompanied with a
proper standard information model). In favor of this we believe there
are two interesting questions to mention:
<http://fiware.github.io/context.Orion/api/v2/latest/> has been the
basis of the soon-to-be-published NGSI-LD specifications created
under the umbrella of an ETSI Industry Specification Group
<https://docbox.etsi.org/ISG/CIM/Open/ISG_CIM_NGSI-LD_API_Draft_for_public_review.pdf>.
NGSI-LD is backward compatible with FIWARE NGSIv2, introducing
certain new features like support to JSON-LD. The FIWARE Community
is committed to bring an open source reference implementation of
this API through the core component of the FIWARE platform: the
Orion Context Broker.
adopted as CEF Building Block by the EC
<https://ec.europa.eu/digital-single-market/en/news/connecting-europe-facility-cef-telecom-work-programme-2018-adopted>
with the announcement of the CEF Telecom programme 2018. As a
result, Public Administrations from EU member states are recommended
to use it for the development of Digital Service Infrastructures
(e.g., infrastructures for publication of open data) which can bring
support to Digital Services that can work in every member state and
cross-frontier. Of course, the adoption of this recommendation by
private organizations is welcomed and fostered. In this respect, we
believe that support of the PSD2 directive is a good example of
directive enabling the creation of Digital Service Infrastructures
supporting the development of services that can work
cross-frontier. Consequently, creating a link between the PSD2 and
the CEF Digital Building Blocks program maybe an opportunity.
Bottom line: the PSD2 directive leads to definition of Open APIs by
banks. Should they invent a new one or could they leverage on one that
already exists and has got the endorsement by ETSI and the EC?
In addition to that, several components have been developed as part
of the FIWARE platform to bring support to access control on FIWARE NGSI
API resources, following standard XACML architecture concepts
(PEP+PDP+PAP) as well as the publication and monetization of these
resources. Work regarding publication has been developed supporting
publication through extended open data portals (e.g., we have developed
the extensions which enable CKAN open data portals to transform into
data marketplaces). Monetization aspects have been developed in
collaboration with TM Forum
<https://www.tmforum.org/press-and-news/myfiwarestory-tm-forum-partnership-creating-data-economy-infrastructure/>,
supporting TM Forum Open APIs for the modeling and publication of
commercial offerings on digital resources. Overall looking towards
bringing support to Data Economy concepts.
Hope this information helps you to gain even more interest in
FIWARE. As mentioned, a bit more info on your side would be helpful to
explore how we can help you.
Cheers,
–
Juanjo Hierro
Chief Technology Officer
juanjose.hierro@fiware.org <juanjose.hierro@fiware.org>
www.linkedin.com/in/jhierro <https://www.linkedin.com/in/jhierro>
Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro
<https://twitter.com/JuanjoHierro>
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
Fiware-collaboration-req mailing list
Fiware-collaboration-req@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-collaboration-req