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
skos:scopeNote "Used for things where the precision of a date is sufficient, such as most projects, tasks, and the like.Recommended usage is to put the hours through microseconds to zero to avoid spurious precision."^^xsd:string ;
2715
+
skos:scopeNote "Used for things where the precision of a date is sufficient, such as most projects, tasks, and the like.Recommended usage is to zero out the hours through microseconds to avoid spurious precision."^^xsd:string ;
2716
2716
.
2717
2717
2718
2718
gist:actualEndDateTime
2719
2719
a owl:DatatypeProperty ;
2720
-
rdfs:subPropertyOf gist:actualEndDateTime ;
2720
+
rdfs:subPropertyOf gist:endDateTime ;
2721
2721
rdfs:range xsd:dateTime ;
2722
2722
skos:definition "An abstraction over the various precisions of actual end time. They can be compared since they all have the same format."^^xsd:string ;
2723
2723
skos:editorialNote "Dave: this was in your presentation but not your OWL file. Not sure if you still want it."^^xsd:string ;
@@ -2730,14 +2730,8 @@ gist:actualEndMicrosecond
2730
2730
rdfs:range xsd:dateTime ;
2731
2731
skos:definition "A system time used for timestamps."^^xsd:string ;
"A system time will be as precise as the system can supply, typically at least milliseconds, sometimes microseconds."^^xsd:string ,
2739
-
"The convention for timestamps, such as recording a transaction, is to specify just the end point; the start time is rarely needed."^^xsd:string
2740
-
;
2733
+
skos:prefLabel "actual end microsecond"^^xsd:string ;
2734
+
skos:scopeNote "A system time will be as precise as the system can supply, typically at least milliseconds, sometimes microseconds. The convention for timestamps, such as recording a transaction, is to specify just the end point; the start time is rarely needed."^^xsd:string ;
2741
2735
.
2742
2736
2743
2737
gist:actualEndMinute
@@ -2757,7 +2751,7 @@ gist:actualStartDate
2757
2751
skos:definition "The actual date that something started, with precision of one day (+/- 12 hours)."^^xsd:string ;
skos:scopeNote "Used for things where the precision of a date is sufficient, such as most projects, tasks, and the like. Recommended usage is to put the hours through microseconds to zero to avoid spurious precision."^^xsd:string ;
2754
+
skos:scopeNote "Used for things where the precision of a date is sufficient, such as most projects, tasks, and the like. Recommended usage is to zero out the hours through microseconds to avoid spurious precision."^^xsd:string ;
"A system time will be as precise as the system can supply, typically at least milliseconds, sometimes microseconds."^^xsd:string ,
2781
-
"The convention for timestamps, such as recording a transaction, is to specify just the end point; the start time is rarely needed. This property is defined for the cases when you do need to capture the runtime of a system process, and is then used in conjunction with gist:actualEndMicrosecond"^^xsd:string
2782
-
;
2773
+
skos:scopeNote "A system time will be as precise as the system can supply, typically at least milliseconds, sometimes microseconds. The convention for timestamps, such as recording a transaction, is to specify just the end point; the start time is rarely needed. This property is defined for the cases when you do need to capture the runtime of a system process, and is then used in conjunction with gist:actualEndMicrosecond."^^xsd:string ;
2783
2774
.
2784
2775
2785
2776
gist:actualStartMinute
@@ -2812,7 +2803,7 @@ gist:atDateTime
2812
2803
rdfs:range xsd:dateTime ;
2813
2804
skos:definition """This is the top level property for asserting time.
2814
2805
2815
-
The sub-properties allow the ontologist to do three things:
2806
+
The subproperties allow the ontologist to do three things:
2816
2807
1) Distinguish start and end times.
2817
2808
2) Indicate whether a time is planned or actual. This is useful for everything from project management to calendar appointments and the like. It is also useful for date effectivities; i.e., something valid up to a planned date).
2818
2809
3) Distinguish varying levels of precision; sort of a simple version of the Allen functions.
@@ -2824,14 +2815,10 @@ Time zone offset, such as -6:00 (of which there are a few dozen) is recognized i
2824
2815
There will be many historical dates that do not have a time zone offset (e.g., Lincoln's birthday, as well as about 75% of all legacy systems), and in that case the offset can be omitted.
2825
2816
2826
2817
The conventions for precision that are repeated in each property are as follows:
2827
-
2828
-
*DateTime is an abstraction over the various precisions of its sub-properties.
2829
-
2830
-
*Date refers to a calendar date (birthdays and invoice dates) and is assumed to be precise +/- 12 hours. Time zone offset is allowed.
2831
-
2832
-
*Minute refers to clock time; e.g., a meeting will start at 9:15 with a timezone offset. Precision is assumed to be +/- 1 minute.
2833
-
2834
-
*Microsecond refers to system time, and it will be as precise as the system can supply; typically at least milliseconds, sometime microseconds.
2818
+
- *DateTime is an abstraction over the various precisions of its subproperties.
2819
+
- *Date refers to a calendar date (e.g., birthdays and invoice dates) and is assumed to be precise +/- 12 hours. Time zone offset is allowed.
2820
+
- *Minute refers to clock time; e.g., a meeting will start at 9:15 with a timezone offset. Precision is assumed to be +/- 1 minute.
2821
+
- *Microsecond refers to system time, and it will be as precise as the system can supply; typically at least milliseconds, sometime microseconds.
2835
2822
2836
2823
"""^^xsd:string ;
2837
2824
skos:prefLabel "at date time"^^xsd:string ;
@@ -2847,12 +2834,12 @@ gist:baseConversionFactor
2847
2834
2848
2835
gist:birthDate
2849
2836
a owl:DatatypeProperty ;
2850
-
rdfs:subPropertyOf gist:actualStartDate ;
2837
+
rdfs:subPropertyOf gist:startDateTime ;
2851
2838
rdfs:range xsd:dateTime ;
2852
-
skos:definition "The date some living thing was born."^^xsd:string ;
2839
+
skos:definition "The date some living thing was or will be born."^^xsd:string ;
skos:scopeNote "This property refers to a calendar date and is assumed to be precise +/- 12 hours (time zone offset is allowed). It is recommended to put the hours through microseconds to zero, to avoid spurious precision."^^xsd:string ;
2842
+
skos:scopeNote "This is a subproperty of gist:startDateTime rather than gist:actualStartDateTime because some living things have yet to be born. This property refers to a calendar date and is assumed to be precise +/- 12 hours (time zone offset is allowed). It is recommended to zero out the hours through microseconds to avoid spurious precision. Implementations requiring a birthdate to the minute can define a subproperty."^^xsd:string ;
2856
2843
.
2857
2844
2858
2845
gist:comesFromAgent
@@ -2925,16 +2912,12 @@ gist:conversionOffset
2925
2912
2926
2913
gist:deathDate
2927
2914
a owl:DatatypeProperty ;
2928
-
rdfs:subPropertyOf gist:actualStartDate ;
2915
+
rdfs:subPropertyOf gist:actualEndDate ;
2929
2916
rdfs:range xsd:dateTime ;
2930
-
skos:definition """Date of death, typically as established by a coronor.
2931
-
2932
-
AtDate refers to a calendar date (birthdays and invoice dates) and is assumed to be precise +/- 12 hours (time zone offset is allowed)
2933
-
2934
-
“2021-06-01T00:00:00-6:00”^^xsd:dateTime
2935
-
2936
-
Note: recommended us is to put the hours throiugh microseconds to zero, to avoid spurious precision."""^^xsd:string ;
2917
+
skos:definition "Date of death, typically as established by a coronor."^^xsd:string ;
skos:scopeNote "Refers to a calendar date and is assumed to be precise +/- 12 hours (time zone offset is allowed). Recommended usage is to zero out the hours through microseconds to avoid spurious precision. Implementations requiring a birthdate to the minute can define a subproperty."^^xsd:string ;
2938
2921
.
2939
2922
2940
2923
gist:description
@@ -3702,12 +3685,20 @@ gist:plannedEndDate
3702
3685
a owl:DatatypeProperty ;
3703
3686
rdfs:subPropertyOf gist:plannedEndDateTime ;
3704
3687
rdfs:range xsd:dateTime ;
3705
-
skos:definition
3706
-
"The date that something was planned to end, with precision of one day (+/- 12 hours)."^^xsd:string ,
3707
-
"Used for anything with a planned end date, such as when a lease will expire, when an offer is no longer available, etc. Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual. Recommended usage is to put the hours through microseconds to zero to avoid spurious precision."^^xsd:string
3708
-
;
3688
+
skos:definition "The date that something was planned to end, with precision of one day (+/- 12 hours)."^^xsd:string ;
skos:scopeNote "Used for anything with a planned end date, such as when a lease will expire, when an offer is no longer available, etc. Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual. Recommended usage is to zero out the hours through microseconds to avoid spurious precision."^^xsd:string ;
3692
+
.
3693
+
3694
+
gist:plannedEndDateTime
3695
+
a owl:DatatypeProperty ;
3696
+
rdfs:subPropertyOf gist:endDateTime ;
3697
+
rdfs:range xsd:dateTime ;
3698
+
skos:definition "An abstraction over the various precisions of planned end time. They can be compared since they all have the same format."^^xsd:string ;
3699
+
skos:editorialNote "Dave: this was in your presentation but not your OWL file. Not sure if you still want it."^^xsd:string ;
3700
+
skos:prefLabel "planned end date time"^^xsd:string ;
3701
+
skos:scopeNote "This property, unlike gist:actualEndDateTime, does not have a subproperty for microsecond precision, because planned times typically are not expressed at that level of granularity. Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual."^^xsd:string ;
3711
3702
.
3712
3703
3713
3704
gist:plannedEndMinute
@@ -3717,22 +3708,17 @@ gist:plannedEndMinute
3717
3708
skos:definition "The date that something was planned to end, with precision of +/- 1 minute."^^xsd:string ;
"Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual."^^xsd:string ,
3722
-
"Used for things like meetings and time card entries, where the hour and minute are important. Recommended usage is to zero out the seconds and microseconds to avoid spurious precision."^^xsd:string
3723
-
;
3711
+
skos:scopeNote "Used for things like meetings and time card entries, where the hour and minute are important. Recommended usage is to zero out the seconds and microseconds to avoid spurious precision.Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual."^^xsd:string ;
3724
3712
.
3725
3713
3726
3714
gist:plannedStartDate
3727
3715
a owl:DatatypeProperty ;
3728
3716
rdfs:subPropertyOf gist:plannedStartDateTime ;
3729
3717
rdfs:range xsd:dateTime ;
3730
-
skos:definition
3731
-
"The date that something was planned to start, with precision of one day (+/- 12 hours)."^^xsd:string ,
3732
-
"Used for anything with a planned start date, such as when a lease will start, when a configuration becomes available, etc. Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual. Recommended usage is to put the hours through microseconds to zero to avoid spurious precision."^^xsd:string
3733
-
;
3718
+
skos:definition "The date that something was planned to start, with precision of one day (+/- 12 hours)."^^xsd:string ;
skos:scopeNote "Used for anything with a planned start date, such as when a lease will start, when a configuration becomes available, etc. Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual. Recommended usage is to zero out the hours through microseconds to avoid spurious precision."^^xsd:string ;
3736
3722
.
3737
3723
3738
3724
gist:plannedStartDateTime
@@ -3742,10 +3728,7 @@ gist:plannedStartDateTime
3742
3728
skos:definition "An abstraction over the various precisions of planned start time. They can be compared since they all have the same format."^^xsd:string ;
3743
3729
skos:editorialNote "Dave: this was in your presentation but not your OWL file. Not sure if you still want it."^^xsd:string ;
3744
3730
skos:prefLabel "planned start date time"^^xsd:string ;
3745
-
skos:scopeNote
3746
-
"This property, unlike gist:actualStartDateTime, does not have a sub-property for microsecond precision, because planned times typically are not expressed at that level of granularity."^^xsd:string ,
3747
-
"Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual."^^xsd:string
3748
-
;
3731
+
skos:scopeNote "This property, unlike gist:actualStartDateTime, does not have a subproperty for microsecond precision, because planned times typically are not expressed at that level of granularity. Typically a planned date is in the future when first captured, but when tasks run late, we leave the plan where it was and compare it to the actual."^^xsd:string ;
0 commit comments