See also: IRC log
<scribe> Scribe: Steven
Charlie: Let's get feedback, and I will produce a release candidate this week
Jack: One week in the XG, what happens then?
Charle: The phone bridge, and IPR
expire
... other XGs have published in their charter period
[Discussion of TPAC]
Charlie: If we emphasise in the
patterns part of the paper, the role of the different
markups
... surface them as a formats issue
<John_Boyer> Minor edit: last paragraph of intro, "XML-based architectures" should probably be "XML-based markup formats"
Charlie: ... these are not abstract patterns but use cases
Steven: May be more grounded for the planned readership
John: The W3C seems to want to describe the web as what current browsers do, so the scripting bit is importnant
Charlie: I wonder if we should
make the point more strongly that scripting is not yet fully
interoperable
... we don't yet have a technical direction
... there, but we might want to emphasise the point
John: There are two ways of decorating a page, one with javascript, the other is to inject more DOM nodes
Charlie: We do both
John: People who care about
strict conformance, will start looking at runtime DOMs
... in Dojo you can inject elements, that cause more Dojo
elements to be inserted, so that the DOM is no longer
'valid'
... some people care about that
Charlie: Standardisation may be
necessary on the lifecycle of the document
... and how the DOMs get extended
... we shouldn't care *what* does it
... I use Dojo in 4.2 as an example
John: Another candidate example,
is focusin vs DOMfocusin
... in Ubiquity we produce web-based input elements from the
Forms input element
... but what has the focus?
... is there only one DOM?
Charlie: The issue arises in Dojo too
<John_Boyer> there's the source document that I think about when authoring the app, so I want to write event handlers, e.g. DOMFocusIn, relative to xf:input, but an xf:input gets decorated with a web input, which receives the "focusin"
<John_Boyer> so two things have the focus, technically
Steven: I think the issue is the same as in compilation
as long as you get the right user experience according to the input code, all is fine
Charlie: Would you like to add to section 4.7 on Standardisation?
Steven: If there were a WG, that would be what it did. Do you want more sketched out?
<wiecha> http://www.amplesdk.com/reference/#/ample/overview/lifetime.xml
Charlie: We could abstract from
the example given in the link
... I will push on other parts of section 4
... Jack, John, any bits you want to own?
... SMIL?
Jack: Which should I write?
Charlie: 5.5.1
Jack: I'll look through it
Charlie: I'm working on the diagrams
Steven: I can help if you send me some sketches
[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) Succeeded: s/publish/have published/ Succeeded: s/uii/i/ Succeeded: s/AN/An/ Succeeded: s/iad/ida/ Succeeded: s/arrived/arises/ Succeeded: s/given/given / Found Scribe: Steven Inferring ScribeNick: Steven Default Present: wiecha, +1.250.294.aaaa, John_Boyer, Steven, Jack Present: wiecha +1.250.294.aaaa John_Boyer Steven Jack Agenda: http://lists.w3.org/Archives/Public/public-xg-app-backplane/2009Sep/0012.html Got date from IRC log name: 29 Sep 2009 Guessing minutes URL: http://www.w3.org/2009/09/29-backplane-minutes.html People with action items:[End of scribe.perl diagnostic output]