Object property descriptive context
inclusion status
https://opda.org.uk/pdtf/inclusionStatusTurtle ↓
The disposition of a fixtures-and-fittings item in a sale: whether the item is Included in, Excluded from, or absent (None) from the transaction, held as a mode of the sale rather than a quality of the property.
Whether a fixtures-and-fittings item is Included in, Excluded from, or absent (None) from a sale. A UFO Mode/Relator of the sale TRANSACTION (ODR-0007), confirmed by session-027 R4 — NOT a Quality of opda:Property (the same item is included in one sale and absent from the next, so inclusion has no rigid bearer in the brick-and-mortar). Bound on a transaction-scoped fixtures-list node (NEVER rdfs:domain opda:Property), ranging over the opda:InclusionStatusScheme value-space (Included / Excluded / None). The full sale-transaction Relator identity criterion is owned by ODR-0007.
Domain & range
- Subjects (domain)
-
Transaction - Objects (range)
-
Concept
Constraining SHACL shapes · 1
| Shape | Type | Card. | Severity | Message |
|---|---|---|---|---|
FixturesListShape | — | — | Violation | Fixtures-item opda:inclusionStatus MUST be one of the opda:InclusionStatusScheme values (Excluded / Included / None) — a sale-transaction Mode, never a Quality of opda:Property (ODR-0022 §4 / session-027 R4). |
Used in the RML mapping · 1
TriplesMap(s) that populate this property (ADR-0060 — the RML mapping's own bidirectional trace to the PDTF JSON Schema).
Provenance · dct:source
harness/odr/ODR-0022/section-Rules-4