Versioning division properties about ocd-division-ids HOT 5 CLOSED

I'm also guessing this is primarally a US issue, but I imagine this bug will translate wherever we have multiple versions of shapefiles that we relate to

from ocd-division-ids.

Partial fix in place; needs work for place, & county

from ocd-division-ids.

and cd-*

from ocd-division-ids.

So, I guess we're talking about versioned properties? We currently only have a facility for versioning IDs with validFrom, validThrough. In Canada, I haven't yet encountered a use case where I needed to version a property; our Census tries hard to maintain IDs over time, and to not reuse an ID until several decades have passed. But I haven't really plumbed historical use cases.

In Canada, I use two-letter language code suffixes for translations, so the pattern of adding suffixes for alternate versions (in time or language) of the same datum has some precedent.

Also, I'd prefer to use a full YYYY year suffix instead of YY.

from ocd-division-ids.

Closing as the original issue was fixed, and we don't need to set a policy on how to name the columns for custom properties of different vintages.

from ocd-division-ids.