See also: IRC log
<Steven> hi
<scribe> scribe: John_Boyer
<wiecha> http://www.amplesdk.com/examples/svg/dynamic/
Charlie: other js implementations
of W3C specs
... xg report should accentuate the "ubiquity" movement of
using js on the client
... they have cool XUL and svg stuff, have plans for xforms
though nothing available yet
... not using the same decorator mechanism
... but is a viable technical approach
... I was impressed with their SVG on IE
Steven: Yes and it even works on Opera, though not Chrome
Charlie: We can approach them
about decoration
... it points to need for standardization of this type of
work
... Does anyone know what AML is?
... they have an XML wrapper around Google Maps.
... They do something close to a repeat for the pinpoints
... Not quite what Mark Birbeck is doing with atomic
control
Steven: No it's more like
nodeset
... unrolled repeat
Charlie: Here would be a place to
inject our richtext markup from ubiquity to put html into the
pinpoints
... Steven, can you look at doing this for our demo?
Steven: I can look at it.
... AML is "Ample markup language"
... They have a repeater element
Charlie: I wonder what the event lifecycle for updating is
Steven: This is a Finnish
site.
... They have a Russian version of the site
... Instead of XPath, they're using CSS selectors in their
repeats
... We ought to be talking to these people.
Charlie: They know about XForms;
it's on their to-do list
... their documentation says XForms 1.1 is currently in
development
... they also have an XBL page
John: what's the license?
... If apache or bsd or something similar, that would enable
ubiquity to borrow the XBL
... if GPL, we won't be able to touch it
<scribe> ACTION: Charlie to contact AML people about licensing [recorded in http://www.w3.org/2009/06/16-backplane-minutes.html#action01]
<Steven> http://www.amplesdk.com/ample/technologies/ui/
<Steven> XForms 1.0 (in development)
Charlie: John and I submitted a
paper to DocEng09 on ODF improvements
... We can put it on the web until it is published
... if/once it is accepted
... If we did an ODF spreadsheet, there would be confusion with
xforms repeat
Steven: It's confusing if we show things in ODF that can already be done in XForms
Charlie: in ODT spec, there are a
number of computed metadata items across the document that
don't overlap with xhtml2
... These would be interesting because they highlight the
ODFness, so we should accentuate points that people won't say
"but I can do this in web markup or in xforms"
John: Are we not picking a flow layout fill-in-the-blanks contract document because it's too hard to implement?
Charlie: No, we get flow layout for free with HTML for the flow and xforms for the blanks.
John: I mean flow layout of *editable* text.
Charlie: Oh, no, that would be too hard to implement
John: Even if not implemented in the prototype, we can still make the point that there are important *interactive* capabilities that can be implemented that are beyond html + xforms
Charlie: Can you go into more detail?
John: If the "web page" is in "design mode" that is essentially using a live DOM to record the end-user interaction as ODF
ODF on the web
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/other/Charlie: other/ Succeeded: s/xg/Charlie: xg/ Found Scribe: John_Boyer Inferring ScribeNick: John_Boyer Default Present: wiecha, John_Boyer, Steven Present: wiecha John_Boyer Steven Regrets: Uli Agenda: http://lists.w3.org/Archives/Public/public-xg-app-backplane/2009Jun/0005.html Got date from IRC log name: 16 Jun 2009 Guessing minutes URL: http://www.w3.org/2009/06/16-backplane-minutes.html People with action items: charlie[End of scribe.perl diagnostic output]