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

RE: bug in notification-11 XSD



Sharon (or Hector), I have not seen you react to this
at all. What is the story here? 

Andy, is this about these 2 lines on pages 17/18

    xmlns:manageEvent="urn:ietf:params:xml:ns:netmod:notification"
    targetNamespace="urn:ietf:params:xml:ns:netmod:notification"

and the corresponding line in IANA considerations:

   URI: urn:ietf:params:xml:ns:netmod:notification

I'd like to understand from the authors what their reason is
to not be consistent as Andy suggests.

If that gets changed, then I suspect that the otehr occurences in
the rpc messages need to be changed too, no?

Bert Wijnen 

> -----Oorspronkelijk bericht-----
> Van: owner-netconf@ops.ietf.org
> [mailto:owner-netconf@ops.ietf.org]Namens Andy Bierman
> Verzonden: donderdag 14 februari 2008 20:17
> Aan: Netconf (E-mail); Bert Wijnen - IETF; Sharon Chisholm
> Onderwerp: Re: bug in notification-11 XSD
> 
> 
> Andy Bierman wrote:
> > Hi,
> > 
> > I just noticed that the targetNamespace is wrong in
> > the first XSD in this draft.  It is missing the ':1.0' suffix
> > that is present in the 'ncEvent' URI.
> > 
> > (Not that this reaffirms my belief that XSD is a mistake factory ;-)
> > 
> 
> oops -- I was looking at ncEvent but I should have been looking
> at manageEvent.  The XSD is okay but I think the WG should pick
> a URI style (with or without version numbers) and stick with it.
> 
> 
> > Andy
> 
> 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/>
> 

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