| Cardinality | Technical term | Business term | Description | Semantic data type |
|---|---|---|---|---|
| 1..1 | inspectionId | Inspection ID number | Generated identifier, including the initials of the inspector name and the timestamp of the recording. Example: PS-2025-12-02-16-03 — inspection performed by Peter Smith, on 2 December 2025, recorded at the time of 16:03 | Identifier |
| 1..1 | inspectionDate | Inspection date | The dates of inspection of the mine site, either by Member State government personnel (or designates), by ICGLR Third Party Auditors, or by the ICGLR Mineral Chain Auditor | Date |
| 1..1 | inspectionResult | Inspection result | The result of the inspection in changing or maintaining the certification status | MDC.01 Certification Status |
| 0..1 | inspectionReport | Inspection report | The Full Inspection Report of each inspection (if feasible). The MIME type should take value from the subset: application/pdf, text/plain, application/vnd.openxmlformats-officedocument.wordprocessingml.document | File |
| 0..1 | inspectionPurpose | Inspection purpose | Short text | String |
| 0..1 | inspectionResults | Inspection results | Long text | String |
| 1..1 | inspectorName | Inspector name | Full name | String |
| 1..1 | inspectorPosition | Inspector position | Title or position | String |
| 1..1 | governmentAgency | Government Agency | Short text | String |
| 0..1 | governmentId | Government ID | Government identification number, if applicable | Identifier |
Notes on Inspection
The “Inspection number” is not mandated by the RCM manual, but it is highly useful as a single unique identifier, particularly in the context of data storage, reporting and querying. Its addition was recommended by the ICGLR secretariat technical team.
Usage of the File element should not be treated lightly because it is one of the most important causes for the growth of storage space on medium and long run, and can also generate risks in the data transfers between countries and ICGLR, as the data batches will grow larger and will be more prone to transaction errors due to the long time of transfer in low bandwidth conditions. The limitation should be set at least for the Regional Minerals Database (recommended max size 10 MB), which can be made more strict (e.g., 5 MB, 8 MB) by member states.
When a certain attribute holds a term that may be composed of several distinct values, the actual usage should determine if it needs to be further broken down into components or even be treated as a secondary entity.
