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

Re: subelements

Martin Bjorklund wrote:

Phil Shafer <phil@juniper.net> wrote:

Johan Rydberg writes:

Why are configurations named with an subelements of <source> or <target>
and not text payload of the element?  This should make it impossible to
have a configuration named "config", for example.

I think you have it backwards, or I'm misunderstanding you.

By using named subelements, we allow extensibility such as:

  <source>
    <divine-inspiration xmlns="http://di.example.net"/>
  </source>


... except that this isn't allowed by the XSD in rfc4741.  Should this
be viewed as a bug in the schema?


no -- there is no mention in the RFC of this extensibility feature
that does not officially exist.  I remember (way back when ;-)
that Phil convinced us that

 <source><running/></source>

was better than

 <source>running</source>

It had something to do with making it easier to define an XSD
that was a subset of the standard configurations.  I don't see
how it makes this possible without editing the schema, same
as if the 'source' was an enumerated string.

However, I don't mind the parameter the way it is,
even if it is harder to implement than a string.
A choice of N elements is more extensible than
a union of N strings.




(In general I think it's unfortunate that the schema is not more
extensible.)



We are going to make sure the Notification XSD is properly extensible.
Several people (4?) have requested this and nobody has objected.

I am declaring that WG consensus exists to define NETCONF XSDs
such that they can be properly extended and restricted.

If RFC 4741 is ever republished (highly likely), then I see no
reason why the XSD cannot be altered, if it still describes
the same set of valid instance documents.

(But if the RFC cycles at Proposed Standard, this is not even
a requirement.)



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