Does ISO 8601 provide any guidelines for writing long date format, such as 2006 March 12, Sunday,or Sunday, 12 March 2006 is taken as standard. What about the...
... such ... standard. ... No, it doesn't. The "Scope" (Section 1) specifically excludes representations using words in the representation (for month or day,...
In a message dated 3/12/2006 5:01:40 P.M. Central Standard Time, siddharthab19@... writes: Does ISO 8601 provide any guidelines for writing long date...
... Or human to human communications. -Pyster "Imagination is more important than knowledge. Knowledge is limited; imagination encircles the world." - Einstein...
... That's a separate issue which ISO8601 is not intended to address. I can't think off-hand of any international standard that attempts to get into such...
Hi all How do I go about mentioning approximated dates according to ISO 8601? I need the following date types translated: 'Summer 2006' 'Around 2006-04' ...
I don't think you can, though with 'between' dates, they can be covered by date ranges, like 2006-04-01--2006-07-31 (or whatever you actual range is, which can...
... ISO 8601:2004 does not allow truncation. ISO 8601:2004 introduces a "time axis". A time value must be a discrete point or interval of that time axis to be...
Remember that the fractions can be on whatever the smallest unit is, so P1.5Y is valid. Other than that, maybe also pass a boolean or an enum to specify ...
What is the semantical format of such a time span? Christian ... depends on what ISO 8601:2004 does not allow truncation. ISO 8601:2004 introduces a "time...
Hi all I had a thought - ISO specifies the length of February as either 28 or 29 days (the latter for leap years), however it is my understanding that February...
Your understanding is incorrect. One leap year every four years is slightly too many leap years (and led to downfall of the Julian calendar). The Gregorian...
... See section 5.5 of ISO 8601:2000 (which is available under files in this group). Basically combine two timepoints with a slash (umm... solidus): So summer...
... No, use reduced precision (:2000) or reduced accuracy (:2004). Basically any field to the right could be thought of as being its lowest value (0 or 1). ...
Hi, ... In this case you don't need a February with 30 days. You could use a non leap year as a leap year, e.g. 2100 or 2200. On the other side, a tropical...
I think we can say with assurance: *it won't be *it will be shorter. How MUCH shorter remains a problem. Peter Haas <mailinglists@...> wrote: Hi, But...
Thanks for your help! ... See section 5.5 of ISO 8601:2000 (which is available under files in this group). Basically combine two timepoints with a slash...
Man I'm glad I'm not going to be around for the Year 10,000 bug, though ;-) ... Hi, ... February as either 28 ... is my ... have 30 days. ... a number with an ...
... This can be squished down to 2006-06-21/09-21 D. ... From: "Christian Ankerstjerne" <panzer@...> To: <ISO8601@yahoogroups.com> Sent: Friday,...
Duncan Bath
dbath@...
Mar 18, 2006 11:47 pm
1531
... It's not really worth it. 2006-01-01/09-01 Some humans will see this as 3 years, rather than 8 months. (truncation vs reduced precision). If you want to...
... (truncation vs ... Which would be why truncation is not allowed in ISO 8601:2004. And also why I would always use the most complete representation....
_http://en.wikipedia.org/wiki/Talk:Leap_year_ (http://en.wikipedia.org/wiki/Talk:Leap_year) Is there a 4000-year rule? It has been suggested (by the...
