Rich Web Backplane XG telecon -- 14 Oct 2008

Thanks for the title/abstract

<Charlie> yup

<Charlie> looking forward to seeing where we are

<Charlie> for all the bits and pieces...

Yes

<Charlie> hi jack

<jackjansen> hi!

<scribe> scribe: Steven

<scribe> Meeting: Backplane Weekly Teleconference

<scribe> Chair: Charlie

TPAC TP Day

<Charlie> http://www.w3.org/2008/10/TPAC/TPDay-Agenda.html

[Steven explains the aims behind the session]

"Session 7: Future of XML ecosystem in W3C client-side work"

John: I'll send a revised version of the abstract

Charlie: I put up a revised set of charts on the wiki

<Charlie> http://www.w3.org/2005/Incubator/app-backplane/wiki/images/0/0f/TPAC_2008.pdf

Charlie: the demos are in good shape
... we need to think about the flow of how it comes together

[look at the slides]

Steven: We have two take aways: Combining tech, and it can be done now
... we should do it from the viewpoint of this incubator
... maybe cut down on the intro

Charlie: Lead from the demos?

Jack: I like slide 2 though

Charlie: I think we can compress it

Jack: Is it too late to change the title? It sounds defensive

Steven: It has gone to press, but we can change the website version

Charlie: There are some good demos. The ODF one, most people don't realise there is an XForms instance in there

Steven: (Earlier) We can end with how modularization means you have a finer-level of possibilities for inclusion. Look at XForms instance in SMIL

Charlie: At this point we can go with the set of demos we have
... maybe I should mention ARIA too though
... so John, anything on modularity?

John: I have an abstract, but I'need to send it to you (having tech problems today)
... the ubiquity strategy is threefold
... that we can get cross-browser support using Ajax
... Ajax is the assembly language of the web
... and the browser manufacturers don't need to be involved
... I will use the opportunity to provide the link to Ubiquity
... open source, Apache license
... broadly applicable
... gets round having to sell it to the browsers
... Then there's the authoring issues
... you can sell parts of the tech stack without having to sell the whole
... If I say wouldn't it be great to use xf:submission without much else
... do people run afoul of validators?

Steven: So that's the power of XHTML Modularization
... it allows you to provide modularized schemas/dtds
... that's how we did it with RDFa
... we had a schema in no time, and it validated immediately

http://www.w3.org/News/2008#item168

Steven: The spec contains examples of how to create DTDs and Schemas

Steven note to self, maybe I should write a tutorial

+1 from Jack

Jack: Slide 16 is a bit daunting, but if you highlight the building blocks, you can make it more approachable

s/datn/daunt/

John: The third point of the threefold approach
... how do you inject the semantics
... leads to the forms attributes approach, like RDFa
... which gets the meme into the author's mind

Steven: Isn't that too much for the talk?

Charlie: Well, that's the 'bridge' part of the title
... it is a part of driving adoption through smaller specs
... and reduces the amount people have to mentally adopt
... but I agree it's a lot, but I think we can order it suitably

John: About the slides
... are we going with slidy?
... how about ODF?

Charlie: You want to post ODF slides?
... it would be easier, but I would vote for slidy
... I will translate to slidy for you if you want
... please send before Saturday night

- DRAFT -

Rich Web Backplane XG telecon

14 Oct 2008

Attendees

Contents

TPAC TP Day

Summary of Action Items

Scribe.perl diagnostic output