See also: IRC log
<scribe> New member, George Gowe
George is from Origo an insurance vertical organisation
Origo has own mesage specifications
now running a web services adoption program and seeing issues with WS toolkits
Minutes from F2F and last conf call approved
Next f2f meeting ...
In Europe looking at dates in May
week 22 - 26th in Edinburgh is an option, it's WWW2006. Origo can host (Thanks George!)
pauld: looked at similar styled specs
pauld: this has undone work from Yves in the Basic Patterns docs is this OK?
Yves: likes the new format
pauld: new structure should help us write a more formal 'spec like' document
JonC: Very little discussion on list. Have we hit the nail on the head?
RESOLUTION: Close ISSUE-7 with JonC proposal
<pauld> schema with predefined types: http://www.w3.org/2002/ws/databinding/edcopy/testsuite/documents/predefinedTypes/predefinedTypes.xsd
pauld: submission to the list identifies 2 proposals
pauld: which proposal do we want to put forward?
JonC: Like 2nd proposal as it doesn't 'lower the bar' too much but still gives advice based on practical knoledge to the schema author.
Ajith: this is very much language dependent
pauld: goes back to how do we quantify patterns i.e. 5 star, 4 star patterns. This seems to be an acid test for if we need such a rating system
Ajith: likes this idea
pauld we may struggle with a fine-grained rating system. Do we want a simpler 'warning' or 'proceed with caution' system?
<pauld> Ajith draws our attention to his validation tool: http://lists.w3.org/Archives/Public/public-xsd-databinding/2006Mar/0017.html
<pauld> ACTION: pdowney to make a combined proposal for ISSUE-3 [recorded in http://www.w3.org/2006/03/28-databinding-minutes.html#action01]
<trackbot> Created ACTION-30 - Make a combined proposal for ISSUE-3 [on Paul Downey - due 2006-04-04].
re Chameleon schemas
pauld: suggest we recommend that we only include patterns that specify a targetNameSpace. No namespace schemas tricky inside SOAP envelopes.
Yves: happy with recommendation as long as design consideration is included to say why tns is desirable
RESOLUTION: close ISSUE 27 with pauls proposal and design consideration as to why tns desirable
pauld: another common gotcha
rec is to offer the basic pattern of elementFormDefault="qualified"
and only allow unqualified elements for empty schema
pauld proposes resolution as proposal
RESOLUTION: close ISSUE-26 with pauld's proposal in the issue
pauld New issues raised 28 - 30
pauld: split ISSUE-1 at Cannes F2F. will likely land in a conformance section.
pauld: please look at these issues and contribute to the list
pauld: will be cancelling mtg on 11th due to travel commitments
<pauld> thanks to JonC for scribing!