- From: <bugzilla@jessica.w3.org>
- Date: Fri, 13 Jan 2012 17:48:20 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15278 --- Comment #6 from Cameron Jones <cmhjones@gmail.com> 2012-01-13 17:48:17 UTC --- This should only apply for formatting and parsing the value to\from a user interface display. The transmission format should retain the ISO 8601 representation value so as to remain unambiguous and remove the need for any additional encoding declaration within the request. This is an internet standard and i am unaware of any actual alternatives to this (other than the subset rfc3339). Since the consumer of transmitted values is servers and developers this has little impact within multi-cultural uses and even the english language is almost a prerequisite for programming let alone using a gregorian calendar. The only limit with this is that dates before the common era will not be encodable, however that a user is able to interact with dates\times within a chosen calendar scale satisfies the overwhelming majority of use cases and represents far greater authoring potential than currently forcing display within the gregorian calendar. With further thought this approach may contain potential for greater applicability in scope as currency and collation information is also specifiable within these tags. A new currency input could be added with automatic currency symbol substation and formatting. Collation could be used for automated ordering of lists which are dynamically populated on client-side. The additional benefit to full support of this feature is that this is an extensive standard repository of locale data which is already managed and integrated into operating systems and programming languages. This should make implementation and maintenance a relatively simple process and without introducing any overhead into html or specification authorities. -- Configure bugmail: https://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 Friday, 13 January 2012 17:48:28 UTC