W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13240] Consider replacing <time> with <data>

From: <bugzilla@jessica.w3.org>
Date: Mon, 08 Aug 2011 21:23:02 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QqXHq-0000ch-Ux@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13240

--- Comment #26 from Stephen Paul Weber <singpolyma@singpolyma.net> 2011-08-08 21:23:02 UTC ---
(In reply to comment #25)
> I'm definitely leaning towards doing this. The alternative seems to be to have
> a whole slew of elements for this kind of thing:
> 
>    <time datetime="2010-10-10">
>    <number value=10>
>    <scalar value=10 unit=kg>
>    <duration value="1h10m2.2s">
>    <timerange start="2010-01-01" end="2010-02-02">
>    <enum value="spring">
> 
> ...all of which pretty much do exactly the same thing: nothing.

Nothing except the one thing that matters: adding semantic value.

If you don't care about the semantic value I would definitely say that an
attribute solves the "some sort of machine data here" use case much better.

I don't see how you can be against the extra semantic data here when the
argument was the same (though much weaker, IMHO) for adding seperate <video>
and <audio> instead of just adding JS APIs to <object type="video/*">

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 8 August 2011 21:23:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:16 UTC