Re: RFC Editor edit list for approved netconf drafts

[Martin Bjorklund <mbj@tail-f.com>]

Andy Bierman <ietf@andybierman.com> wrote:
> Martin Bjorklund wrote:
> > Andy Bierman <ietf@andybierman.com> wrote:
> >> Hi,
> >>
> >> Somebody asked for this edit list earlier.
> >> It is available from the ID-Tracker as well.
> >>
> >> Is this list complete?
> > 
> > What about the schema issues that were discussed in
> > http://ops.ietf.org/lists/netconf/netconf.2006/msg00512.html, and then
> > in some more recent thread?
> 
> What is the proposed text for the RFC Edit?

I must say that I'm not sure that this is the right change, but I
think that the easiest way to fix this is to change the
dataInlineType, configInlineType and filterInlineType to be
xs:extension of xs:anyType instead of xs:restriction, i.e. instead of

     <xs:complexType name="configInlineType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType"/>
       </xs:complexContent>
     </xs:complexType>

which, as far as I understand it, restricts configInlineType to be
'empty', we should have

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

(and same for dataInlineType and filterInlineType).

> Are there any issues with <filter> now, or just <config> ?

Yes, see above.


This change is verified with the validator in libxml2.


/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/>