Re: analysis of YANG vs. RELAX NG

Martin Bjorklund <mbj@tail-f.com> Fri, 30 November 2007 19:38 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyBhT-0003Pi-1y; Fri, 30 Nov 2007 14:38:59 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IyBhR-0003PD-Nu for discuss-confirm+ok@megatron.ietf.org; Fri, 30 Nov 2007 14:38:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IyBhR-0003P0-E5 for discuss@apps.ietf.org; Fri, 30 Nov 2007 14:38:57 -0500
Received: from [213.180.94.162] (helo=mail.tail-f.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IyBhR-0001Du-0n for discuss@apps.ietf.org; Fri, 30 Nov 2007 14:38:57 -0500
Received: from localhost (pool-71-120-236-45.spknwa.dsl-w.verizon.net [71.120.236.45]) by mail.tail-f.com (Postfix) with ESMTP id 806991B80C5; Fri, 30 Nov 2007 20:38:54 +0100 (CET)
Date: Fri, 30 Nov 2007 20:38:49 +0100
Message-Id: <20071130.203849.128933561.mbj@tail-f.com>
To: rohan.mahy@gmail.com
Subject: Re: analysis of YANG vs. RELAX NG
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <953beacc0711291100lfe8cb6xeba5ac28b091b6fb@mail.gmail.com>
References: <953beacc0711281025w4d993dd7u77d729111074496c@mail.gmail.com> <474E83A4.3050000@ericsson.com> <953beacc0711291100lfe8cb6xeba5ac28b091b6fb@mail.gmail.com>
X-Mailer: Mew version 5.1.51 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Hi,

I really appreciate your comments on the YANG draft.  If there are
other little rules you have found, please let us know.

"Rohan Mahy" <rohan.mahy@gmail.com> wrote:
> For example the distinction between the leaf-list and list objects
> in YANG is pretty syntactic. (One of the YANG team's
> "little-rules").

I can understand if you argue that leaf-list is not necessary, since
we have list.  But why is having leaf-list a little-rule?

We think leaf-list is useful of course, but that's not the point (I
think).

> Likewise, creating containers automatically is a syntactic construction.
> (Another "little-rule", but at least this one is explicit).

I think that this is something we can fix.  I think the problem lies
more in the current description of the concept (of containers used for
structuring purpose), than in the concept itself.  The underlying idea
is that if a container is used for structural purposes only, then it
doesn't have to be present in the XML encoding unless necessary.
I.e. if it currently doesn't have any children, then it doesn't have
to be encoded.

> Defining new data types in YANG is completely gratuitous syntax.

I'm sorry, I don't understand what this means. Could you explain what
you mean?


/martin