OASC – national groups of cities/municipalities to find basic common technical ground
130 cities, London, Bordeaux next
Cities are heterogeneous
Standards development organizations are competing
OASC exists to create MIMs, provide certification and training
DevOps for new types of apps (e.g. IoT, AI, LoRa) across cities
Pressure for harmonization – data can be gathered in one place and used in other
Architecture of every system/enterprise/organization is complex, the point is to agree on minimal set of interoperability points
OASC does not create new standards, it curates (like the Foundation for Public Code does not create code, but stewards it). Links to bigger initiatives
Context information management – discovering and structuring data; knowing where to send request for particular data – NGSI-LD is a generic way of structuring information, will be mandated
Shared data models
Ecosystem Transaction Management
Extend to being MIM-compatible – establishing the process for taking up learnings/granular validations from programmes and projects (SynchroniCity, SCORE)
Ways to take part: help validate e.g. data models
Validation by use
Data models – pragmatic way of starting with nuggets for linked data/semantic web
Developer-oriented documents, not standards – e.g. technical user experience
Moving towards real-time transaction of data – terms and conditions on which we handle the data – auto brokering instead of static open data setup
Data needs management – existing marketplaces do exist within the sectors, but there is a need for handling data on dynamic terms and conditions
Necessity to have a unified approach that can be implemented within different solutions, also for sharing data internally between units of the organization
Language localization challenge – there is infrastructure for handling it (versions). Alternatively – exchanging components inside country boundaries