​Jonathan Semple raised the following comment: 

https://joinup.ec.europa.eu/asset/adms/topic/public-comments-adms-specification-v08#comment-11523

1. Contexts.  In Listpoint we publish a large number of Code Lists some of which are widely used national standards and some of which are specific to particular application systems.  Rather than running a central team of stewards to manage all code lists we devolve maintenance down to the people who are most closely involved with each Code List and do not actively promote any Code Lists as being ‘standards’ from the centre.  This is a somewhat different from the more usual centralized ‘de jure’ standards setting approach. Instead we encourage people who are trying to solve application integration problems (mostly Police Forces at present) to create a Context representing the application system at the source end of their integration and a Context representing the application system at the target end of their integration.  A Context is therefore a proxy or profile for the collection of Code Lists that are used by an application system.  If a large number of application systems all use a particular Code List (e.g. Gender v2) then we can say that Gender v2 has become a ‘de facto’ standard.  Listpoint is effectively trying to find order in an anarchic environment by crowd-sourcing. We started on this journey quite recently but already we are seeing people beginning to agree on standardisations they can make to their own code lists so they can be shared more effectively in other Contexts.
   There are standards groups within some organizations and we support them by allowing Contexts to be created to represent a Data Standard instead of an Application.  So standards can still be promoted but application developers are not obliged to use them – they still have freedom to do their own thing if they need to. Listpoint uses Contexts only to record the Code Lists that are used in a particular Application or Standards ‘Context’.  However, I think there may be scope to extend the range of content types that can be referenced to include all the other sorts of Asset that CESAR could hold.  Application and Standard developers can then reference any asset that they either depend upon or found useful in creating their product. In Listpoint we use these references to send out email alerts to the owners of all referencing Contexts when a new version of a code list is published on which they depend. This is part of the incentive for people to contribute information on their various Contexts. The other incentive is that Listpoint provides mapping tools allowing code lists in different Contexts to be mapped together.

Component

Category