pauld: Plan to change how we work, we'll collect patterns from the wild, add them to patterns.xml as 'pending' and then process them as a batch at our F2F in February.

pauld: F2F planning, we have the dates 8-9th February in Edinburgh, London, Nice

pauld: Travelling to London is central, but London is expensive and organising a room is tricky. My slight preference is for Nice.

jonc: could host in Sevenoaks

yves: can't make the 8-9th

pauld: Ok, following week 13-15th in Nice

<scribe> ACTION: ylafon to book room in Nice 13-15th [recorded in http://www.w3.org/2006/12/19-databinding-minutes.html#action01]

<trackbot> Created ACTION-96 - Book room in Nice 13-15th [on Yves Lafon - due 2006-12-26].

<vlad> i'm not available at that time

vlad will go ahead with the 13-15th, maybe Vlad could join us remotely

minutes from last telcon approved

ISSUE-2: test suite

http://lists.w3.org/Archives/Public/public-xsd-databinding/2006Dec/0000.html

vlad: had problems with xs:include, propose not using includes, include the patterns in the example schemas

http://www.w3.org/2002/ws/databinding/examples/6/09/StringElement/

http://www.w3.org/2002/ws/databinding/examples/6/09/StringElement/StringElement.xsd

pauld: are you saying the << element ref="" >> pattern is possibly problematic?

vlad: this one looks fine

<vlad> <xs:element name="targetNamespace" type="xs:string"/>

<vlad> was missing

pauld: in the case of TargetNamespace we have a generic issue with examples which are complete schemas

vlad: these examples are incomplete

pauld: first issue is one which george picked up around generating static include files
... second is complete schemas don't have the echo element in the generated echoXXX.xsd schema and WSDL

<scribe> ACTION: pdowney to fix echo examples for complete schemas such as TargetNamespace [recorded in http://www.w3.org/2006/12/19-databinding-minutes.html#action02]

<trackbot> Created ACTION-97 - Fix echo examples for complete schemas such as TargetNamespace [on Paul Downey - due 2006-12-26].

pauld: not worried with the TargetNamespace example (coverage) but includes need fixing

yves: currently working on removing spurious text nodes (insignificant whitespace) for XMLUnit comparison

pauld: been try Axis testing working sought assistance within BT
... no feed back from outside the Working Group, which is a worry
... will contact some developers directly

ISSUE-12: identifying a conformant schema

yves: nothing new on hosting the service

<scribe> ACTION: pdowney to resurrect the generated schemtron stylesheet [recorded in http://www.w3.org/2006/12/19-databinding-minutes.html#action03]

<trackbot> Created ACTION-98 - Resurrect the generated schemtron stylesheet [on Paul Downey - due 2006-12-26].

nice list of schemas in the wild posted to comments list: http://lists.w3.org/Archives/Public/public-xsd-databinding-comments/2006Dec/0002.html

gcowe: continue to use the patterns detector internally

ISSUE-99: XSLT 2.0 terminology?

pauld: took an action, proposal still in my email buffer

ISSUE-100: LC: Basic Profile Compliant Import

pauld: this seems to be the only way to import a schema into a WSDL, access the elements from messages and be BP compliant

gcowe: not a chameleon schema!

pauld: no!
... could be an issue, i'm not convinced it's valid due to schema import not being transitive

<scribe> ACTION: pdowney to craft examples and patterns for ISSUE-100 transitive import [recorded in http://www.w3.org/2006/12/19-databinding-minutes.html#action04]

<trackbot> Created ACTION-99 - Craft examples and patterns for ISSUE-100 transitive import [on Paul Downey - due 2006-12-26].

paul bores the WG with his explanation of "transistive"

gcowe: we haven't encountered this issue.

pauld: could be an issue for the Basic Patterns document becasue no targetNamespace isn't allowed
... suspect we could add this pattern if it's incorrect but could be a substantive change

jonc: so it's currently advanced?
... can we craft a pattern to capture just this use

pauld: yes, we can detect noTargetNamespace schemas with nothing but imports in them
... thinks the elements in the imported schema won't be available to a validator

ISSUE-101: fractionDigits, minLength and maxLength proposed patterns

pauld: new issue from George

gcowe: we found some patterns in our document
... currently have patterns but these apply to xs:string, added patterns for our cases

http://lists.w3.org/Archives/Public/public-xsd-databinding/2006Dec/0006

pauld: three patterns in one issue?

gcowe: fractions belongs with totalDigits

pauld: exercised how to process patterns with respect to the issues list
... I've been adding new patterns to patterns.xml as "pending"
... would like George (and possibly Jon) to have CVS access and to also work from the patterns.xml and examples.xml rather than the ISSUES list
... we can then batch up and accept patterns as Advanced and track via the ISSUES list at the F2F

pauld: these patterns look Advanced though, no?

RESOLUTION: close ISSUE-101 as Advanced patterns

pauld: OK, that's all for today: Happy Christmas/New Year/Holidays/etc to everybody, and see you next on the 16th Jan