This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17855 - i18n-ISSUE-88: local/floating date terminology
Summary: i18n-ISSUE-88: local/floating date terminology
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 07:04 UTC by contributor
Modified: 2012-09-27 23:32 UTC (History)
4 users (show)

See Also:


Attachments

Description contributor 2012-07-18 07:04:21 UTC
This was was cloned from bug 16959 as part of operation convergence.
Originally filed: 2012-05-07 17:11:00 +0000
Original reporter: Addison Phillips <addison@lab126.com>

================================================================================
 #0   Addison Phillips                                2012-05-07 17:11:13 +0000 
--------------------------------------------------------------------------------
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 Ian 'Hixie' Hickson 2012-09-27 23:32:32 UTC
I started doing this, but then I realised this would cause unfortunate confusion because the keyword that invokes it is called "datetime-local". So I think changing the term might be more confusion than help.