Rical added a comment.

I'm not sure to understand: "Points 9."before" and 10."after" field are 
reserved for future development.
Is it to distinguish before=coordonates and after=time-zone ?
Here I speak only about time-zone.

Like you, to get things moving, I'll make some proposals, from the ISO style 
format -0044-03-15T00:00:00Z.

Just after "T" the time zone could be -180 to -1 to 0 to 180, then:
The precision by number 1 ... 11 is limited to the days.
I propose a more adaptable precision query by char:
Y=year, M=month, D=day, W=week, h=hour, m=minute, s=second.
But also (see below) C=century or E=era.

calendarmodel options to ask to get a time-string:

- I or ISO => like -0044-03-15T00:00:00Z

The ISO time representation is always accessible by modules.

- J or Julian => Julian
- G or Gregorian => Gregorian
- Y or year => year only in distant past, like for the precision parameter, see 
below.

calendarmodel - From this point, modules writers can manage other calendarmodel 
for each use.
But this needs: many works from many modules writers, error risks and hasardous 
interpretations. A library or more calendarmodel options could be better.

- C => digital century only, at any epoch.
- R => roman century only, at any epoch.
- CE => Common era format.
- JC => Christian format.
- india => indian standard epochs.
- china => chinese standard epochs.
- e or europ => european standard epochs.
- out of any epoch in a region, we use R(roman century).

Other countries use defined european epochs because their stories are not 
enough studied and standardised, but that could change in some countries.

calendarmodel options rules:

- They all must have a different identifier.
- We can mix them in a single parameter.
- The default is nil or I for ISO.
- The default options of europ calendarmodel are G(Gregorian) and R(roman 
century).

In the parameter named "custom" we define any client format, like in Excell or 
OpenOffice.
Examples: "D MMM YY" for "2 nov 14" or "DD/MM hh:mm" for "05/12 15:30".

The ISO style format is limited to -9999 and to +9999
The older limit of historic epoch I seen was -1901 in India.
But the archeologia progress, the links with astronomic events, the C14 
datations, and biologic recurrent events permit to consider years from distant 
past.
To manage cases like: 50,000 years, 20 millions years, we could offer simple 
formats for year before or beyond -9999.


TASK DETAIL
  https://phabricator.wikimedia.org/T99674

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Rical
Cc: JanZerebecki, Smalyshev, Jc3s5h, daniel, Aklapper, Tobi_WMDE_SW, 
Wikidata-bugs, JulesWinnfield-hu, Addshore, Liuxinyu970226, Rical, Conny, aude



_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to