Skip to content
Annika edited this page Aug 14, 2024 · 16 revisions

Natural Resource Common Permitting Data Specifications

Lifecycle:Experimental Contributions:Welcome Data:Schema

Description

This repository contains common schemas related to permitting in the Natural Resources Sector.

The intent of these are to standardize the way permitting in the Natural Resource Sector is described as data to enable quality and interoperability.

Hosting these will enable and ensure version history will be maintained.

These will be reviewed as required with the related data managers and permitting teams.

Purpose

The common specifications are to

  • create cross sector data governance
  • feed intelligence to the sector
  • moving towards harmonized statuses
  • activity-based permit bundling
  • and application process tracking
  • enable consistent collection of data and metadata
  • leverage for an integrated data schema for reporting and analytics
  • identify opportunities on data quality, data visualizations, and gaps
  • develops data patterns and guidelines
  • develop common schema patterns for other areas like First Nations Consultation

Overview

Schemas

Subject Description JSON DOC
Core Specification The core permitting content, structure, data types, and expected enums that are consistent across all permitting datasets. json doc
Housing Specification The housing specific schema elements that extend the core schema. json doc
Metadata Specification The metadata elements required and captured while discovering and onboarding into an integrated dataset. json doc
Permit Name Registry Specification This spec is to enable the registry of permit names from source systems/information to be used as enums in the core Core Specification. json doc

Scripts

Subject Description Readme
Validation This package takes a JSON document and validates it against an expected schema structure as defined in a JSON schema definition file. readme
Auto-generation of docs This package converts JSON schema definition files into markdown files. readme

Future

  • Define data types

Schemas

  • status and state registries
    • To enable the mapping of source values to a standardized list
  • activity bundling
    • To enable identifying what permits are applicable to an activity on the landbase, e.g., housing, mining, connectivity.
  • client/proponent
  • other permitting initiatives