See also: IRC log
Mark: I nominate Steven as Chair
Yam: Second
<scribe> ACTION: [NEW] Alessio to test 'popular' browsers on whether an access element in the head of a document turns up in the DOM [recorded in http://www.w3.org/2007/05/30-xhtml-minutes.html#action01]
Alessio: I have tested this with IE and another
test with Firefox etc.
... I will send a mail with the URL and so on
<scribe> ACTION: Alessio to send mail with details of DOM test [recorded in http://www.w3.org/2007/05/30-xhtml-minutes.html#action02]
Steven: Schema comments
<ShaneM> http://www.w3.org/TR/html4/present/graphics.html#adef-color-FONT
<ShaneM> http://www.w3.org/Graphics/Color/sRGB
Steven: I think the color data type can only be
6 digits
... a 3 digit value is only allowed in CSS
... http://www.w3.org/TR/html401/types.html#h-6.5
Shane: But browsers accept 3 digits now
Steven: But maybe not all of them
... then we would break an existing browser
... that had been conformant up til now
... Presumably current vrowsers have taken the rule from CSS, not HTML
... but since HTML says just "a hexadecimal number", then #1 would be OK, and
would mean #000001
... (unfortunately)
... so my conclusion is that we should make the data type #[0-9]+ just so we
don't break any existing content
Shane: You're right
<ShaneM> oh - the datatype should be #[0-9A-F]+
Steven: I think there is value to defining the coord type, since you would get some value from the schema processor telling you about wrong values
Shane: Agree
Steven: Now the issue of Substitution groups
Mark: It would be too much work now
... let us say we will do it in a revisions
Shane: Agree, but there is also a restriction
about substitution groups, that gets in our way
... (which I don't recall the details of right now)
Mark: Not sure if it would be a problem.
Here is the document we are discussing: http://lists.w3.org/Archives/Public/www-html-editor/2007JanMar/0035.html
Steven: I propose that we say we want to do it ain a future version, and will be happy to work with them
<scribe> ACTION: Steven to reply to Schema WG on M12N comments [recorded in http://www.w3.org/2007/05/30-xhtml-minutes.html#action03]
<ShaneM> Coords data type: here is what they proposed:
<ShaneM> <xsd:simpleType name="Coords.rect">
<ShaneM> <xsd:restriction base="xsd:token">
<ShaneM> <xsd:pattern value="(&Length;&Comma;){3}(&Length;)"/>
<ShaneM> </xsd:restriction>
<ShaneM> </xsd:simpleType>
<ShaneM> <xsd:simpleType name="Coords.circle">
<ShaneM> <xsd:restriction base="xsd:token">
<ShaneM> <xsd:pattern value="(&Length;&Comma;){2}(&Length;)"/>
<ShaneM> </xsd:restriction>
<ShaneM> </xsd:simpleType>
<ShaneM> <xsd:simpleType name="Coords.poly">
<ShaneM> <xsd:restriction base="xsd:token">
<ShaneM> <xsd:pattern value="(&Pair;&Comma;){2,unbounded}(&Pair;)"/>
<ShaneM> </xsd:restriction>
<ShaneM> </xsd:simpleType>
Steven: Not enough people could come to the FtF at this short notice, so there will be no meeting in NY in June; the next FtF is September 10-11 in Madrid Spain. Please plan to be there.
<yamx> My understanding is there is some difference between XHMLMP1.2 and XHTMLBasic 1.1.
<yamx> My question is how serious the gap is for W3C.
Steven: So the call for CR is going to go ahead.
Yam: How will the W3C interpret the exit criteria?
<yamx> OMA's position is the gap analysis for W3C exit criteria is taken by W3C.
Steven: Normally there must be two interoperable implementations, and I thought OMA were doing the test suitte
Yam: We? Oh. I will check
Steven: That was my understanding
Shane: There is only one thing that is really
new in 1.1, and that is the inputmode attribute
... so we should be nearly there. That is the only thing that really needs
testing
Yam: If Inputmode is tested in OMA, then W3C is OK?
Steven: Yes
... since Basic 1.1 is a subset of what you are testing, with the exception
of inputmode
<scribe> ACTION: Yam to check on the status of test materials from OMA [recorded in http://www.w3.org/2007/05/30-xhtml-minutes.html#action04]
Steven: It is even possible for the CR period to be zero-length, if the exit criteria are met early enough
Alessio: I have sent my report: http://lists.w3.org/Archives/Public/public-xhtml2/2007May/0023
Rich: What do you use in IE to see what is in the DOM?
Alessio: I use a toolbar
... it is a plugin
Steven: What was the question we were trying to answer with this?
Shane: Whether we could add the access to XHTML
1.2 and get it to work, and not blow up existing browsers
... it looks like it is OK
[ADJOURN]
This is scribe.perl Revision: 1.128 of Date: 2007/02/23 21:38:13 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 0.97) Succeeded: s/St// Succeeded: s/moe/mode/ Succeeded: s/IT/It/ Found Scribe: Steven Inferring ScribeNick: Steven Default Present: Steven, Mark_Birbeck, +04670855aaaa, Tina, Rich, ShaneM, Alessio, Yamx Present: Steven Mark_Birbeck +04670855aaaa Tina Rich ShaneM Alessio Yamx Regrets: Susan Agenda: http://lists.w3.org/Archives/Public/public-xhtml2/2007May/0020 Got date from IRC log name: 30 May 2007 Guessing minutes URL: http://www.w3.org/2007/05/30-xhtml-minutes.html People with action items: alessio steven yam[End of scribe.perl diagnostic output]