With support from Data AD's (Malcolm & David), this document was approved for publication, and moved into final Editor Review on 29 August, 2006.

We've spotted and fixed a small error (Section 5.4.7: SchemaNamespace removed from the list of parameters in the description of AddSchemaRequest) in 
the attached, which should be used as the final version.

Since public comment, we have handled the issue raised during public comment and have reviewed the text within the group. This internal review has 
taken into account feedback from an implementation activity, as to what could usefully be clarified or tightened-up.  The most substantial change in 
the light of the internal review has been to tighten the handling of typed collections.

Thanks, and sorry for the delay.  Yes, please go ahead with
those changes.  We're looking forward to the next/final
document.  Work with your ADs as needed for this revision,
then upload and assign back to gbn for the next phase.

This note indicates how we propose to respond to the comments made during the public comment period.  At the time of writing (2nd May 2006) the public
 comment period has completed but we have not received any feedback subsequent to the completion of the public comment period.  We are keen to clarify
 as soon as possible how to proceed from here, especially as GGF17 starts in just over a week.


#1 john_ibbotson@uk.ibm.com, 2006-03-02

Issue:
  
I'm tying to use the XMLSequenceAccessPT within GT4. Using GT4 to build the Java stubs, I get some weird effects for the fault classes. Some of the 
classes end up with _Element being added to the class name. This is an Axis strategy for naming conflicts.

However, I can get round it by getting rid of the anonymous types for Faults. For example:
<xsd:complexType name="ServiceBusyFaultType"/>
<xsd:element name="ServiceBusyFault" type="wsdai:ServiceBusyFaultType">
</xsd:element>

I suspect I am encountering some tools fault, but changes to the DAIS WSDL/Schema does fix the problem.  

Response:

This problem with the Axis WSDL2Java tool has also been encountered by other developers. To avoid the naming conflict, it is suggested that the first 
character of the fault type be changed to lower case for all of the faults.

For example, for a fault currently defined as follows:

<xsd:element name="InvalidStartPositionFault">
<xsd:complexType/>
</xsd:element>

<wsdl:message name="InvalidStartPositionFault">
<wsdl:part name="InvalidStartPositionFault"
element="wsdaix:InvalidStartPositionFault"/>
</wsdl:message>

WSDL2Java produces Java code which does not compile. The following change fixes this:

<xsd:element name="invalidStartPositionFault">
<xsd:complexType/>
</xsd:element>

<wsdl:message name="InvalidStartPositionFault">
<wsdl:part name="InvalidStartPositionFault"
element="wsdaix:invalidStartPositionFault"/>
</wsdl:message>

These changes will be included in the revised specifications.

I'm tying to use the XMLSequenceAccessPT within GT4. Using GT4 to build the Java stubs, I get some weird effects for the fault classes. Some of the 
classes end up with _Element being added to the class name. This is an Axis strategy for naming conflicts. 

However, I can get round it by getting rid of the anonymous types for Faults. For example:
          <xsd:complexType name="ServiceBusyFaultType"/>
          <xsd:element name="ServiceBusyFault"
                       type="wsdai:ServiceBusyFaultType">
          </xsd:element>

I suspect I am encountering some tools fault, but changes to the DAIS WSDL/Schema does fix the problem.

Sorry for my delay in initial editor review.  Somehow I missed
the email notification of this upload.

My initial Editor review indicates this document is ready to
move forward.  It is now in GFSG initial 15-day review, prior
to 60-day public comment.