Category:Chronologies Working Group - Revision history

Khider: /* Relative chronologies */ Add Polls

2017-09-18T19:04:13Z

‎Relative chronologies: Add Polls

Khider: /* Relative chronologies */ fix typo

2017-09-14T19:18:02Z

‎Relative chronologies: fix typo

Khider: Relative chronologies

2017-09-14T19:16:53Z

Relative chronologies

Jeg: ref to Cox & Richard added

2017-08-19T00:00:32Z

ref to Cox & Richard added

Jeg at 23:57, 18 August 2017

2017-08-18T23:57:01Z

Jeg at 23:56, 18 August 2017

2017-08-18T23:56:32Z

Jeg at 23:56, 18 August 2017

2017-08-18T23:56:00Z

Jeg at 23:52, 18 August 2017

2017-08-18T23:52:27Z

Jeg: new section on time representation

2017-08-18T23:44:00Z

new section on time representation

Jeg at 23:40, 18 August 2017

2017-08-18T23:40:54Z

@@ Line 569: / Line 569: @@
 | Flag for mixed chronologies ||R || || [[User:Khider|Deborah Khider]] ([[User talk:Khider|talk]]) 12:16, 14 September 2017 (PDT)
 |}
 == Polls ==

@@ Line 562: / Line 562: @@
 |-
 | The target || E|| Which record was used as target for the alignment? || [[User:Khider|Deborah Khider]] ([[User talk:Khider|talk]]) 12:16, 14 September 2017 (PDT)
-| -
+|-
 | Labeling features ||E for manual alignment/D for automated alignment || Which features of the records were used as tie points || [[User:Khider|Deborah Khider]] ([[User talk:Khider|talk]]) 12:16, 14 September 2017 (PDT)
 |-
@@ Line 568: / Line 568: @@
 |-
 | Flag for mixed chronologies ||R || || [[User:Khider|Deborah Khider]] ([[User talk:Khider|talk]]) 12:16, 14 September 2017 (PDT)
 |}

@@ Line 548: / Line 548: @@
 Desired Metadata
 </poll>
 == Polls ==

← Older revision		Revision as of 00:00, 19 August 2017
Line 87:		Line 87:

	Thus, the direction of time flow (forward or backward) can always been inferred from context; however, the diversity of spelling and abbreviations makes it difficult for machines to guess this, and thus a more disciplined representation would be helpful. For all representations, one might consider an internal representation like `kilo_years_BP`, and an external representation for display purposes like `kyr BP`.		Thus, the direction of time flow (forward or backward) can always been inferred from context; however, the diversity of spelling and abbreviations makes it difficult for machines to guess this, and thus a more disciplined representation would be helpful. For all representations, one might consider an internal representation like `kilo_years_BP`, and an external representation for display purposes like `kyr BP`.
		+
		+	Lastly, we note that the excellent ontology of geologic time by Cox & Richard<ref>Cox, S. J. D., and S. M. Richard (2015), A geologic timescale ontology and service, Earth Science Informatics, 8(1), 5–19, doi:10.1007/s12145-014-0170-6.</ref>, which deals with >1Ma time scales, does not encompass such distinctions, and thus a new representation is needed.

	== Recommendations from the literature ==		== Recommendations from the literature ==

@@ Line 77: / Line 77: @@
 * Possible instances of '''yearlyIncrement''' are : ''year, years, annum, annums'', etc
-* Possible instances of prefix are: ''none, kilo, mega, giga''; this conveys information about the multiplicative factor that needs to be applied to the increments.
+* Possible instances of '''prefix''' are: ''none, kilo, mega, giga''; this conveys information about the multiplicative factor that needs to be applied to the increments.
-*  Possible instances of suffix are: ''none, BP, CE, AD''. the suffix conveys  information about the direction of time flow, and the reference point (with some ambiguity that needs resolving).
+*  Possible instances of '''suffix''' are: ''none, BP, CE, AD''. the suffix conveys  information about the direction of time flow, and the reference point (with some ambiguity that needs resolving).
 - For ''years CE'', the prefix is none, the yearlyIncrement is years, the suffix is CE. Thus time flows forward from the origin of the Common Era, which is sometimes placed at year 0 (astronomical calendar, or [https://www.iso.org/iso-8601-date-and-time-format.html ISO8601]), sometimes at year 1. A system for disambiguation is needed (perhaps by attaching an ISO standard).

← Older revision		Revision as of 23:56, 18 August 2017
Line 73:		Line 73:
	One way to unify its representation is to recognize that all known applications use something of the form:		One way to unify its representation is to recognize that all known applications use something of the form:

−	'''prefix _ yearlyIncrement _ suffix'''	+	'''prefix _ yearlyIncrement _ suffix'''

@@ Line 80: / Line 80: @@
 *  Possible instances of suffix are: ''none, BP, CE, AD''. the suffix conveys  information about the direction of time flow, and the reference point (with some ambiguity that needs resolving).
-For ''years CE'', the prefix is none, the yearlyIncrement is years, the suffix is CE. Thus time flows forward from the origin of the Common Era, which is sometimes placed at year 0 (astronomical calendar, or [https://www.iso.org/iso-8601-date-and-time-format.html ISO8601]), sometimes at year 1. A system for disambiguation is needed (perhaps by attaching an ISO standard).
+- For ''years CE'', the prefix is none, the yearlyIncrement is years, the suffix is CE. Thus time flows forward from the origin of the Common Era, which is sometimes placed at year 0 (astronomical calendar, or [https://www.iso.org/iso-8601-date-and-time-format.html ISO8601]), sometimes at year 1. A system for disambiguation is needed (perhaps by attaching an ISO standard).
- For ''kyr BP'' the suffix conveys that time flows in reverse from the present day, again defined with some ambiguity as 1950 CE or 2000 CE (see Age poll). The prefix is kilo, indicating that a factor of 1000 needs to be applied.
+- For ''kyr BP'' the suffix conveys that time flows in reverse from the present day, again defined with some ambiguity as 1950 CE or 2000 CE (see Age poll). The prefix is kilo, indicating that a factor of 1000 needs to be applied.
-For "Ga", the prefix is giga, indicating a billion factor. The increment is "annum", and the suffix is none, indicating implicitly something like BP (where the 1950 or 2000 reference point is immaterial given the time spans involved.
+- For "Ga", the prefix is giga, indicating a billion factor. The increment is "annum", and the suffix is none, indicating implicitly something like BP (where the 1950 or 2000 reference point is immaterial given the time spans involved.
-Thus, the direction of time flow (forward or backward) and always been inferred from context; this is
+Thus, the direction of time flow (forward or backward) can always been inferred from context; however, the diversity of spelling and abbreviations makes it difficult for machines to guess this, and thus a more disciplined representation would be helpful. For all representations, one might consider an internal representation like `kilo_years_BP`, and an external representation for display purposes  like `kyr BP`.
 == Recommendations from the literature  ==

@@ Line 73: / Line 73: @@
 One way to unify its representation is to recognize that all known applications use something of the form:
-'''prefix ___ increment ___ suffix'''
+'''prefix _ yearlyIncrement _ suffix'''
 == Recommendations from the literature  ==

@@ Line 67: / Line 67: @@
 Using CE (Common Era)
 </poll>
 == Recommendations from the literature  ==