Bug 16959 - i18n-ISSUE-88: local/floating date terminology
i18n-ISSUE-88: local/floating date terminology
Status: ASSIGNED
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec
unspecified
PC Windows NT
: P2 minor
: ---
Assigned To: Travis Leithead [MSFT]
HTML WG Bugzilla archive list
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-07 17:11 UTC by Addison Phillips
Modified: 2014-04-08 23:59 UTC (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Addison Phillips 2012-05-07 17:11:13 UTC
2.5.5.7 Global dates and times
http://dev.w3.org/html5/spec/single-page.html#global-dates-and-times

This defines a 'global date and time', which is the same as a 'local date and time', only with a time zone representation. I propose changing the 'local' value to use the term 'floating' (since it is not truly local). The term 'global' could remain. I would also suggest adding a reference to w3.org/TR/timezone (our note) to help users understand when to use which type.
Comment 1 contributor 2012-07-18 07:04:24 UTC
This bug was cloned to create bug 17855 as part of operation convergence.
Comment 2 Travis Leithead [MSFT] 2014-02-07 22:47:02 UTC
My plan for this bug is to add the reference to w3.org/TR/timezone and change the "local date and time" section to "floating date and time" (which section is still needed by the HTMLTimeElement, regardless of removing the <input type="datatime-local"> control. This will align the terminology and hopefully avoid author confusion.
Comment 3 Travis Leithead [MSFT] 2014-02-11 01:09:11 UTC
The change to rename local to floating terminology has landed in HTML5.1. Please review for consistency/correctness. Thanks!

https://github.com/w3c/html/commit/22162bf56037c266c78f9c9d77ccd1c8fda40b77
Comment 4 Addison Phillips 2014-02-11 04:13:29 UTC
Diff looks good to me, but I don't see the addition of the reference to w3.org/TR/timezone? Is that intentional?
Comment 5 Addison Phillips 2014-02-11 04:56:22 UTC
Argh. I see it addressed in bug 16957
Comment 6 Travis Leithead [MSFT] 2014-02-22 01:42:31 UTC
Now back-ported to fix the HTML5.0 CR issue:
https://github.com/w3c/html/commit/efd24702b2bd4803850971b55745210e50af6420

Leaving active as there is some concern raised with this change

Removed the CR keyword as this is addressed for CR.
Comment 7 Sam Ruby 2014-04-08 23:59:43 UTC
It was noted that at the F2F that this feature is at risk for 5.0.