These terms seem to be used interchangeably in the documentation, but they mean different things.
I suggest adding an explanation of the terms at the start of the adoption section and checking that they are used consistently throughout the documentation.
Proposed explanation:
Adoption refers to the decision and commitment to use a data standard. It is a strategic process where stakeholders recognise the value of the standard and agree implement it. Adoption can happen at different levels:
- Policy Level: A government or organisation mandates the use of a standard.
- Sector Level: An industry or community collectively agrees to follow a standard.
- Organisational Level: A specific organisation decides to adopt a standard.
Implementation is the technical and operational process of applying the standard in practice. It involves adapting systems, transforming data, and ensuring compliance with the standard's structure and rules. Key aspects include:
- Mapping: Identifying existing data, the systems that hold it, and the transformations required to conform to the standard
- Development: Creating or updating software and databases to produce or consume data that conforms to the standard.
- Publication: Making the standardised data available for use.
Examples:
- Adoption: a national government agency mandates the use of the Open Contracting Data Standard for procurement data.
- Implementation: a procurement agency responds to the mandate by reconfiguring its database, updating its reporting software, and publishing open data that conforms to the Open Contracting Data Standard.
Key differences:
| Aspect |
Adoption |
Implementation |
| Focus |
Commitment & decision-making |
Technical execution |
| Who is involved? |
Policy makers, executives, stakeholders |
Developers, data engineers, IT teams |
| Timeframe |
Can be long-term & strategic |
Usually a defined project or process |
| End Goal |
Standard is endorsed or required |
Standard is correctly applied in systems |
In short, adoption is about saying "yes" to a standard, while implementation is about applying it in practice.
These terms seem to be used interchangeably in the documentation, but they mean different things.
I suggest adding an explanation of the terms at the start of the adoption section and checking that they are used consistently throughout the documentation.
Proposed explanation: