NEW ISSUE: UPA in web service binding with EndpointReference

TARGET: SCA WS Binding Specification
cd01

DESCRIPTION: 

The schema for binding.ws calls for
the following construct:

         
      <sequence>

         
          <element ref="wsa:EndpointReference"
minOccurs="0"

         
               maxOccurs="unbounded"/>
               

         
          <any namespace="##other"
processContents="lax" minOccurs="0"

         
               maxOccurs="unbounded"/>

         
      </sequence>

Which leads to a UPA error it you try
and validate against it.  For UPA see http://en.wikipedia.org/wiki/Unique_Particle_Attribution

The schema is valid in the sense that
it's valid and well formed XML but you will get a UPA validation error
if your .composite file has an EndpointReference element within a binding.ws
element. The problem being that the validator doesn't know if the EndpointReference
belongs to the <EndpointReference> or <any> schema elements.

PROPOSAL:

It seems difficult to fix this kind
of problem and maintain the ability to support EndpointReference validation
and binding.ws extensibility without changing the structure of binding.ws.
Resolution to be determined.

Simon Holdsworth

STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair

MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK

Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898

Internet - 

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU