Entity attribute
Entity attribute is one of Demiton's published registers for Australian civil construction. One key/value attribute on a project, worker, asset or other entity, such as a project's stage. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
Part of Counterparties in the register catalog.
- Register ID
entity_attributeUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- A stateThe current value of something, replaced when it changes.
- Status
- DeclaredDefined, and fills when a source produces its first record.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- AS/NZS ISO 19162:2020Geographic information - Well-known text representation of coordinate reference systems (AU/NZ adoption)
- GDA2020 / MGA2020Geocentric Datum of Australia 2020 and Map Grid of Australia 2020 (National Measurement (Recognized-Value Standard of Measurement of Position) Determination 2017)
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles
- GDPRGeneral Data Protection Regulation
- EPSG Geodetic Parameter DatasetEPSG Geodetic Parameter Dataset (EPSG:7844 GDA2020, EPSG:4326 WGS 84)
- ISO 19162:2019Geographic information - Well-known text representation of coordinate reference systems (with Amd 1:2023)
- OC4IDSOpen Contracting for Infrastructure Data Standard (projectStatus / project phase vocabulary)
- RFC 7946The GeoJSON Format
- NZGD2000 / NZTM2000New Zealand Geodetic Datum 2000 and New Zealand Transverse Mercator 2000 (LINZ)
- Privacy Act 2020 (NZ)Privacy Act 2020 - Information Privacy Principles
- OSGB36 / ETRS89 (OSTN15)British National Grid datum and ETRS89 with OSTN15 transformation (Ordnance Survey)
- UK GDPRUK General Data Protection Regulation with Data Protection Act 2018
- NAD83(2011) / NAVD 88North American Datum of 1983 (2011) and North American Vertical Datum of 1988 (NGS)
Connectors
Connected today
Demiton keeps this register current from these systems now.
No system fills this register yet.
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
None planned yet.
Fields
10 fields: 5 required, 5 optional.
Required
Every record carries these fields.
- valueText
The resolved canonical value: the OC4IDS phase, employment state, opportunity outcome, and so on.
Example:
LF - Forklift- shelf_typeText
The pattern instance
entity_attribute:{key}; today the only carrier of the attribute identity and of the per-key supersede bucket.Example:
worker- asserted_atDate and time
When the value was last asserted by the resolver (
valid_from, defaulting to write time)Example:
2026-06-18T09:00:00+10:00- attribute_keyText
The canonical attribute this row asserts —
stage,employment_status,outcome,value,closed_date,project_managerobserved; 19 keys declared in all.Example:
high_risk_licence_class- subject_entity_idWhole number
The project, worker, asset or opportunity the attribute is about; the shared subject of the row.
Example:
5503
Optional
Present when the source system records them.
- evidenceGroup of fields
The raw resolver signals reconciled to produce the value, kept for auditability.
- confidenceNumber
The resolver's confidence in the value; 1.0 on both resolvers today.
Example:
0.95- valid_untilDate and time
The supersession stamp; the live row is
valid_until IS NULL, and superseded values are retained as an audit trail.- legal_entityWhole number
The legal entity the assertion is scoped to when the producer knows it.
- financial_periodText
The financial period the assertion is scoped to when the producer knows it.
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Financial periodcontext for the record, from
When known - Legal entitycontext for the record, from
When known
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "asserted_at": "2026-06-18T09:00:00+10:00", "attribute_key": "high_risk_licence_class", "confidence": 0.95, "shelf_type": "worker", "source_id": "form-9931", "source_system": "ASSIGNAR", "subject_entity_id": 5503, "value": "LF - Forklift"}Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/entity_attribute/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.