In message 49a5d6e8.5070...@lachy.id.au, Lachlan Hunt
lachlan.h...@lachy.id.au writes
[Resending this to the list now that the problem that prevented it from
accepting any mail has been fixed.]
[Likewise]
Andy Mabbett wrote:
Use-cases for machine-readable date mark-up are many: as
On Sat, Feb 28, 2009 at 4:39 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote:
Do we
really have to illustrate use cases in action, before we can develop the
technology which allows them to be demonstrated exists?
Though I admit it seems ass-backwards until you get it, the answer
is yes, you
In message
7c2a12e20902241613v7ba27c60q433fd84a74279...@mail.gmail.com, Aryeh
Gregor simetrical+...@gmail.com writes
the emphasis on clear and immediate use-cases. I didn't notice you
mentioning any of those in your posts. What are some examples of
actual, concrete applications with
[Resending this to the list now that the problem that prevented it from
accepting any mail has been fixed.]
Andy Mabbett wrote:
Use-cases for machine-readable date mark-up are many: as well as
the aforesaid calendar interactions, they can be used for
sorting; for
Andy Mabbett wrote:
It seems to me that there are several outstanding, and overlapping,
issues for time in HTML5, which include use-cases, imprecise dates,
Gregorian vs. non-Gregorian dates and BCE (aka “BC“) dates.
The time element was primarily designed to address use cases involving
In message 49a3e9b9.4090...@lachy.id.au, Lachlan Hunt
lachlan.h...@lachy.id.au writes
Andy Mabbett wrote:
It seems to me that there are several outstanding, and overlapping,
issues for time in HTML5, which include use-cases, imprecise dates,
Gregorian vs. non-Gregorian dates and BCE (aka “BC“)
and non-Gregorian
calendars. ...but I do see the no BCE compromise as a workable one.
-Original Message-
From: whatwg-boun...@lists.whatwg.org [mailto:whatwg-boun...@lists.whatwg.org]
On Behalf Of Andy Mabbett
Sent: Tuesday, 2009 February 24 13:42
To: WHATWG List
Subject: Re: [whatwg] Dates
At 13:59 -0500 24/02/09, WeBMartians wrote:
It's back! It won't die! :-)
Although it can be argued that a standard should not consider the
work required for implementation, many of the trade-offs in
reference to times and dates do indeed take the present state of
code into consideration.
In message 619d9f095a7941eebcbb05fd4b03f...@pirate, WeBMartians
webmarti...@verizon.net writes
Although it can be argued that a standard should not consider the work
required for implementation, many of the trade-offs in reference to
times and dates do indeed take the present state of code
On Tue, Feb 24, 2009 at 6:01 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote:
What's the expected end-of-life date for HTML5? Do we really want to
hamstring ourselves 'til then, by considering only current, as-of-2009,
capabilities?
HTML5 is not supposed to have an end-of-life. It's meant to
that are represented by strings of more than four
characters: years preceding 999 BCE (or 1000 BCE?) or
subsequent to CE.
-Original Message-
From: David Singer [mailto:sin...@apple.com]
Sent: Tuesday, 2009 February 24 15:12
To: WeBMartians; 'Andy Mabbett'; 'WHATWG List'
Subject: Re: [whatwg] Dates
This is a copy of my blog post:
http://pigsonthewing.wordpress.com/2009/02/23/dates-and-coordinates-in-html5/
(aka http://is.gd/kB3k )
please feel free to comment here, or there.
I'm grateful to Bruce Lawson of Opera for alerting me to discussion of
the time element on this mailing list
12 matches
Mail list logo
