14:52:36 <RRSAgent> RRSAgent has joined #i18n
14:52:36 <RRSAgent> logging to http://www.w3.org/2011/07/27-i18n-irc
14:52:43 <Zakim> Zakim has joined #i18n
14:52:49 <aphillip> trackbot prepare teleconference
14:53:04 <aphillip> trackbot, prepare teleconference
14:53:06 <trackbot> RRSAgent, make logs world
14:53:08 <trackbot> Zakim, this will be 4186
14:53:08 <Zakim> ok, trackbot; I see I18N_CoreWG()11:00AM scheduled to start in 7 minutes
14:53:09 <trackbot> Meeting: Internationalization Core Working Group Teleconference
14:53:09 <trackbot> Date: 27 July 2011
14:53:34 <aphillip> Agenda: http://lists.w3.org/Archives/Member/member-i18n-core/2011Jul/0013.html
14:53:49 <aphillip> ScribeNick: aphillip
14:53:49 <aphillip> Scribe: Addison Phillips
14:53:50 <aphillip> Chair: Addison Phillips
14:53:57 <aphillip> rrsagent, draft minutes
14:53:57 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
14:54:28 <aphillip> rrsagent, set logs world-visible
14:54:38 <aphillip> rrsagent, draft minutes
14:54:38 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
14:56:16 <r12a> zakim, dial richard-home
14:56:16 <Zakim> ok, r12a; the call is being made
14:56:17 <Zakim> I18N_CoreWG()11:00AM has now started
14:56:18 <Zakim> +Richard
14:57:08 <Zakim> -Richard
14:57:09 <Zakim> I18N_CoreWG()11:00AM has ended
14:57:09 <Zakim> Attendees were Richard
14:58:11 <r12a> :-)
14:58:32 <Zakim> I18N_CoreWG()11:00AM has now started
14:58:39 <Zakim> +Addison_Phillips
14:58:42 <aphillip> zakim, I am Addison_Phillips
14:58:42 <Zakim> ok, aphillip, I now associate you with Addison_Phillips
15:00:07 <r12a> zakim, dial richard-home
15:00:07 <Zakim> ok, r12a; the call is being made
15:00:09 <Zakim> +Richard
15:03:22 <Gwyneth> Gwyneth has joined #i18n
15:03:32 <Zakim> +[Microsoft]
15:03:50 <aphillip> zakim, [Microsoft] is Gwyneth
15:03:50 <Zakim> +Gwyneth; got it
15:08:34 <aphillip> 
15:08:39 <aphillip> Topic: Minutes and Agenda review
15:09:07 <aphillip> Topic: Action Items
15:09:27 <aphillip> close ACTION-46
15:09:27 <trackbot> ACTION-46 Dump charmod-norm and add disclaimer paragraph, dates, etc. so that we can publish an interim working draft closed
15:09:32 <aphillip> close ACTION-45
15:09:33 <trackbot> ACTION-45 Publish qa-personal-names for wide review closed
15:09:39 <aphillip> reopen ACTION-46
15:09:39 <trackbot> ACTION-46 Dump charmod-norm and add disclaimer paragraph, dates, etc. so that we can publish an interim working draft re-opened
15:10:23 <aphillip> so close on action 56
15:10:37 <aphillip> 	Change 512 to 1024 in the charset declaration article
15:11:12 <aphillip> Figure out how to keep alive open bugs for the html5 LC
15:12:16 <aphillip> Topic: Info Share
15:12:23 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
15:13:36 <aphillip> ACTION: richard: send addison pisa conference materials as draft for IUC presentation
15:13:36 <trackbot> Created ACTION-60 - Send addison pisa conference materials as draft for IUC presentation [on Richard Ishida - due 2011-08-03].
15:14:01 <aphillip> Topic: Media Resources
15:14:10 <aphillip>  http://lists.w3.org/Archives/Public/public-i18n-core/2011JulSep/0022.html
15:14:37 <aphillip>  http://www.w3.org/TR/2011/WD-mediaont-api-1.0-20110712/
15:18:28 <aphillip> ACTION: addison: raise MediaResources issues in tracker and forward to relevant WG
15:18:28 <trackbot> Created ACTION-61 - Raise MediaResources issues in tracker and forward to relevant WG [on Addison Phillips - due 2011-08-03].
15:18:51 <aphillip> Topic: HTML5 REVIEW
15:19:57 <aphillip> richard: polyglot
15:19:59 <aphillip> ...
15:20:01 <r12a> http://www.w3.org/International/track/products/4
15:20:16 <r12a> http://www.w3.org/International/track/issues/58
15:20:30 <r12a> ISSUE-58 
15:20:46 <Zakim> +??P15
15:21:06 <aphillip> zakim, ??P15 is matial
15:21:06 <Zakim> +matial; got it
15:21:28 <matial> matial has joined #i18n
15:21:57 <fsasaki> fsasaki has joined #i18n
15:21:57 <aphillip> since UTF-16 is no longer allowed in polyglot documents, should close
15:22:06 <aphillip> close ISSUE-58
15:22:06 <trackbot> ISSUE-58 In-document declarations always useful closed
15:22:23 <aphillip> http://www.w3.org/International/track/issues/60
15:22:25 <aphillip> ISSUE-60
15:22:32 <r12a> ISSUE-60: Omit the either/or list
15:22:32 <trackbot> ISSUE-60 Omit the either/or list notes added
15:22:39 <aphillip> rewritten, so no longer issue
15:22:40 <Zakim> +??P16
15:23:07 <aphillip> close ISSUE-60
15:23:07 <trackbot> ISSUE-60 Omit the either/or list closed
15:23:24 <aphillip> 	Mention lang and xml:lang
15:23:28 <aphillip> ISSUE-61
15:23:46 <aphillip> richard: done now. <meta> content language now non-conforming
15:23:59 <aphillip> close ISSUE-61
15:23:59 <trackbot> ISSUE-61 Mention lang and xml:lang closed
15:24:07 <aphillip> Case requirements
15:24:10 <aphillip> ISSUE-62
15:24:16 <aphillip> richard: done, considerably rewritten
15:24:22 <aphillip> close ISSUE-62
15:24:22 <trackbot> ISSUE-62 Case requirements closed
15:24:49 <aphillip> richard: went through the bidi list
15:24:52 <aphillip> ... three remaining ones
15:25:17 <aphillip> http://www.w3.org/International/track/products/5
15:25:32 <aphillip> ISSUE-26
15:25:33 <aphillip> Please add support for rb
15:25:47 <aphillip> ISSUE-29
15:25:47 <aphillip> ruby code samples
15:25:55 <aphillip> addison: added to prep?
15:25:59 <aphillip> richard: no, reopened
15:26:15 <aphillip> ISSUE-30
15:26:16 <aphillip> 	Allow utf-16 meta encoding declarations
15:26:20 <aphillip> richard: on-going
15:26:29 <aphillip> .... resolved "wontfix" by hixie
15:27:03 <aphillip> ... good idea to reopen
15:27:46 <aphillip> addison: UTF-16 allowed in HTML documents but can't declare it
15:27:59 <aphillip> richard: BOM used to declare
15:28:30 <aphillip> addison: reopen it!
15:28:52 <aphillip> richard to open bug
15:29:03 <aphillip> ISSUE-32
15:29:04 <aphillip> 	rlo and lro attribute values
15:29:17 <aphillip> richard: "punt"
15:30:40 <aphillip> matial: don't see a lot of use for it; nice to have
15:30:47 <aphillip> close it
15:30:52 <aphillip> close ISSUE-32
15:30:52 <trackbot> ISSUE-32 rlo and lro attribute values closed
15:30:56 <aphillip> ISSUE-34
15:31:00 <aphillip> 	bdo element doesn't leave rendering up to presentation layer 
15:31:31 <aphillip> close in favor of new issue
15:31:38 <r12a> http://www.w3.org/International/track/issues/34
15:31:48 <aphillip> close ISSUE-34
15:31:48 <trackbot> ISSUE-34 bdo element doesn't leave rendering up to presentation layer closed
15:32:09 <aphillip> http://www.w3.org/International/track/products/10
15:32:40 <aphillip> http://www.w3.org/International/track/products/12
15:33:03 <aphillip> ISSUE-76
15:33:06 <aphillip> Clarify 'preferred name' for encodings
15:33:18 <aphillip> http://www.w3.org/International/track/issues/76
15:34:00 <aphillip> richard: when ian says "preferred name" means preferred name in registry if it exists or name at top of entry
15:34:09 <aphillip> ... the former is only 22 items
15:34:16 <aphillip> ... link is missing here
15:34:30 <aphillip> comment accepted
15:34:45 <aphillip> ISSUE-76: comment accepted for HTML5 LC
15:34:46 <trackbot> ISSUE-76 Clarify 'preferred name' for encodings notes added
15:35:03 <aphillip> http://www.w3.org/International/track/products/11
15:35:14 <aphillip> ISSUE-72
15:35:15 <aphillip> BOM as preferred encoding declaration
15:35:30 <aphillip> richard: section that says how to identify encoding
15:35:40 <aphillip> ... one option is BOM and it says "preferred"
15:36:00 <aphillip> ... later there is a note that says we (our WG) recommends the <meta> element
15:36:25 <aphillip> ... (and I started editing our article recommending against BOM)
15:36:38 <aphillip> addison: BOM is evil :-)
15:39:30 <aphillip> ISSUE-72: accepted for Polyglot LC
15:39:30 <trackbot> ISSUE-72 BOM as preferred encoding declaration notes added
15:39:39 <aphillip> ISSUE-73
15:39:41 <aphillip> Case sensitivity of lang
15:40:22 <aphillip> richard: lang in list of attributes that must be lowercase only
15:40:33 <aphillip> ... becuase attributes handled case insensitive?
15:40:35 <r12a> http://www.w3.org/International/track/issues/73
15:41:17 <aphillip> addison: language tags themselves are case insensitive
15:41:32 <aphillip> richard: it's xml:lang that matters to xml processors
15:41:56 <aphillip> ISSUE-73: accepted for Polyglot LC
15:41:56 <trackbot> ISSUE-73 Case sensitivity of lang notes added
15:42:12 <aphillip> ISSUE-74
15:42:13 <aphillip> 	Remove Content-Language meta from polyglot
15:42:24 <aphillip> http://www.w3.org/International/track/issues/74
15:42:35 <aphillip> richard: all this wording about fallbacks
15:43:08 <aphillip> ... so content-language is non-conforming in HTML5 and thus can't be used in polyglot
15:43:25 <aphillip> ... so need to remove from polyglot
15:45:12 <aphillip> richard: 1. can't use C-L meta in polyglot documents (since non-conforming)
15:45:28 <aphillip> ... 2. therefore remove mention of it from fallback description because irrelevant
15:45:52 <aphillip> ISSUE-74: accepted for Polyglot LC
15:45:52 <trackbot> ISSUE-74 Remove Content-Language meta from polyglot notes added
15:46:04 <aphillip> ISSUE-75
15:46:05 <aphillip> 	Section 11 is blank
15:46:08 <aphillip> non-I18N
15:46:18 <aphillip> personal/editorial comment
15:46:24 <r12a> http://www.w3.org/International/track/issues/75
15:47:08 <r12a> ISSUE-137
15:47:09 <r12a> http://www.w3.org/International/track/issues/137
15:47:12 <aphillip> html5 bidi support should be normative
15:48:19 <aphillip> richard: ian to add normative section on bidi rendering
15:49:19 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
15:51:06 <aphillip> http://www.w3.org/International/track/products/10
15:51:33 <aphillip> ISSUE-77
15:51:34 <aphillip> HTTP and defaulting to UTF-16LE
15:51:37 <r12a> http://www.w3.org/International/track/issues/77
15:51:56 <aphillip> If the HTTP header declares the file to be UTF-16BE, which I believe it can, and in which case a BOM should *not* be used, then I think that this would not be true. If the HTTP header declares the file to be UTF-16, then there must be a BOM, so I assume that this is a recovery mechanism if someone does declare UTF-16 in HTTP but omits the BOM. I'd think that some kind of error message would be in order though. 
15:52:31 <aphillip> addison: seems straightforward
15:52:41 <aphillip> ISSUE-77: accepted for HTML5 LC
15:52:41 <trackbot> ISSUE-77 HTTP and defaulting to UTF-16LE notes added
15:52:56 <aphillip> http://www.w3.org/International/track/issues/78
15:52:56 <aphillip> ISSUE-78
15:53:06 <r12a> http://www.w3.org/International/track/issues/78
15:53:14 <aphillip> The spellcheck attribute currently is limited to user-edited text.  It would be useful to have some way of identifying content that should not be spellchecked in an editor or by an automated spellchecking service. It would seem most intuitive to use the same attribute for this, but more carefully distinguish between the case where the user agent is dealing with user editable text and non-user-editable text, if necessary.
15:54:19 <aphillip> addison: so a processing instruction for editing tools??
15:55:13 <aphillip> ... i18n issue? or general?
15:55:56 <aphillip> felix: borderline between ITS and I18N and general
15:56:02 <aphillip> ... think it's important
15:56:14 <aphillip> ISSUE-78: accepted for HTML5 LC
15:56:14 <trackbot> ISSUE-78 Spellcheck should work in editors notes added
15:56:26 <aphillip> ISSUE-79
15:56:27 <aphillip> Multilingual q quote rendering
15:56:34 <aphillip> http://www.w3.org/International/track/issues/79
15:56:47 <aphillip>  It would be useful to add a note to this section to remind readers that the default characters used for quotation marks are set in the default stylesheet[1], and will vary depending on the user's locale and language preferences. But that users may need to override the defaults for text in a particular language, and that they can do so using the quotes property in CSS (http://www.w3.org/TR/CSS21/generate.html#quotes-specify).
15:56:57 <aphillip> addison: think this is a good comment
15:57:18 <aphillip> richard: there is a note that UA's should take language into account
15:57:38 <aphillip> ... language of the UA
15:57:48 <aphillip> addison: but that's wrong... should be language of content
15:58:04 <aphillip> gwyneth: does it take into account spacing (such as french use of NBSP)
15:59:13 <aphillip> ... CSS page doesn't indicate spaces
15:59:37 <aphillip> ISSUE-79: accepted for HTML5 LC
15:59:37 <trackbot> ISSUE-79 Multilingual q quote rendering notes added
15:59:47 <Zakim> -Richard
15:59:48 <aphillip> ISSUE-80
15:59:50 <aphillip> Default rules for the quotes property
16:00:04 <aphillip> http://www.w3.org/International/track/issues/80
16:00:08 <r12a> http://www.w3.org/TR/html5/rendering.html#punctuation-and-decorations
16:00:15 <aphillip> "Rules setting the 'quotes' property appropriately for the locales and languages understood by the user are expected to be present."  How are the locales and languages understood by the user determined? Is this related to the Accept-Language settings of the browser?  I'm assuming that the requirement here is to provide a single default only per browser installation, rather than to provide defaults for text in various languages (which would be a nice plus). If
16:00:19 <aphillip> rrsagent, draft minutes
16:00:19 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
16:00:26 <r12a> zakim, dial richard-home
16:00:26 <Zakim> ok, r12a; the call is being made
16:00:27 <Zakim> +Richard
16:00:31 <Zakim> -Richard
16:00:49 <r12a> uh ?
16:01:07 <r12a> zakim, dial richard
16:01:07 <Zakim> ok, r12a; the call is being made
16:01:09 <Zakim> +Richard
16:01:10 <aphillip> zakim, who is here?
16:01:11 <Zakim> On the phone I see Addison_Phillips, Gwyneth, matial, fsasaki (muted), Richard (muted)
16:01:13 <Zakim> On IRC I see fsasaki, matial, Gwyneth, Zakim, RRSAgent, aphillip, r12a, trackbot
16:01:59 <aphillip> ISSUE-80: accepted for HTML5 LC
16:01:59 <trackbot> ISSUE-80 Default rules for the quotes property notes added
16:03:41 <aphillip> ISSUE-80: should apply rules based on the language of document
16:03:41 <trackbot> ISSUE-80 Default rules for the quotes property notes added
16:05:58 <aphillip> quote shapes based on language of document except potentially using browser language or A-L as an ultimate fallback
16:06:15 <aphillip> ISSUE-80: quote shapes based on language of document except potentially using browser language or A-L as an ultimate fallback
16:06:15 <trackbot> ISSUE-80 Default rules for the quotes property notes added
16:06:23 <r12a> http://www.w3.org/International/track/issues/80
16:06:26 <aphillip> ISSUE-81
16:06:27 <aphillip> Strip other line-terminators?
16:06:35 <aphillip> http://www.w3.org/International/track/issues/81
16:06:48 <aphillip> Where it says:  -- When a user agent is to strip line breaks from a string, the user agent must remove any U+000A LINE FEED (LF) and U+000D CARRIAGE RETURN (CR) characters from that string. --  Should other line-terminators also be included here?
16:08:13 <aphillip> ISSUE-81: accepted for HTML5 LC
16:08:13 <trackbot> ISSUE-81 Strip other line-terminators? notes added
16:08:21 <r12a> http://www.w3.org/International/track/issues/81
16:08:28 <aphillip> ISSUE-82
16:08:30 <aphillip> 	Non-ASCII enumerated values
16:08:41 <aphillip> http://www.w3.org/International/track/issues/82
16:08:50 <aphillip> I realize that the set of "enumerated values" in HTML5 consists strictly of ASCII strings. However, there is no syntactical requirement that this be true. Non-ASCII values could be included into an enumerated value set, in which case, the "ACSII case-insensitive" match may be incomplete. Instead of using "ASCII case-insensitive", could Unicode case-folded matching be defined instead? This is stable, well-defined, and a strict superset of the ASCII case?
16:09:51 <aphillip> addison: somewhat pedantic, may not be worth raising?
16:10:21 <aphillip> ISSUE-82: rejected for LC
16:10:21 <trackbot> ISSUE-82 Non-ASCII enumerated values notes added
16:10:40 <aphillip> close ISSUE-82
16:10:40 <trackbot> ISSUE-82 Non-ASCII enumerated values closed
16:10:42 <aphillip> ISSUE-83
16:10:45 <aphillip> Note about why Gregorian only used
16:10:52 <aphillip> http://www.w3.org/International/track/issues/83
16:11:06 <aphillip> The section describes date values using strictly the Gregorian calendar. As long as the values are strictly internal (as a means of representing incremental or floating time values, cf. our note Working With Time Zones), this doesn't represent a barrier to the use of other calendric systems. Please include a note indicating this so that international users understand why Gregorian is used here.
16:12:14 <aphillip> ISSUE-83: accepted for HTML5 LC
16:12:14 <trackbot> ISSUE-83 Note about why Gregorian only used notes added
16:12:20 <aphillip> ISSUE-84
16:12:21 <aphillip> Representing BCE months
16:12:29 <aphillip> http://www.w3.org/International/track/issues/84
16:12:37 <aphillip> The 'months' definition only handles dates from the (proleptic) Gregorian year 0 in the common era going forwards. There is no way to represent BCE dates. Should there be?
16:14:09 <aphillip> month="1903-10"
16:14:42 <aphillip> gwyneth: need an "era" field?
16:15:14 <aphillip> gwyneth: need to explain this comment more
16:15:37 <aphillip> ISSUE-84: accepted for HTML5 LC
16:15:37 <trackbot> ISSUE-84 Representing BCE months notes added
16:15:54 <aphillip> ISSUE-85
16:15:55 <aphillip> Health warning about converting date to/from incremental time
16:16:13 <aphillip>      The 'date' definition contains no time zone information. It is thus a floating date value and a health warning should be included about converting it to/from incremental time values. 
16:17:20 <aphillip> date="2011-06-28T14:34:55.007"
16:19:17 <aphillip> ISSUE-85: accepted for HTML5 LC
16:19:17 <trackbot> ISSUE-85 Health warning about converting date to/from incremental time notes added
16:19:39 <aphillip> ISSUE-86
16:19:52 <aphillip> 	Option for 1 digit hour
16:20:12 <aphillip> ISSUE-85: mention efforts on JavaScript inclusion of zone info
16:20:12 <trackbot> ISSUE-85 Health warning about converting date to/from incremental time notes added
16:20:25 <aphillip> http://www.w3.org/International/track/issues/86
16:20:33 <aphillip> In parsing a 'time' value, the rule for the hours section is: "Two digits, representing hour, in the range 0 ≤ hour ≤ 23". Should this optionally allow only one digit?
16:20:51 <aphillip> richard: actually tripped over this
16:21:33 <aphillip> time="0:00:00"
16:22:07 <aphillip> ISSUE-86: accepted for HTML5 LC
16:22:07 <trackbot> ISSUE-86 Option for 1 digit hour notes added
16:22:42 <aphillip> ISSUE-86: many users will make this error and the result will be an error rather than a time
16:22:42 <trackbot> ISSUE-86 Option for 1 digit hour notes added
16:22:55 <aphillip> ISSUE-87
16:22:56 <aphillip> Leap seconds
16:23:04 <aphillip> http://www.w3.org/International/track/issues/87
16:23:14 <aphillip> There is a note disallowing the representation of leap seconds. This poses a potential problem for applications sensitive to leap seconds. Should the values be allowed, even if later processing does not deal with it?
16:24:08 <Gwyneth> The International Earth Rotation And Reference Systems Service (IERS) Earth Orientation Center is taking comments on whether to get rid of leap seconds. http://hpiers.obspm.fr/eop-pc/index.php?index=questionnaire
16:24:09 <aphillip> datetime="1980-01-01T00:00:60"
16:25:27 <aphillip> ISSUE-87: accepted for HTML5 LC
16:25:28 <trackbot> ISSUE-87 Leap seconds notes added
16:25:39 <aphillip> ISSUE-88
16:25:40 <aphillip> 	Local/floating date and time
16:25:53 <aphillip> 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.
16:27:25 <aphillip> ISSUE-88: accepted for HTML5 LC
16:27:25 <trackbot> ISSUE-88 Local/floating date and time notes added
16:27:37 <aphillip> ISSUE-89
16:27:38 <aphillip> 	Time zones and local dates and times
16:27:44 <Gwyneth> I need to head out to another meeting. Sorry.
16:27:47 <Zakim> -Gwyneth
16:27:47 <aphillip> http://www.w3.org/International/track/issues/89
16:27:54 <aphillip> This section defines 'local dates and times', which is a date-and-time value *without* a time zone. This type seems problematic because it does not deal with the time zone problem. Its relationship to either floating or incremental times is completely arbitrary. See also Issue 88.
16:30:42 <aphillip> addison: so have more understanding... modeling JS Date(). There are use cases like airline schedules where useful. Question is about giving good guidance to authors.
16:31:21 <aphillip> ... call for a health warning related to time zones?
16:31:54 <aphillip> ISSUE-89: update to call for health warning on use of local dates and times
16:31:54 <trackbot> ISSUE-89 Time zones and local dates and times notes added
16:32:06 <aphillip> ISSUE-89: accepted for HTML5 LC
16:32:06 <trackbot> ISSUE-89 Time zones and local dates and times notes added
16:32:46 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
16:33:29 <aphillip> ISSUE-91
16:33:30 <aphillip> 	15 minute time zones
16:33:36 <aphillip> http://www.w3.org/International/track/issues/91
16:33:44 <aphillip> The note on time zone offsets says in part: "...and the minutes component of offsets of actual time zones is always either 00, 30, or 45." Really this is arbitrary and prone to change. The total range of time zones also changes from time to time. I would suggest inserting a "at the time this document was published" caveat such that innocent readers are not caught by surprise by a new 15 mintue time zone offset or by more monkey business surrounding the IDL.
16:34:29 <aphillip> ISSUE-91: accepted for HTML5 LC
16:34:29 <trackbot> ISSUE-91 15 minute time zones notes added
16:34:38 <aphillip> ISSUE-92
16:34:40 <aphillip> Time zone offset vs. time zone
16:34:47 <aphillip> http://www.w3.org/International/track/issues/92
16:34:58 <aphillip> This section gives a number of examples that equate time zone offset with an actual time zone. For example:  -- "1979-10-14T12:00:00.001-04:00" One millisecond after noon on October 14th 1979, in the time zone in use on the east coast of the USA during daylight saving time. --  It should be made clear that a zone offset is not the same thing as a time zone. Mention should be made of the need for separate time zone information when working with real date and t
16:36:00 <aphillip> ISSUE-92: accepted for HTML5 LC
16:36:00 <trackbot> ISSUE-92 Time zone offset vs. time zone notes added
16:36:12 <aphillip> ISSUE-93
16:36:13 <aphillip> http://www.w3.org/International/track/issues/93
16:36:20 <aphillip> implicit conversion to incremental time
16:36:28 <aphillip> Rule 9 in the parsing of a valid global date and time is: "Let time be the moment in time at year year, month month, day day, hours hour, minute minute, second second, subtracting timezonehours hours and timezoneminutes minutes. That moment in time is a moment in the UTC time zone.". It is not clear what type 'time' is. It appears to be a field-based time value, but it this intended as an implicit conversion to incremental time?
16:37:24 <aphillip> ISSUE-93: accepted for HTML5 LC
16:37:24 <trackbot> ISSUE-93 Implicit conversion to incremental time? notes added
16:37:39 <aphillip> ISSUE-94
16:37:40 <aphillip> http://www.w3.org/International/track/issues/94
16:37:48 <aphillip> Allowing culturally specific week rules
16:37:56 <aphillip> This section defines 'weeks'. The rules for weeks and week counting are culturally linked, but these rules define week start as always Monday. The rule for determining the "first week" that it includes the first Thursday (again, a culturally variant value). Shouldn't there be provision for allowing culturally specific week rules be applied?
16:38:21 <matial> definitely
16:38:29 <aphillip> ISSUE-94: accepted for HTML5 LC
16:38:29 <trackbot> ISSUE-94 Allowing culturally specific week rules notes added
16:40:30 <aphillip> ISSUE-95
16:40:32 <aphillip> http://www.w3.org/International/track/issues/95
16:40:40 <aphillip> Limitations and defaults for accept-charset
16:40:48 <aphillip> The "accept-charset" field is said to "gives the character encodings that are to be used for the submission". Is this a real limitation on the encodings used? Is there a default value (presumably the page encoding)?
16:42:31 <aphillip> http://www.w3.org/TR/html5/forms.html#the-form-element
16:42:47 <aphillip> present for backward compatibility?
16:42:59 <aphillip> ISSUE-95: accepted for HTML5 LC
16:42:59 <trackbot> ISSUE-95 Limitations and defaults for accept-charset notes added
16:43:12 <aphillip> ISSUE-96
16:43:25 <aphillip> Allowing for EAI
16:43:27 <r12a> http://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=ian%40hixie.ch&emailtype2=substring&email2=&bugidtype=includ
16:43:27 <r12a> _id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
16:43:29 <aphillip> The email address validation scheme quotes ABNF from RFC 5322 and doesn't appear to allow addresses that are IDNA. While EAI is kinda slow moving, shouldn't HTML5 allow for it?
16:44:07 <r12a> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11579
16:44:13 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
16:44:18 <r12a> Support for internationalized e-mail addresses
16:44:58 <aphillip> ISSUE-96: add this issue to HTML5 bug 11579
16:44:58 <trackbot> ISSUE-96 Allowing for EAI notes added
16:45:16 <aphillip> ISSUE-97
16:45:16 <aphillip> Allowing a page to request a given locale
16:45:25 <aphillip> http://www.w3.org/International/track/issues/97
16:45:33 <aphillip> -- The format shown to the user is independent of the format used for form submission. Browsers are encouraged to use user interfaces that present dates and times according to the conventions of the user's preferred locale. --  Should we encourage the use of the *page's* preferred locale? It would be best if we could provide a way for page authors to create a consistent user experience. Work on the ECMAScript I18N extension may eventually help here, but only 
16:49:32 <aphillip> matial: provide authors ability to override user's preferences, but user's preferences should work in absense of an override
16:49:52 <aphillip> ISSUE-97: accepted for HTML5 LC
16:49:53 <trackbot> ISSUE-97 Allowing a page to request a given locale notes added
16:51:43 <aphillip> ACTION: addison: write to HTML5 chairs and ask for extension to complete our comments targetting mid-August (??)
16:51:43 <trackbot> Created ACTION-62 - Write to HTML5 chairs and ask for extension to complete our comments targetting mid-August (??) [on Addison Phillips - due 2011-08-03].
16:56:13 <aphillip> close ISSUE-128
16:56:13 <trackbot> ISSUE-128 Why is content-language non-conforming? closed
16:56:40 <aphillip> ACTION: addison: file accepted as accepted and unreviewed comments as provisional
16:56:40 <trackbot> Created ACTION-63 - File accepted as accepted and unreviewed comments as provisional [on Addison Phillips - due 2011-08-03].
16:57:13 <Zakim> -Addison_Phillips
16:57:15 <Zakim> -Richard
16:57:19 <Zakim> -fsasaki
16:57:19 <aphillip> rrsagent, make minutes
16:57:19 <RRSAgent> I have made the request to generate http://www.w3.org/2011/07/27-i18n-minutes.html aphillip
16:57:36 <aphillip> zakim, bye
16:57:36 <Zakim> leaving.  As of this point the attendees were Addison_Phillips, Richard, Gwyneth, matial, fsasaki
16:57:36 <Zakim> Zakim has left #i18n
16:57:43 <aphillip> rrsagent, bye
16:57:43 <RRSAgent> I see 4 open action items saved in http://www.w3.org/2011/07/27-i18n-actions.rdf :
16:57:43 <RRSAgent> ACTION: richard: send addison pisa conference materials as draft for IUC presentation [1]
16:57:43 <RRSAgent>   recorded in http://www.w3.org/2011/07/27-i18n-irc#T15-13-36
16:57:43 <RRSAgent> ACTION: addison: raise MediaResources issues in tracker and forward to relevant WG [2]
16:57:43 <RRSAgent>   recorded in http://www.w3.org/2011/07/27-i18n-irc#T15-18-28
16:57:43 <RRSAgent> ACTION: addison: write to HTML5 chairs and ask for extension to complete our comments targetting mid-August (??) [3]
16:57:43 <RRSAgent>   recorded in http://www.w3.org/2011/07/27-i18n-irc#T16-51-43
16:57:43 <RRSAgent> ACTION: addison: file accepted as accepted and unreviewed comments as provisional [4]
16:57:43 <RRSAgent>   recorded in http://www.w3.org/2011/07/27-i18n-irc#T16-56-40