Re: [Netconf] 4741bis-04 has non-deterministic schema

[Martin Bjorklund <[e-mail]>]

Hi,

Kent Watsen <[e-mail]> wrote:
> I loaded the schema from 4741bis-04 into XMLSpy (2006) and got the
> following error:
> 
> '<xs:element ref="rpc-error">' makes the content model
> non-deterministic against '<xs:any namespace-"##any">'.

Ugh.  I've validated the XSD with libxml, but it doesn't complain :(
I agree this is an error though.

One option is to change the ##any to ##other:

  <xs:group name="rpcResponse">
    <xs:sequence>
      <xs:element ref="rpc-error"
                  minOccurs="0" maxOccurs="unbounded"/>
      <xs:any namespace="##other" processContents="lax"
              minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:group>

But then we have the problem that the "data" element is not listed
here, since it is defined in the Operations Layer as rpc output to get
and get-config.  This becomes a problem since the XSD and YANG model
both provide elements to the same namespace.

We could handle this by putting data back:

  <xs:group name="rpcResponse">
    <xs:sequence>
      <xs:element ref="rpc-error"
                  minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="data" type="dataInlineType" minOccurs="0"/>
      <xs:any namespace="##other" processContents="lax"
              minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:group>

  <xs:complexType name="dataInlineType">
    <xs:complexContent>
      <xs:extension base="xs:anyType"/>
    </xs:complexContent>
  </xs:complexType>

But then we're mixing layers... 


An alternative would be to use the substitution technique that we
already use for the rpc operation:

  <xs:group name="rpcResponse">
    <xs:sequence>
      <xs:element ref="rpc-error"
                  minOccurs="0" maxOccurs="unbounded"/>
      <xs:element ref="rpcResponse" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:group>

  <xs:complexType name="rpcResponseType"/>
  <xs:element name="rpcResponse"
              type="rpcResponseType" abstract="true"/>


And then if you want to define your own rpc-reply element, e.g. "data"
you would do:

  <xs:element name="data" substitutionGroup="nc:rpcResponse">
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="nc:rpcResponseType">
          <xs:sequence>
            <xs:any minOccurs="0" maxOccurs="unbounded"
                    namespace="##other" processContents="lax"/>
          </xs:sequence>
        </xs:extension>
      </xs:complexContent>
    </xs:complexType>
  </xs:element>



/martin