Permit Signals — Ontology Crosswalk
Schema: upcoming (extends events-timeline — all permit rows live under event_category='civic' with event_type LIKE 'permit.%')
Target standards: DCAT-US v3.0 (dataset-level), schema.org/GovernmentPermit, W3C PROV-DM (permit lifecycle as activity chain)
Authority: Schema.org, W3C, U.S. DOC
Status: FAIR-aligned, schema.org rich-results compatible
Dataset license: mixed, per source city — each record keeps its source city's open-data terms and source URI (Los Angeles records are CC-BY-4.0; Seattle, New York, Chicago, Philadelphia, Dallas, Houston, and Phoenix records carry their own city open-data terms) · commercial use is licensed for Seattle and Los Angeles permit records only, through the Commercial All-access license; every other city is research-only
1. Why this pairing
Permit data is structurally a lifecycle — filed → approved → issued → finaled / revoked / expired. schema.org has no construction-specific permit type, so Codex maps each permit to schema.org/GovernmentPermit (a subtype of schema.org/Permit) and carries the construction permit category in the Codex axiom:permit.* enum (§4). Because each stage is a separate record in the Events Timeline linked by metadata.related_event_ids, PROV-DM is the right way to express the chain.
2. Dataset-level (DCAT-US v3.0)
| DCAT-US field | Value |
|---|---|
dct:identifier |
urn:axiom:codex:dataset:permit-signals:v1.0.0 |
dct:title |
"Axiom Permit Signals Dataset" |
dct:description |
"Building, demolition, zoning, and construction permits across U.S. jurisdictions with parcel linkage, and developer entity resolution." |
dcat:keyword |
["permits", "construction", "zoning", "parcels", "development-pipeline"] |
dcat:theme |
["http://publications.europa.eu/resource/authority/data-theme/REGI", "...ECON"] |
dct:license |
per source city's open-data terms (research); Los Angeles records only are CC-BY-4.0 |
3. Record-level crosswalk → schema.org/GovernmentPermit
{
"@context": "https://schema.org",
"@type": "GovernmentPermit",
"@id": "urn:axiom:event:3f8a0e12-1b2c-4d5e-9f7a-6d1e2c3b4a5f",
"identifier": [
{"@type": "PropertyValue", "propertyID": "jurisdiction-native", "value": "SF-BP-2026-01234"}
],
"validFrom": "2026-03-14",
"validThrough": "2027-03-14",
"issuedBy": {
"@type": "GovernmentOrganization",
"name": "San Francisco Department of Building Inspection"
},
"validIn": {
"@type": "Place",
"address": {"streetAddress": "2200 N. Broad St", "addressLocality": "Philadelphia", "addressRegion": "PA"}
},
"permitType": "axiom:permit.newConstruction",
"actionStatus": "axiom:permit.approved",
"axiom:declaredValueUSD": 2400000,
"axiom:parcelId": "philadelphia-pa:123-456-789",
"axiom:h3Index": "88283082b9fffff"
}
3.1 Field-by-field mapping
| Codex field | schema.org | Notes |
|---|---|---|
event_id |
@id |
Links to Events Timeline |
source_ref |
identifier[].value |
Jurisdiction-native permit number |
permit_type |
permitType (axiom-namespaced value) |
Enum — see §4 |
event_type |
actionStatus |
e.g. permit.filed → axiom:permit.filed |
occurred_at |
dateCreated or validFrom by stage |
Stage-dependent |
effective_from |
validFrom |
|
effective_to |
validThrough |
|
issuing_agency |
issuedBy.GovernmentOrganization |
|
jurisdiction_slug |
— | Embedded in issuedBy.name |
address |
validIn.Place.address |
|
parcel_id |
axiom:parcelId |
See JOIN_KEYS §4.6 |
h3_index |
axiom:h3Index |
|
declared_value |
axiom:declaredValueUSD |
|
applicant_entity_urn |
axiom:applicantEntityUrn |
Codex entity resolution |
4. permit_type enum (Codex-namespaced)
schema.org/GovernmentPermit doesn't define a permit-type taxonomy. Codex publishes one under axiom:permit.*:
axiom:permit.newConstructionaxiom:permit.additionaxiom:permit.alterationaxiom:permit.demolitionaxiom:permit.changeOfUseaxiom:permit.zoning(variance, rezoning, special exception)axiom:permit.signageaxiom:permit.mechanical(HVAC, plumbing, electrical)axiom:permit.fireaxiom:permit.other
5. Lifecycle as PROV-DM
Each permit is a cascade in Events Timeline — permit.filed → permit.approved → permit.completed (or the revoked/cancelled branches). The full chain is emitted as a PROV-DM prov:wasInformedBy graph; see events-timeline ontology crosswalk §5.
Typical stage-linked JSON-LD fragment:
{
"@id": "urn:axiom:event:<completed-event-uuid>",
"@type": "prov:Activity",
"prov:type": "permit.completed",
"prov:wasInformedBy": [
{"@id": "urn:axiom:event:<approved-event-uuid>"},
{"@id": "urn:axiom:event:<filed-event-uuid>"}
]
}
6. FAIR compliance
| Principle | Status |
|---|---|
| F | ⚠️ (schema.org/GovernmentPermit mapping; DCAT-US metadata planned, not yet published) |
| A | ✅ (Parquet distribution for published cities; no query API) |
| I | ⚠️ (schema.org + PROV-DM mapping; DCAT-US alignment planned) |
| R | ✅ (per-record source-city license and source URI, versioned schema) |
7. Deviations
- schema.org has no construction-specific permit type. Codex uses
schema.org/GovernmentPermit; the construction category lives inaxiom:permit.*(§4). - Jurisdiction-native
permit_typevalues vary wildly. Every jurisdiction has its own vocabulary. Codex normalizes to the 10-valueaxiom:permit.*enum (§4); the raw source value is preserved inaxiom:sourcePermitType.
8. Changelog
- v1.0 (2026-04-16) — Initial crosswalk. Permit Signals is published as a view over Events Timeline (event_type LIKE 'permit.%') rather than a separate dataset.