replaces
Links a corrected publication unit — a tariff filing, or a standalone pricing model with no enclosing filing — to the prior one it replaces for the SAME effective period. The replaced subject is voided; the replacing one occupies the same effective window with corrected content. A filing replaces a filing; a pricing model replaces a pricing model. Use urpx:supersedes for a forward-in-time change of effective period; use urpx:replaces for an in-place correction of an existing period.
| Canonical IRI | https://urpx.org/ns/ontology/replaces | ||
|---|---|---|---|
| Note | For a pricing model published within a filing, corrections ride the filing chain: the corrected filing replaces the prior filing, and the models inside carry no lifecycle assertions of their own. Model-level replacement is for standalone models (market or dynamic feeds, competitive supply, contracts, scenarios). The replacing subject carries the corrected content plus the unchanged content, so it stands alone for its effective window. A replaced subject should also be marked voided via urpx:cancelledBy. Distinct from supersession (forward-in-time end-dating; the prior stays valid history) and from withdrawal (cancellation with no successor). | ||
| Source | |||
Properties
| owl:inverseOf | urpx:replacedBy |
|---|---|
| rdf:type | owl:ObjectProperty |
| rdfs:comment | Links a corrected publication unit — a tariff filing, or a standalone pricing model with no enclosing filing — to the prior one it replaces for the SAME effective period. The replaced subject is voided; the replacing one occupies the same effective window with corrected content. A filing replaces a filing; a pricing model replaces a pricing model. Use urpx:supersedes for a forward-in-time change of effective period; use urpx:replaces for an in-place correction of an existing period. |
| rdfs:label | Replaces |
| skos:note | For a pricing model published within a filing, corrections ride the filing chain: the corrected filing replaces the prior filing, and the models inside carry no lifecycle assertions of their own. Model-level replacement is for standalone models (market or dynamic feeds, competitive supply, contracts, scenarios). The replacing subject carries the corrected content plus the unchanged content, so it stands alone for its effective window. A replaced subject should also be marked voided via urpx:cancelledBy. Distinct from supersession (forward-in-time end-dating; the prior stays valid history) and from withdrawal (cancellation with no successor). |
Blank Nodes
| rdfs:domain | |
|---|---|
| rdfs:range | |