-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
place and org should claim membership of att.datable #2451
Comments
Assigning to @trishaoconnor to move this issue through a discussion in Council. Presuming the idea is approved, will re-assign to @jamescummings to do the work in a branch and issue a PR. |
We've seen with What about |
@skurzinz The The encoding developed for Maybe what's needed by all of these elements is a generalized/adaptable |
Some of that was a bit off the original ticket, I know. But as @skurzinz points out, it's important we consider how these concepts of person, organization, place, and event relate to each other in temporality. After all that thinking about |
I’d say those are two different scenarios: In the one, an entity begins/ends to exist (which is quite parallel to the att.datable on Similarly, an What makes the proposal by @jamescummings tempting in my view is the ease of modeling the non-complicated low-hanging fruit in a generic way: Start with (I just noticed that similar to CIDOC "beginning_of_begin" and "end_of_begin" you can do the same on
Those finely grained coding options are good to have.) |
I support the idea of adding place, org, and also person to att.datable, seeing it as a very useful, generic way to provide (and determine in processing) the range of dates where these entities existed. I see it as a good step towards consistent generic model and interoperability. Nevertheless, I don't think it should preclude the use of child elements like birth/date/event with their own dating attributes to cover the details and complexities of the source material and its interpretation. |
Organisations and places, along with most other named, might exist only for a particular duration. While with person there are specific elements inside such as birth and death, there is nothing similar for places and organisations and places. One solution is to create child event elements for the creation and dissolution of an organisation, or the founding and destruction of a place, and that is good when one also wants to provide additional information about the creation/dissolution/founding/destruction of the entity, but when you just want to record the date, this seems like a messing inconvenience. Events are already claim membership of att.datable.
If done, one could easily add notBefore/notAfter/from/to to indicate duration of the existence of a place. So, assuming you don't want to supply more details, instead of having to do something like this:
one could just do:
If council thought this was an ok idea, I'm happy to implement it consistently across all named entities.
The text was updated successfully, but these errors were encountered: