The core data model was established following the RCM, including the Appendixes, the documentation related to the Regional Minerals Database — specifically the technical specification developed in 2016 that proposes the data structure of the database — and information collected from the member states, either through direct interviews or through direct observation of public resources made available by the states, such as for example the Mining Cadasters provided as web portals with free access.
Each Attribute of each Entity is identified by a “Business term”, that describes uniquely the significance of the attribute. The “Business term” has a human-readable form and has a direct correspondence in a “Technical term”, that is to the extent possible the transcription of the business term in camelCase.
The usage of a specific case for the technical term is a convention taken specifically for each standard, as there is no general universal rule applicable. The case should be compatible with the potential technical formats that are going to be used as representation for the standardized entities. The present standard does not specify, nor restrict, the usage of a specific technical format.
In perspective, the most suitable technical formats for the representation of the entities described in this standard would be JSON (including JSON-LD) or XML.
As convention, camelCase is used as the naming scheme for technical terms, as being the most human-readable and being the choice of other standardization initiatives, for example those developed under https://spdci.org/.
Numbering conventions
- All Entities, primary and secondary, are numbered from MD.01 to MD.13 (MD = Mining Data — a convention internal to this document, that can be replaced in the future)
- All Code Lists are numbered from MDC.01 to MDC.07 (MDC = Mining Data Codes — a convention internal to this document)
