Next in thread → Next in month →

Re: [ebcore-comment] problem with msg-header-2_0.xsd

From
Pim van der Eijk <>
Date
2020-09-30T13:45:50+00:00
ID
Thread
Re: [ebcore-comment] problem with msg-header-2_0.xsd
Hello,

    
This is an old known problem, see e.g.
      http://lists.ebxml.org/archives/ebxml-dev/200810/threads.html#00007.  
      The solution is to edit the definition of "Acknowledgment" to be
      like the following and it will be valid.  This is not a problem
      for interoperability as nobody is using these additional
      "##other"  elements.

    
BTW 1,  the ebxml message TC has its own comment list 
      .  I send it there too.

    

    
BTW 2,  nice to hear that the ancient v2 of ebMS is still finding
      new implementers.   We have had a newer version 3 and an AS4
      profile also since quite a few years.  

    

    
Pim

    

    

    

    
    <element name="Acknowledgment">

              <complexType>

                  <sequence>

                      <element ref="tns:Timestamp"/>

                      <element ref="tns:RefToMessageId"/>

                      <element ref="tns:From" minOccurs="0"/>

                      <element ref="ds:Reference" minOccurs="0"
      maxOccurs="unbounded"/>

                      <!-- 

                      <any namespace="##other"
        processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

                      -->

                  </sequence>

                  <attributeGroup ref="tns:headerExtension.grp"/>

                  <attribute ref="soap:actor"/>

              </complexType>

          </element>

      

    

    

    

    
On 29-09-2020 16:45, Joe Schmitz wrote:

    

    
      
      
      
      
      

        
Hello, 

        
 

        
When I try to validate the following xsd or
          use the XSD to validate an xml message I get an error.

        
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd

        
 

        
--------------------

        
The content model of complex type
          definition '{anonymous}' is ambigious.

        
                             Error
          location: schema / element / complexType

        
                             Details

        

          
                                                         
            cos-nonambig: <:any namespace='##other'> makes the
            content model non-deterministic against <:element
            name='Reference'>. Possible causes: name equality,
            overlapping occurrence or substitution groups.

        

        
 

        
Can you help?

        
 

        
Thanks

        
 

        
Joe

        
 

        
 

        

        
 

        
Joe
Schmitz                                                                                            
            Switchboard: + 46 8 511 85 990

        
Technical Project
            Manager                                                 
                               Cell: + 46 (0)70 96 66 737

        
Infosolutions
            Sverige
AB                                                                         e-mail:

        
Kista Science Tower, plan
            E5                                                                
          www.infosolutions.se

        
SE-164
            51  KISTA

        
Sweden
Next in thread → Next in month →