See also: IRC log
<scribe> Scribe: JR
JA: Not able to get to his action items.
<jallan> http://www.w3.org/2006/08/10-ua-minutes.html last minutes
JR: Not done either
<scribe> ACTION: JA to Contact Judy Brewer about IBM having a third rep on UA [recorded in http://www.w3.org/2006/08/24-ua-minutes.html#action01]
JA: Noticed no techniques for 6.1, 6.2, 6.4
JR: In 6.1, Write req given a lot of spac in notes.
PP: Do any AT's write to the infoset?
JA: Don't know of any.
PP: Defintion of infoset just seems to describe XML
PP: COuldn't UA conform by just handing over the HTML doc...
JR: Write req. seems to imply a centralized place for it
JA: Does this have to do with
... CL can you ask Rich about implications of 6.1 - is AJAX related?
<scribe> ACTION: CL to ask Rich about implications of 6.1 - is AJAX related? [recorded in http://www.w3.org/2006/08/24-ua-minutes.html#action02]
JA: Is DOM3 a rec?
... Yes according to W3 site.
JR: Still a P1?
<jallan> dom 3 http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/
CL: Trend may be moving from DOM to access API (DOM info coming through access API's)
<jallan> for assitive technologies
PP: In Linux world, get info
through Accessibility API, not DOM.
... IN windows world AT's go back and forth.
CL: HPR using DOM
... So browser has DOM, but exposed differently on diff platforms
<jallan> AT can use accessibility API or use browser DOM
CL: 6.2 already mentions multiple ways to get to the DOM
<jallan> What level of DOM implementation on current browsers?
e.g. In the Java and ECMAScript operating environments, export the normative bindings specified in the DOM Level 2 Core Specification
scribe: In other operating environments, the exported bindings (e.g., C++) must be publicly documented.
<jallan> how will changing to DOM3 impact compliance
<scribe> ACTION: JA to Review implementation report to see who complies with 6.2 [recorded in http://www.w3.org/2006/08/24-ua-minutes.html#action03]
JA: Lst sentence of Note 1 looks like a technique.
JA's action is COMPLETE - all are noted as complete.
JA: iSimpleDOMnode(sp?) is interface to query using DOM calls
actually was PP
CL: IMportatn because MSAA didn't give good even access to attributes
<parente> see heading "MSAA tree vs. DOM tree - what's the relation?"
JA: Pull last sentence out as a tech "Developers should therefore use commonly available operating system supported interprocess communication features (such as semaphores) to ensure synchronized, thread-safe access.
<jallan> cl: js or xul in Firefox can write to dom
iSimpleDOMnode can only read
<jallan> ACTION: JA add xul url to references "Writing to DOM in Firefox using XUL" [recorded in http://www.w3.org/2006/08/24-ua-minutes.html#action04]
JA: Just saying use published
... Weird technique
PP: Just a statement of fact
JA: SHould we have ODF mentionned in Notes and Rationale
<parente> Uno ^
CL: Do AT's go to Uno?
PP: No - it's OpenOffice's API, not for the dpocument in particular
JA: Browser nedds plugins for these formats...
CL Browser is container for plugin
JAL Like when PDF opens in browser
CL: Flash access is IE-specific
... XPcom is a kind of Com intercae specific to Firefox
JA: Let's defer this one.
... Till F2F?
PP: ATSPI could be added as well to techs.
<parente> UNO reference: http://udk.openoffice.org/
<parente> XPCOM reference: http://www.mozilla.org/projects/xpcom/
<jallan> ACTION: JA: add uno reference, and XPCOM. expand #2 atk to be atk/atspi [recorded in http://www.w3.org/2006/08/24-ua-minutes.html#action05]
JA: Let's stop there
This is scribe.perl Revision: 1.127 of Date: 2005/08/16 15:12:03 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: JR Inferring ScribeNick: JR Default Present: Jim_Allan, Jan_Richards, parente, cklaws Present: Jim_Allan Jan_Richards parente cklaws Regrets: Charles M Got date from IRC log name: 24 Aug 2006 Guessing minutes URL: http://www.w3.org/2006/08/24-ua-minutes.html People with action items: 2 add atk cl expand ja reference uno url xpcom. xul WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]