W3C home > Mailing lists > Public > www-forms-editor@w3.org > July 2002

Re: Response to your issue sent to the XForms WG about the XForms Last Call WD

From: François Yergeau <francois@yergeau.com>
Date: Tue, 30 Jul 2002 16:06:24 -0400
Message-ID: <3D46F1C0.70408@yergeau.com>
To: Thierry Michel <tmichel@w3.org>
CC: www-forms-editor@w3.org

Hello Thierry,

The i18n WG today considered your responses to our issues about the 
XForms Last Call WD http://www.w3.org/TR/2002/WD-xforms-20020118/
.

Thierry Michel wrote:

> Your issue is archived at
> http://lists.w3.org/Archives/Public/www-forms-editor/2002Feb/0058.html
> 
> XForms WG Resolution:
> 
> Point 1: we're doing c) namely moving to the end of the submission methods
> (now 11.7). We have mandated UTF8 encoding. We have not deprecated these
> methods.


This is satisfactory, given the necessity to have a way to use HTTP GET 
with its special semantics.  We have an issue about the example given in 
this section (now 11.5, apparently), see point 4 below.


> Point 2. Agree, but solved in a different way (spec change)


Nicely done, we are satisfied.  Note a typo "implemnetation" in that 
section (11.4).


> Point 3. Agree.


Thank you.


> Point 4. Agree.


Really?  This is hard to see in the current draft (we looked at 
http://www.w3.org/MarkUp/Forms/Group/Drafts/Sources/index-all.html dated 
29 July 2002).

In this point we asked 'Please make examples better internationalized 
(for instance change "First name" to "Given name").'  But the example in 
11.5 uses a <FirstName> element!  And since the problem we had with 
application/x-www-form-urlencoded was precisely one of charset, it would 
be wise to have some non-ASCII characters to illustrate the 
serialization in a more meaningful way.  We suggest that you change the 
example to:

Instance data:

  <PersonName title="Mr">
    <GivenName>René</GivenName>
  </PersonName>

application/x-www-form-urlencoded:

  GivenName=Ren%c3%a9;


We also requested:

'Please include an example showing that the same model can be used with
different user interfaces in different languages (fields laid out in
different order, fields that appear in a certain language version of the
form but not in some other, e.g. "state/province", labels in different
language than content).'

Richard Ishida later sent a worked out example. We can see no trace of 
this example or anything like what we requested in the current spec (but 
we haven't scoured it thoroughly).  Can you please point us to the right 
spot?



We have also reviewed your response to Martin Dürst's comments, which 
were actually i18n comments 
(http://lists.w3.org/Archives/Member/w3c-i18n-ig/2002Jul/0025.html)

 >Your issue is archived at
 >http://lists.w3.org/Archives/Public/www-forms-editor/2002Feb/0100.html
 >
 >XForms WG Resolution:
 >
 >
 >1) Agree. We have added a note about the i18n benefits of xsd:anyURI.

We could not locate the note in question, can you please help us?

 >2) Your comment had no specific suggestion... This is a host-language 
 >issue.

OK, no objection to this resolution.

 >3) Agreed. We now include an example of "calendar" date entry

Thanks.

 >4) Agree. boolean-from-string() has been changed as suggested.

Thanks again.


Regards,

-- 
François Yergeau
for the i18n WG
Received on Tuesday, 30 July 2002 16:07:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 June 2009 18:12:11 GMT