CWRC-Writer Annotations: should we include calendar values in dates

[ilovan]

Can and should you try to incorporate calendar values in dates?
Would this be supported by the date format we are using? (Susan doesn't think so)
Can we find something else that would support it better? (which we will need to do if the current date format does not support it and we decide it should be included).

XML (TEI) example:

<date when="1991-01-02" calendar="#gregorian">

[ilovan]

@joelacummings , I'll let you folks label the issue based on the conventions the ontology group uses.
[questions from @SusanBrown ]

[DeborahStacey]

In the Time Ontology, the Gregorian calendar is assumed and I don't think that they have any way to do other calendars. If we use the Time ontology and XSD time data types also do not use different calendars. If we want to handle different calendars then we would have to extend the Time ontology or create separate ontologies for different calendars that mirror the Time ontology (uggh!!!). Time is always such a problem. Deb

…

________________________________ From: Mihaela Ilovan <notifications@github.com> Sent: Thursday, April 25, 2019 11:57 AM To: cwrc/ontology Cc: Subscribed Subject: [cwrc/ontology] CWRC-Writer Annotations: should we include calendar values in dates (#481) Can and should you try to incorporate calendar values in dates? Would this be supported by the date format we are using? (Susan doesn't think so) Can we find something else that would support it better? (which we will need to do if the current date format does not support it and we decide it should be included). XML (TEI) example: <date when="1991-01-02" calendar="#gregorian"> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#481>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABC2EXRZEDF4GM5V6RQXUZ3PSHIGPANCNFSM4HIOP7ZA>.

[JasmineDW]

@alliyya @SusanBrown is this closed since we're mapping dates to CIDOC time span?

[SusanBrown]

Does CIDOC timespan cover other calendars? On Nov 12, 2021, at 3:21 PM, JasmineDW ***@***.******@***.***>> wrote: CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to ***@***.******@***.***> @alliyya<https://github.com/alliyya> @SusanBrown<https://github.com/SusanBrown> is this closed since we're mapping dates to CIDOC time span? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#481 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEFJIBSOPS4GN5SR6KTIG3ULVZK3ANCNFSM4HIOP7ZA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[alliyya]

Consulted with Erin.

CIDOC timespan doesn't directly cover other calendars, but we can type a timespan as having a particular type of date/calendar used. But still using Gregorian dates in the P82a/b for interoperability for tools/data.

Example provided by Erin

<todays_date_AH> a crm:E52_Time-Span ; 
    crm:P2_has_type "Hijri date" ; 
    rdfs:label "Today's date as determined by the Islamic calendar" ;
    crm:P82_at_some_time_within "11 Rabi Al-Akhar, 1443 AH" ; 
    P82a_begin_of_the_begin "2021-11-16 00:00:00" ; 
    P82b_end_of_the_end "2021-11-16 11:59:59" . ```

[SusanBrown]

Great. Is there a vocabulary of calendars that we can use for the typing instead of a string? Would https://perio.do/technical-overview/ be helpful in this context? We spent quite a lot of time mapping the periods used by the Orlando interface in preparation for making them part of periodO. I think the work is about 90% done and it could be very useful in terms of data faceting, potentially, as well as connecting with how the interface works. I’m not sure if periodO is still taking in new periods, but I could inquire, if we thought it was work pursuing. On Nov 16, 2021, at 12:56 PM, Alliyya Mo ***@***.******@***.***>> wrote: CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to ***@***.******@***.***> Consulted with Erin. CIDOC timespan doesn't directly cover other calendars, but we can type a timespan as having a particular type of date/calendar used. But still using Gregorian dates in the P82a/b for interoperability for tools/data. Example provided by Erin <todays_date_AH> a crm:E52_Time-Span ; crm:P2_has_type "Hijri date" ; rdfs:label "Today's date as determined by the Islamic calendar" ; crm:P82_at_some_time_within "11 Rabi Al-Akhar, 1443 AH" ; P82a_begin_of_the_begin "2021-11-16 00:00:00" ; P82b_end_of_the_end "2021-11-16 11:59:59" . ``` — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#481 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEFJIFD3G6PHNH2ZMT2KGTUMKLOFANCNFSM4HIOP7ZA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.