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

Re: RFC Editor edit list for approved netconf drafts

Martin Bjorklund wrote:

Andy Bierman <ietf@andybierman.com> wrote:

Martin Bjorklund wrote:

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


I don't know the correct XSD text either.
Since this entire exercise is for the benefit
of XSD tools, we need somebody who uses those tools
to find the text that works.


As I wrote, I did test it with libxml2.

Furthermore, if this construct is used (i.e. xs:extension) the
original filter definition validates just fine even for xpath,
i.e. there would be no need to add the 'select' attribute.  (Not that I
have any problems with the 'select' attribute).


  - Since XML treats whitespace as content, the following filters
    are different:

    1) legal, empty:    <filter type="subtree"></filter>
    2) illegal, text:   <filter type="subtree"> </filter>


I don't follow that logic.  Are you suggesting that this is special
only for the empty filter, but not when you have some subelements?
Thus, would

  <filter type="subtree"><top xmlns="http://foo.com"/></filter>
be identical to 
  <filter type="subtree">
    <top xmlns="http://foo.com"/>
  </filter>

or not?




No it is not special.
It is just whitespace between a start and end tag,
not between two start tags.  Your example is correct.
Whitespace from start to start tag or end to start tag is ignored.

<filter> </filter>

<filter>
</filter>

Both of these elements contain whitespace; they are not empty.
This test applies only to simpleTypes.  I don't actually
reject this. I check for it, and treat the construct as
an empty tag.  You can force the parser to take a whitespace
string using double quotes:  <foo>" "</foo>.








/martin




Andy



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