Phase1 Workshop13

20-09-10 Architecture - Platform Framework Concept

Participants

• Stefan Schäfer
• Dani Schwander
• SNCF, Axelle Lemagnen
• Xrail, Cecilia Dagerholm
• DB Cargo, Mahesh Bhatter
• CFL, Lori Paquet

Minutes

Discussion based on presentation (link below).

longer discussion about migration path and sequence of implementation --> this was not the scope of this meeting and will be covered afterwards in separate workshops.

 

Inputs

• provide detailed information about usage of access token for the various systems (different transaction volumes, access methodologies,...)
• monitoring of data usage and workflow (e.g. similar to block chain technology)
• a better term for access protocol is usage protocol since it not only monitors access but also usage of the data and services
• differentiate the relevance and usage of the modules. Depending on that the service levels must be different.
• consider importance of the modules
• Naming of modules
  • Identity = Access/Identity Mgmt
  • Content = Data Mgmt
• license module is only providing the necessary data for billing and invoice. Billing and invoice is part of the EcoSystem.
• licensing on pretty much everything, each data object should be licensed, specially all restricted data
• channel management is something for the future when considered as alignment of all types of communication paths