<trackbot-ng> Date: 13 February 2008

<John_Boyer> Meeting: Weekly Forms WG Teleconference

<Steven> already done john

<John_Boyer> Scribe: Leigh

<Steven> Regrets fornext week from me: XHTML2 WG FtF

<John_Boyer> scribenick: klotz

<Steven> In Venice...

<Charlie> Regrets for me as well for next week

<Steven> And presumably regrets for MarkB

<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Feb/0046.html

<Steven> Regrets from MarkB for today too

<John_Boyer> http://lists.w3.org/Archives/Public/public-forms/2008Feb/0037.html

<nic1> not all changes

<nic1> only a few changes are back-ported

<nic1> ack, me

<nic1> he mechanism for encoding character code points into bit patterns MAY vary from entity to entity. All XML processors MUST accept the UTF-8 and UTF-16 encodings of Unicode 3.1 [Unicode3]; t

<nic1> Character Range[2]   Char   ::=   #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]/* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */

<nic1> http://www.w3.org/TR/2004/REC-xml-20040204/#charsets

<nic1> new version : http://www.w3.org/TR/2008/PER-xml-20080205/#charsets

<nic1> doesn't points to a certain version of unicode

<nic1> personally not happy with the change from a technical point of view, but I understand it from business point of view

RESOLUTION: We respond to say that we have no objections to XML 1.0 PER 5.

<scribe> ACTION: Leigh Klotz to respond on behalf of Forms WG to say that we have no objections to XML 1.0 PER 5. [recorded in http://www.w3.org/2008/02/13-forms-minutes.html#action01]

<trackbot-ng> Created ACTION-452 - Klotz to respond on behalf of Forms WG to say that we have no objections to XML 1.0 PER 5. [on Leigh Klotz, Jr. - due 2008-02-20].

<John_Boyer> 28http://www.w3.org/MarkUp/Forms/wiki/XForms_Future_Features#head-c6aaca91edf26a8918c6e59784a9de3f747e1f94 <http://www.w3.org/MarkUp/Forms/wiki/XForms_Future_Features>

<John_Boyer> http://www.w3.org/MarkUp/Forms/wiki/XForms_Future_Features#head-c6aaca91edf26a8918c6e59784a9de3f747e1f94

<nic1> it is only in XUpdate that you can change data

<nic1> and there it is quite limited what you can do

<nic1> But if Erik wants to create an AVT module, I think we shouldn't stop him of doing that...

<nic1> It is just another module

<ebruchez> Sure, but for a given feature, you do want working group support

If there is a way to express the effect of AVTs as self-modifying documents then there is likely a way to programmatically transforma AVT {}'s into equivalent AVT-free self-modifying markup.

john see http://www.w3.org/MarkUp/Forms/wiki/FrontPage

Is there someone willing to champion the 1.2 release pattern for wizards?

<Steven> yes

<ebruchez> I have to go, bye bye

<nic1> bye

This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Leigh
Found ScribeNick: klotz

WARNING: No "Topic:" lines found.

Default Present: John_Boyer, wellsk, Charlie, Steven, Nick_van_den_Bleeken, Susan_Borgrink, klotz, ebruchez, unl, +03491211aaaa, Roger
Present: John_Boyer wellsk Charlie Steven Nick_van_den_Bleeken Susan_Borgrink klotz ebruchez unl +03491211aaaa Roger
Agenda: http://lists.w3.org/Archives/Public/public-forms/2008Feb/0046.html
Found Date: 13 Feb 2008
Guessing minutes URL: http://www.w3.org/2008/02/13-forms-minutes.html
People with action items: klotz leigh

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report