You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to define the core and extended data elements of a historical place. Probably the simplest would be to pick a place in Opele's historical administrative hierarchy, e.g. Duchy of Opole and Racibórz.
Need to decide whether this will require a full RDF sample (derived in large part from Opele) or whether a description of the differences would suffice.
The text was updated successfully, but these errors were encountered:
Following up a discussion with Graham in late August, what I will review is whether the structure for a 'current place' (e.g. Opole) can be re-used as is for a 'historical place' (e.g. Duchy of Opole) with just one change: representing the different from: to: dates that place existed in time (which should be found in its admin/political historical hierarchy) as a simple table, in place of the 'current hierarchy'.
In this way, we don't need a new pattern. The data for one or more from: to: periods for the historical place is already explicit in its admin/political historical hierarchy – we'd just be representing it in a different, more visually accessible manner in place of the (obviously not relevant) current hierarchy derived from the reference gazetteer(s). I'll create a separate Duchy of Opele UI mockup for this to illustrate what I mean.
We need to define the core and extended data elements of a historical place. Probably the simplest would be to pick a place in Opele's historical administrative hierarchy, e.g. Duchy of Opole and Racibórz.
Need to decide whether this will require a full RDF sample (derived in large part from Opele) or whether a description of the differences would suffice.
The text was updated successfully, but these errors were encountered: