[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: another schema issue



Martin Bjorklund a écrit :
I didn't quite understand all implications of configInlineType:

     <!--
       Type for <config> element
       -->
     <xs:complexType name="configInlineType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType"/>
       </xs:complexContent>
     </xs:complexType>

     <xs:element name="config" type="configInlineType"/>


so I tried to validate an edit-config message with the schema in the
draft and xmllint.

It complained and said that the <config> element's type is empty,
which makes sense I suppose.  There's a restriction on anyType which
restricts it to nothing.
Same for me. I validates in Java but not in libxml2 (C). I suspect Java is wrong but not sure.
This is the same problem as filter previously.
Add something like this solve the problem, instead of xs:complexContent:
<xs:sequence>
        <xs:any processContents="skip"/>
      </xs:sequence>
Also, if I remember well the xpath attribute of filter is not set to optional. I think it should.
Vincent


Shouldn't the "config" element (all all others alike) be defined as:

         <xs:element name="config" type="xs:anyType"/>


What do I miss?


/martin





--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>


	

	
		
___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>