Repository for contribution of code mappings into OED

[johcarter]

Description

Code mappings (eg construction and occupancy codes into OED) are being contributed and are a useful resource for people using OED but probably shouldn't be part of the specification itself. where should we put them?

[johcarter]

The proposal is to store code mappings in a new folder within the main OED repo 'Contributions', but the schemes and mappings will not be considered part of the specification and not subject to OED versioning processes.

Schemes/mappings can be contributed as and when, and added to the develop branch in between OED releases.

Comments welcome.

[aiste-kalinauskaite]

@johcarter could you list which parts of the OED would be affected by this? What is covered by "schema" and what is covered by "mappings"?

[johcarter]

OED would not be affected, this would be an independent area of data contributions.

Schemes could cover code lists for custom GeogSchemes for example, as we have some reserved values in 'OtherValues' for third party GeogSchemes.

Mappings will normally be other occupancy and construction scheme codes into OED, but not limited to. For example it could include peril code mappings and other code mappings into enumerated code lists in OED, like the sec mods.