Follow an energy-certificate example
A practitioner asks: “Which property does this certificate describe, and what does it say?” Follow that question through the existing candidate. Every linked term and source item below comes from the current model.
1. Start with the information people recognise
An Energy Performance Certificate (EPC) is represented in the candidate by four source items. Each has its own workbook row and full source path. The table explains how the candidate groups them around the certificate.
| Source item | Candidate treatment | Why it is grouped here |
|---|---|---|
| Uprn | challenge | Use the certificate UPRN for reconciliation with common Property identity and challenge the legacy numeric datatype. |
| Please supply a copy of the EPC for the property | consolidate | Record how the certificate is supplied as controlled certificate metadata. |
| Current energy efficiency rating | consolidate | Place the controlled rating on the certificate that reports the assessment. |
| Address | consolidate | Keep certificate address text as reconciliation evidence on the certificate, not as the current Property address. |
“Consolidate” means several source fields contribute to a shared modelling pattern. “Challenge” flags an inherited assumption for review. Neither label records human approval.
2. Read the proposed relationship
The property has its semantic home in the Common boundary. The certificate and its relationships belong to Property Data Services. That division is a proposed ownership of meaning, not an instruction that every organisation must store data in the same way.
Inspect the Property Data Services context or review the wider construction, services and energy topic.
3. Check what the values actually mean
The current energy-rating vocabulary contains 10 values: A, B, C, D, E, F, G, Exempt property, Survey instructed, No certificate.
A question for domain reviewers
A–G are ratings. “No certificate”, “Survey instructed” and “Exempt property” describe other states. Should one value list carry all of these meanings, or should a later revision distinguish them? This is a review question raised by the existing source and candidate, not an approved change.
Inspect the value list and its source trace →
4. Separate a source rule from a proposed data rule
The pack’s main Unique Property Reference Number (UPRN) provides a second useful example. Its source datatype is xsd:integer. The candidate treats it as a string of digits because it is an identifier used for matching, rather than a quantity used for arithmetic.
- Source evidence
- The original UPRN item retains the integer datatype and records the candidate disposition as challenge.
- Candidate validation
- The Property shape requires one UPRN string matching
^[0-9]+$. This is the candidate’s rule; a technical pass does not settle whether the modelling choice is correct.
5. Turn an observation into useful feedback
A useful review identifies the exact item, explains a concrete scenario, cites supporting evidence and says what should change. For this example:
“For the current energy-rating item, please distinguish a recorded rating from the absence of a certificate. Here is the case our service needs to exchange, and the source that supports it.”
This is an illustrative feedback prompt. It has not been submitted or accepted. Read the review questions and decision route.
Evidence: the linked source-item, resource, vocabulary and shape pages are generated from the same candidate corpus. The diagram explains that corpus; it does not add an ontology assertion or a real property record.
Comments
Loading comments…
Sign in to post a comment