On 20/01/2012, at 6:52 PM, Bronislav Klučka wrote: > On 20.1.2012 18:52, Cameron Heavon-Jones wrote: >> >> >> The lang attribute is the structural declaration of the content's >> localization, be it prose or data values. There should be no difference in >> what the following mean: >> >> <p lang="en">This is some english text</p> >> >> <input lang="en" type="text" value="This is some english input"/> >> >> <input lang="en" type="date" value="2012"/> <!-- An english date --> > "English date" is misleading term here > > <input lang="en" type="datetime" value="2010-11-19T15:48+01:00"/> > is a datetime, not English datetime, not Czech datetime (since time zone > suggests CET), but a datetime, the difference is how it should be presented. > But also in this case translation/language has no meaning here, because of > the time zone in dates, East Coast Time presentation will be different than > London time presentation, it can have the same structure (mm/dd/yyyy > [0-11]:[0-59] am/pm) but values should be different. > And without lang attribute, this should follow users choice > 11/19/2010 2:48 pm in London, 19.11.2010 15:48 in Prague and as such should > be displayed according to localization > > > > > Brona >
Yes, i agree that "english date" is slightly confusing but with the in the context of the additional examples i thought it adequately described the problem. I agree with your description of the value of datetime with regards to timezone as a facet of the value. Without any lang resolution within the representation, i agree that the presentation should follow the user's choice locale. No disagreements here. Thanks Cameron Jones
