Ladislav Lhotka <[email protected]> wrote: > > > On 24 May 2016, at 16:33, Dale R. Worley <[email protected]> wrote: > > > > (I've not received some of the discussion e-mails, so I am just now > > responding.) > > > > Ladislav Lhotka <[email protected]> writes: > >> This follows from the fact that YANG doesn't support mixed content: > >> there is no way how this whitespace can be made significant. > > > > It seems to me that this is the restriction that should be stated: "In > > NETCONF XML, non-whitespace character content is only allowed as content > > of elements that provide values. > > Yes, it means in elements representing leaf and leaf-list instances. > > > Non-whitespace character content in other locations is ignored." > > You probably meant "whitespace character content" here. (?) > > > > > > > Of course, this is a general statement about the XML encoding, not about > > any specific Yang element. > > > >> What about comments and processing instructions? > > > > My understanding is that comments are always allowed, because they're > > understood to be deleted by the XML parsing process. Processing > > instructions seem to be defined to be significant. I would assume that > > by default no processing instructions are allowed unless Netconf defines > > one. > > I agree.
PIs are directed to applications / implementations. There are no standard PIs defined. However, I don't think it would be correct to state that there MUST NOT be any PIs - if some implementation supports a PI the client can send it to that implementation and everything is fine. /martin _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
