Open annabelleee opened 6 years ago
Timespan Model:
Note from 2018-06-14 call: Do need p2/E55 on the Timespan, with use case of estimated / computed timespans from other data rather than evidenced in primary sources. Also this is more consistent with every other branch, where resources can have Types.
OTOH, there's no need for p2/E55 on the Dimensions, as the Type is from the predicate.
I'd agree with that. The question whether time span can have a type is a tricky one I agree. For consistency I would like to see it there but I can't think of a good use case either.
Time span is limited to E2 as a domain.
I put the CRM properties in in relation to XSD:Date, but we could make a version with EDTF as well.
embarassingly I have long ago lost both the IP and any login information I have for our joint arches installation, so building the branch was beyond my reach this time. I did create metadata and some sample data for discussion. I would be happy to try to build the branch but I would need the above info again.
https://docs.google.com/spreadsheets/d/1C6uEx_FxePvideG5O03ydFhqXEa3oPuYlv51qzpTAlY/edit#gid=0
Three branches: Time-span (Basic) Time-span (Extended) Time-span (EDTF) JSON exists, need to create archesproject.org pages.
We discussed two versions of this: one using the EDTF data type in Arches and the other using XSD. I don't have a photo of the sketch on this (just my notes), so if someone has it, please upload the sketch photo.
Steps to completion (updated):