See also: IRC log
discussion of what's required to make progress
pauld: need to reply to commenters, prepare issue list for Basic
pauld: having decided to publish Advanced as a note, we're freer to put more descriptive content
jonc: George, you need more feedback from the WG on the patterns you've prepared
gcowe: that would be nice
jonc: are we happy with the granularity of Advanced patterns?
pauld: I'm mostly interested in Basic, are we comfortable with Advanced?
jonc: I'd like a formal review of the Advanced patterns
... are we confident the Advanced patterns haven't broken the Basic patterns?
pauld: the patterns and examples pages flag up incorrect attribution as red "status" http://www.w3.org/2002/ws/databinding/examples/6/09/
AttributeTypeReference and SequenceSequenceElement seem to be "basic" but detected as "advanced"
SequenceSequenceElement should be Advanced
AttributeTypeReference looks a little over engineered
concerned there's no canonical example for GlobalElementComplexType
pauld: worried we're going to
have to rerun the test report
... if we make wholesale changes to examples such this
<Yves> if we need to add patterns to Basic, we still have the possibility to do a short CR
I don't think this example can be basic thanks to Decimal type
I suspect that GlobalElementComplexType is, however, basic
pauld: propose that the example put in the spec doesn't include Decimal
gcowe: need to rebuild the test report and other pages, seem inconsistent
<Yves> Yves is rebuilding the report
<Yves> => reports done
GlobalElementComplexType is a new pattern added by George
pauld: doesn't introduce any new
schema elements, but has been flagged as "Advanced"
... which flagging all examples as "Advanced"
This pattern should be "Basic"!
I don't think there is an issue, this is in *all* of our WSDL examples echoAttributeTypeReference etc introduced by test framework, therefore "Basic"
draws the WG's attention to: http://www.w3.org/2008/07/soapjms.html
suggest we meet same time next week
pauld: pick up a week today!