OASIS ebXML Messaging Services TC

Back to discussions
Expand all | Collapse all

[ebxml-msg] Issue 74: foreign namespace attributes

  • 1.  [ebxml-msg] Issue 74: foreign namespace attributes

    Posted 02-12-2002 20:30 
     MHonArc v2.5.2 -->

















    ebxml-msg message
    







    [Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]
    


    







    Subject: [ebxml-msg] Issue 74: foreign namespace attributes
    







    



    



    I agree with David's addition of the anyAttribute construct 
back to the headerExtension.grp and bodyExtension.grp attribute groups in 
"Version 2.0 rev A". The namespace however is not quite correct. It should be 
changed from
    

     
    

    <anyAttribute 
namespace="http://www.w3.org/2000/10/XMLSchema-instance" 
processContents="lax"/>
    

     
    

    to
    

     
    

    <anyAttribute 
namespace="http://www.w3.org/2001/XMLSchema-instance" 
processContents="lax"/>
    

     
    

    to correspond to the W3C Recommended verson of XML Schema. 
I think the main purpose of this wildcard attribute is to 
allow for the specification of an xsi:schemaLocation attribute for the foreign 
namespace qualified wildcard elements that occur under a given ebXML SOAP Header 
or SOAP Body extension element.
    

     
    

    I am not sure about the <anyAttribute 
processContents="lax"> definition under the Reference element. It is an 
attempt to make the schema consistent with section 3.2.1 (Reference Element) 
section in the spec which states: "Any other namespace-qualified attribute MAY 
be present. A Receiving MSH MAY choose to ignore any foreign namespace 
attributes other than those defined above."
    

     
    

    Such wildcard attributes without any namespace restriction has 
never been used in any previous version of the ebMS schema. I think the 
statement in section 3.2.1 allowing such wildcard attributes constitutes a 
change that may have never been agreed by the team.
    

     
    

    I am attaching some communications I have had with David 
earlier.
    

     
    

    -Arvola
    

     
    


    


    



    David:
    

     
    

    

    This is directly related to issue #74 raised by Doug. Why 
don't we discuss this on the ebxml-msg@lists.oasis-open.org 
alias and try to get it resolved at next week's CC?
    

     
    

    Regards,
    

    -Arvola
    

    
  

    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                
    
                                                
                                            
    
                                        

                                        
                                        

                                    
			

                                    
                                

                                
                                
    
                                
    
                            
		
                
        
    




            
        
    


	
    


    
    
         
    
    Related Content