As the world is in a state of constant change, Who's On First (WOF) records are constantly changing, too. With most record changes, a simple property update and update to thewof:lastmodified
property field is sufficient. However, if a Significant Event takes place, additional work is needed.
So, what exactly is a Significant Event and how is it defined?
wof:name
without storing the original wof:name
as an alternative namewof:name
due to the original wof:name
being wrong to begin withwof:parent_id
wof:placetype
wof:hierarchy
to include an updated wof:id
If a WOF record is updated due to a Significant Event, the following work is required:
wof:id
.wof:supersedes
value equal to that of the existing feature's wof:id
.wof:superseded_by
value equal to that of the new feature's wof:id
.mz:is_current
value equal to 0
.edtf:deprecated
property. Otherwise, the edtf:cessation
property will be given a date (YYYY-MM-DD). This edtf
date should equal the date when the feature was edited.It is important to note that this list, as written today, may be incomplete or unable to capture the subtleties and demands of real-life. Additionally, we expect a decent amount of churn in Who's On First during the early days of the project which may require us to bend the rules in certain cases. However, this churn should settle as the database grows in size and allow us to possibly refine these rules.
Our Who's On First Life Cylce Document has more detailed information about Significant Events in relation to the wof:id
.
Questions? Drop us an email.