See also: IRC log
minutes from last week approved
F2F planning - suggested hotel is full
Jonc: have to drop off at 15:30
George sends regrets for next week's call
chair: let's go to ISSUE-10 and skip next week, then
Jonc: presents background on rationalle for his text
modified proposal from Jonc: http://lists.w3.org/Archives/Public/public-xsd-databinding/2006Sep/0023.html
pauld: where would this text go?
jonc: you've pushed for maybe a primer or annotated companion to the document, not necessarily in our spec?
pauld: less text may mean less comments, otoh good text may stave people making comments. This issue is contentious enough to get them anyway.
pauld: so we've three proposals, and there are two parts: the normative constriction and the explanatory text.
jonc: my latest proposal replaces the first one
jonc: i'm ok with the constriction
yves: mostly ok with constriction, but would also like to see the rational as non-normative text
george: ok with the constriction
yves: you might prefer readability and maintainance as opposed to interoperability, maybe this pattern should be a guideline, not normative?
chair: so we're back to it being a "Design Consideration". I'm not hearing consensus. let's park this for a couple of weeks.
pauld: still working on the report
gcowe: working on the naming convention
... sent paul mail
pauld: thanks, we need to move the ant forward, and the two-phase pattern detection
pauld: did some testing on this: http://lists.w3.org/Archives/Public/public-xsd-databinding/2006Sep/0022.html
<scribe> ACTION: gcowe to test ISSUE-68 example with WebSphere [recorded in http://www.w3.org/2006/09/19-databinding-minutes.html#action01]
<trackbot> Created ACTION-66 - Test ISSUE-68 example with WebSphere [on George Cowe - due 2006-09-26].
<pauld> I can pick up ACTION-63 as business as usual
pauld: came up with example for Chameleon Include - do we need a separate issue for this?
http://lists.w3.org/Archives/Public/public-xsd-databinding/2006Sep/0021.html
Is this a separate pattern, if so I'll open a separate issue for this?
gcowe: we discussed making stand-alone schemas before, I can look into this
pauld: we also need to double-check we have patterns for all our issues and examples for all our patterns, a script might help here.