Issue 458: Proofreading of scope notes of P79-P80-P81-P82

ID: 
458
Starting Date: 
2019-10-25
Working Group: 
3
Status: 
Done
Closing Date: 
2020-06-26
Background: 

In the 45th joint meeting of the CIDOC CRM SIG and SO/TC46/SC4/WG9; 38th FRBR – CIDOC CRM Harmonization meeting; during the discusion of issue 410, the sig asked SS and MD and CEO to proofreading or reformulate the following properties

P79-P80 by SS

P81-P82 by MD & CEO

Heraklion, October 2019

Current Proposal: 

Posted by Steve on 27/10/2019

Here is the homework about P79 & P80

 

In the 46th joint meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9; 39th FRBR - CIDOC CRM Harmonization meeting;The sig reviewed the edited scope note for E79 beginning is qualified by (HW by SS) and accepted proposed changes. It was decided that P79 beginning is qualified by will appear in version 7.0 of the CRM. But at the same time, a new issue must start regarding whether P79 should remain in the CIDOC-CRM or if it should be moved to CRMarcheo. The decision regarding its fate in the CRM universe will be made after version 7.0. 
The minutes of ISSUE 380 during the 43rd sig meeting need be consulted regarding any decisions/proposals made concerning how to treat time-spans that were ongoing at the time of documentation. 
The details of P79 beginning is qualified by and  of P80 end is qualified by can  be found in the here
The HW  about P81-P82 is not yet done.  The scope notes remain the same in the version 7. CEO will continue to look at this and see if the scope note can be improved in versions next to 7.0.

Athens, February 2020

Posted by Martin on 24/3/2020

Dear All,

Here my revision of P81, P82. I have added the phrases in bold, and added examples. This should go into version 7.0.
I have kept the quantification many to one, because keeping simultaneously multiple estimates is aquestion of provenance. If the maintainers of the KB believe all estimates are correct, they should replace them by the estimate as described in bold, and document the arguments for the individual periods. On the other side, if they decide to keep different time-spans for the same period per estimate, the query mechanism should compute and evaluate based on the resulting estimate as described in bold.

Please comment.

Best,

Martin

---------------------------------------------------------------------------------------------------------------------------

"P81 ongoing throughout" (at least)  and "P82 at some time within"(at most) :

P81 ongoing throughout
Domain:              E52 Time-Span
Range:                E61 Time Primitive
Quantification:    many to one, necessary (1,1:0,n)
 
Scope note:         This property associates an instance of E52 Time-Span with an instance of E61 Time Primitive specifying a minimum period of time covered by it. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows  a Time-Span’s minimum temporal extent (i.e. its inner boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different minimum extents without contradicting each other, the smallest interval including these extents will be the best estimate. This should be taken into account for information integration.

Examples:       *   The time-span of the development of the CIDOC CRM(E52) ongoing throughout 1996-2019(E61) (observed until time of documentation 1.1.2020)
                         *   The time-span of the construction of the imperial palace in Beijing under Emperor Yong Le(E52) ongoing throughout 1407-1419 (E61)

 

P82 at some time within
Domain:              E52 Time-Span
Range:                E61 Time Primitive
Quantification:    many to one, necessary (1,1:0,n)

Scope note:         This property describes the maximum period of time within which an E52 Time-Span falls. Since Time-Spans may not have precisely known temporal extents, the CIDOC CRM supports statements about the minimum and maximum temporal extents of Time-Spans. This property allows  a Time-Span’s maximum temporal extent (i.e. its outer boundary) to be assigned an E61 Time Primitive value. Time Primitives are treated by the CIDOC CRM as application or system specific date intervals, and are not further analysed. If different sources of evidence justify different maximum extents without contradicting each other, the resulting intersection of these extents will be the best estimate. This should be taken into account for information integration.

Examples:  * The time-span of the development of the CIDOC CRM (E52) at some time within 1992-infinity (E61)
                    * The time-span of the Battle of the Teutoburg Forest (E52) at some time within 9AD (E61)
                    * The time-span of the construction of the imperial palace in Beijing under Emperor Yong Le (E52) at some time within 1406-1420(E61)
------------------------------------------------------------------------------------------------------------------------------------------------ 

Outcome: 

In the 47th joint meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9; 40th FRBR - CIDOC CRM Harmonization meeting; the  SIG reviewed the new scope notes for the properties P79-P80-P81-P82,  used to describe how inner and outer boundaries of intervals are combined in information integration. The sig accepted the  minor modifications in the scope notes of P79 & P80 and the added text for P81 & P81 and to start a new issue for discussing examples of integrating (i) non-contradictory minimal extents and (ii) non-contradictory maximal extents –HW to MD.

The issue closed

June 2020

Reference to Issues: