[I18N Core] Teleconference Minutes 2005-02-22

Present: Addison (chair, scribe), Martin, Richard, Mary, François
Regrets: Tex

ACTION ITEMS:
AP: revise SVG message and look at it again.  (IP) 
AP: remind people to get AC Reps to sign them up. (and again...) 
AP: Send list of current outstanding reviews  
RI: ping GEO about doing some reviews. Possibly the ATAG 2.0 review. 
AP: send updated BTIX comments 

(ACTUAL) AGENDA 
  
 1. Action Items (5 minutes) 
 2. Announcements (5 minutes) 
 3. Review Radar status report (10 minutes) 
 4. Review: Binary Types in XML
 5. Encodings in XHTML discussion (15 minutes)

 [14:06] apphillips: action items
[14:06] apphillips: AP: follow up with Jeremy  (done) 
 AP: revise SVG message and look at it again.  (IP) 
  (someone): bring a microphone so we can use Skype as a backup for TechPlenary 
 AP: remind people to get AC Reps to sign them up. (and again...) 
 AP: Send list of current outstanding reviews   (done 050209)  
 RI: ping GEO about doing some reviews. Possibly the ATAG 2.0 review. 
 MD + AP: Look at Binary Data in XML 
 AP: write a response for review by list 
 (all): send any comments about the encoding thread by tomorrow morning London time (richard's day)

[14:08] apphillips: http://lists.w3.org/Archives/Public/public-i18n-core/2005JanMar/0069.html

[14:10] apphillips: Richard to speak to Stephen Pemberton about the problems with the encoding discussion.
 [14:13] apphillips: ---
[14:14] apphillips: Announcements
[14:14] apphillips: - new page on the site (techniques index)
[14:14] r12a: http://www.w3.org/International/technique-index

[14:15] apphillips: - site search field (within the I18n site)
[14:17] apphillips: ---
[14:17] apphillips: http://www.w3.org/International/core/reviews

[14:20] apphillips: http://lists.w3.org/Archives/Public/public-i18n-core/2005JanMar/0069.html

[14:22] apphillips: 1. section 2.2, "expectedMediaType attribute": is set up to describe an "Accept" header, complete with q (quality) values. Accept-extensions are explicitly not permitted. This has important meaning for us: it means no charset parameter is permitted. Of course, there is the question of whether it makes sense for the expected media type to be constraining the encoding, but it is something that bears consideration.
[14:25] apphillips: 2. section 3. "Declaring media type for binary data": there are two examples (one is image/png and the other is text/xml;charset=utf-16). The XML example is good, in that it uses a charset parameter. 
  
   a. There should be mention that the charset parameter for text/* types is REQUIRED similar to that in the other binary XML documents. 
  
   b. There should probably be an example of the charset parameter in use. The examples (quite properly) use a binary image as an example, but it is entirely probable that this mechanism will be used to send content such as HTML or XML documents too.
[14:29] apphillips: (a should read STRONGLY RECOMMENDED)
[14:32] apphillips: 3. General observation: this document provides a way to indicate a specific preference for a media type using the expectedMediaType attribute, but doesn't specify other interesting Accept-* meta information. For example, there is no way to specify a specific language (accept-language) or encoding (accept-charset) for that same content. It might be wise to include that information in this specification and not require users to invent their own mechanisms for these items.
[14:36] apphillips: maybe match "expected" prefix.
[14:40] apphillips: text/plain
[14:43] apphillips: collapse 1 and 3 into one comment
[14:44] apphillips: prefix uses xmlmime (xml is reserved)
[14:45] apphillips: prefix is illegal
[14:45] apphillips: make it "mimexml" or something
[14:48] apphillips: adopted with changes
[14:48] apphillips: ----
[14:51] * apphillips 3 March IESG date for telechat
[14:51] apphillips: encoding discussion
[14:57] apphillips: break tag in hebrew issue

Addison P. Phillips
Globalization Architect, Quest Software
http://www.quest.com


Chair, Internationalization Core Working Group
http://www.w3.org/International


Internationalization is not a feature.
It is an architecture.

Received on Wednesday, 23 February 2005 00:10:13 UTC