See also: IRC log
<trackbot> Date: 23 September 2009
<scribe> Scribe: Steven
Shane: I updated the three specs
in the drafts area
... and produced a DoC for 1.1
... the other two had no issues
http://www.w3.org/MarkUp/Drafts/
<ShaneM> XHTML 1.1 draft DoC is at http://htmlwg.mn.aptest.com/htmlwg/xhtml11-per-doc-20090916.html
http://www.w3.org/MarkUp/2009/ED-xhtml11-20090916/
http://www.w3.org/MarkUp/2009/ED-xhtml-basic-20090916/
http://www.w3.org/MarkUp/2009/ED-xhtml-print-20090916/
Steven: Did we set all version of XML? Did we set them all to 4?
Shane: Yes, because M12N uses that, and v5 changes normative requirements wrt name tokens
Steven: Let's just check the
Rejects in the DoC
... they look OK
... I think then that that means we are ready to go
... but I'd like the group to have time to look at the docs,
till the end of the week?
Shane: Sure
Steven: And then I'll contact Ralph and plh to let them look at the docs before I formally ask for transition
s/SN/Sn/
Steven: Are there any more issues wrt the PERs?
http://lists.w3.org/Archives/Public/public-forms/2009Jul/0008.html
RRSAgent`Steven: As we talked about last week, they are taking out namespaced events
scribe: we'd be planning on that
anyway
... and nobody depends on them
... Mark has pointed out that you could still have namespaced
events in the syntax, and map them to the API if wanted
... but the other part is that they are deprecating (most of)
the DOM* events, like DOMActivate
... and I don't really understand why.
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
Shane: Do they have replacements?
Steven: I think so
... Sorry, it's not DOMActivate, that has been retained
... but DOMFocusIn for instance
Shane: From XML Events2, we don't care
Steven: I think it only
indirectly affects us, via XForms
... and we can leave the discussions to them
Shane: We should press forward with the update to M12N 1.1
Steven: Are they all issues in the DB?
Shane: I'll create an issues
doc
... and post it
Tina: I would like to discuss
before December what we will do with @version
... and how to determine if it is XHTML2
... I do an automated testing tool
<ShaneM> didn't we agree to use @version ?
Tina: and we test based on the language
Shane: Then it is in the DOM
Tina: That's all I need
Steven: Do we have a problem with using a new namespace?
Tina: They don't use the namespace for identification
Steven: They might one day
... browsers do do some sniffing
... we should do some experiemtns
Tina: We still need to be able to identify a document as XHTML2
Steven: Yes, especially if you are going to server-side process it
[ADJOURN]
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) FAILED: s/SN/Sn/ Succeeded: s/AN/An/ Succeeded: s/SD/S/ Succeeded: s/TH/Th/ Found Scribe: Steven Inferring ScribeNick: Steven Default Present: McCarron, Tina, Steven, ShaneM Present: McCarron Tina Steven ShaneM Regrets: Alessio Agenda: http://lists.w3.org/Archives/Public/public-xhtml2/2009Sep/0021 Found Date: 23 Sep 2009 Guessing minutes URL: http://www.w3.org/2009/09/23-xhtml-minutes.html People with action items:[End of scribe.perl diagnostic output]