Report for the 10/17 telcon by Jacek: The ETF has started with my list of issues. Issue #1: we seem to be heading in the way which SQL/XML chose - encoding characters illegal in XML into an expanded hex form. Issues 18/121: soapbuilders agree that inlining of referenced data would be a good thing. There are some further issues though that the ETF will have to consider, I will bring these issues to the ETF. Issue 29: SOAP seems to fulfill the requirement 402. It has to be made clear that the SOAP data model and SOAP encoding rules are not mandatory, that other data models and encoding rulesets can be used in SOAP. Issue 17: The spec and/or the primer will contain some guidance about when/how to use the SOAP data model and encoding rules, also with or without XML Schema. The text will depend on the outcome of the discussions around the previous issue, 29. Issue 30: we agreed the spec should explicitly say that hrefs in SOAP encoding can effectively point to anything, not just to data inside the envelope. There is a further issue about typing the referenced data in case it's a world wide web resource.