Re: [NGO] NETCONF Data Modeling BoF (NDM) proposal

"tom.petch" <cfinss@dial.pipex.com> Fri, 14 September 2007 09:01 UTC

Return-path: <ngo-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IW737-0004Uq-Pn; Fri, 14 Sep 2007 05:01:17 -0400
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1IW736-0004Uh-Mh for ngo-confirm+ok@megatron.ietf.org; Fri, 14 Sep 2007 05:01:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IW732-0004Tw-9c for ngo@ietf.org; Fri, 14 Sep 2007 05:01:12 -0400
Received: from ranger.systems.pipex.net ([62.241.162.32]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IW731-0006WB-Nv for ngo@ietf.org; Fri, 14 Sep 2007 05:01:12 -0400
Received: from pc6 (1Cust72.tnt8.lnd4.gbr.da.uu.net [62.188.137.72]) by ranger.systems.pipex.net (Postfix) with SMTP id 40EF6E0009CA; Fri, 14 Sep 2007 10:01:08 +0100 (BST)
Message-ID: <017301c7f6a4$87471300$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: Ladislav Lhotka <lhotka@cesnet.cz>, ngo@ietf.org
References: <FCC7D7D1DB94054EB491EED9D274727D030FB6@wabex2.sharpamericas.com><034101c7f5f3$90c16540$0601a8c0@pc6> <1189688078.382.20.camel@missotis>
Subject: Re: [NGO] NETCONF Data Modeling BoF (NDM) proposal
Date: Fri, 14 Sep 2007 09:20:36 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -100.0 (---------------------------------------------------)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc:
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Errors-To: ngo-bounces@ietf.org

----- Original Message -----
From: "Ladislav Lhotka" <lhotka@cesnet.cz>
To: <ngo@ietf.org>
Sent: Thursday, September 13, 2007 2:54 PM
Subject: Re: [NGO] NETCONF Data Modeling BoF (NDM) proposal


tom.petch píše v Čt 13. 09. 2007 v 12:46 +0200:
> ----- Original Message -----
> From: "McDonald, Ira" <imcdonald@sharplabs.com>
> To: "Ladislav Lhotka" <lhotka@cesnet.cz>; "tom.petch" <cfinss@dial.pipex.com>
> Cc: <ngo@ietf.org>
> Sent: Wednesday, September 12, 2007 9:18 PM
> Subject: RE: [NGO] NETCONF Data Modeling BoF (NDM) proposal
>
> > Hi Tom,
> >
> > Characterizing RELAX NG versus XSD as "not powerful enough"
> > intrigues me.  Even the W3C now develops many new standards
> > in RELAX NG and machine translates them to XSD *only* when
> > their standards development work is complete (last draft).
> >
>
> Which demonstrates that XSD is at least as powerful as RELAX NG.

No, it just demonstrates that it is easier to communicate the data model
(and develop the schemas) in RELAX NG than in XSD. Even Tim Bray now
recommends to convert to RELAX NG:
http://www.tbray.org/ongoing/When/200x/2006/11/27/Choose-Relax

>
> Now if all valid XSD could be machine translated into RELAX NG,
> I would have to reconsider:-)

You can make up XSD schemas that cannot be translated to RELAX NG and
vice versa. However, for most real-life situations, and especially with
the restrictions placed on NETCONF data (no mixed content, wrapper
elements enclosing repeated children), it is IMO fair to say that both
languages have comparable expressive power and the schemas can be
generally translated in both directions.

<tp>

OK, I will go and do my homework on RELAX NG and maybe then admit defeat.

But I do think that Andy's points in favour of XSD are valid, namely that we
need the skills to produce an interoperable standard, and that we have in XSD.
(It would have been interesting at the previous WG meeting to have asked those
understood RELAX NG to identify themselves and see if it were more than seven).
And to change horses at this point would, for me, imply an RFC4741bis in RELAX
NG.

Tom Petch
</tp>

Lada

Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C



_______________________________________________
NGO mailing list
NGO@ietf.org
https://www1.ietf.org/mailman/listinfo/ngo