See also: IRC log
<JacekK> minutes http://www.w3.org/2002/ws/sawsdl/minutes/20070213
RESOLUTION: minutes approved
<scribe> ACTION: Eric to upgrade the SPDL page for SAWSDL readers and then work things out with the Usage Guide [PENDING] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20070220#action01]
<scribe> ACTION: bns to check http://www.w3.org/2007/01/SPAT/ if it's useful [DONE] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20070220#action02]
<scribe> ACTION: JacekK to ask WS-Desc WG about propagation of annotations in the component model [DONE] [recorded in http://www.w3.org/2002/ws/sawsdl/minutes/20070220#action03]
two March telcons 1 hour later for USA
jacek: discussion about moving WSDL safety to SAWSDL moved to next week
jacek: we can formulate a new charter or suggest new WG focusing on different facets of SA
joel: lot of possibilities need to think about
jacek: please send any suggestion to private ML
jacek: implementation report still to be filled, any report?
<john_ajith_jon> http://cs.uga.edu/~ranabahu/tools/tool-table.html
carlos: extension of BPEL which make use of SAWSDL from project SUPER
... waiting for a more stable version for march
ajith: previous work for wsdl-s on object model can refocus on SAWSDL
... now working to extend woden for WSDL 2.0, will talk about it on their list
... next step integrate RADIANT with extended woden
... WSDL 1.1 model might be ready for end of february
joel: updates on IBM tool for next week
jacek: same on the RDF mapping and our WSMO spec - more update next week
joel: not clear wath happens with complex types
RESOLUTION: model reference will propagate from complex and simple types to the element and attribute declarations that use them
laurent: agree that in case of contradictions they'll be invalid
<ericP> are model references allowed to contradict?
<ericP> ahh, good
<ericP> +1 to what laurent says
jacek: problem of propagation of model ref to extended interfaces: estension doesn't invalidate cathegorization
... wsdl interface extension may be inheritance but also aggregation
ajith: how to identify a cathegorization annotation?
jacek: option: model references aren't inherited by default but implementors of extending interface can decide
<ericP> we *can* restrict what realm of use we can specify
jacek: doesn't seem there are relevant reasons for automatic inheritance
ericp: it should be up to who extends to decide how to deal with the annotations
jacek: propagation make sense when there's is 1-to-1 relationship like from elements to their types, not at interface level where it's more complex
ericp: difficoult to specify, why not trying to think in terms of just discouraging bulk propagation by default?
<laurenth> the inheritnce behaviour is model reference specific
jacek: need to wrap up let's continue discussion on mailing list
<ericP> true, can easily copy and paste modelReferences more easily than one can copy an entire WSDL interface