[YANG] yin-element missing from pyang
Balazs Lengyel <balazs.lengyel@ericsson.com> Mon, 14 January 2008 12:31 UTC
Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1JEOTe-0005L1-Tw; Mon, 14 Jan 2008 07:31:42 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43)
id 1JEOTd-0005Ku-7M
for yang-confirm+ok@megatron.ietf.org; Mon, 14 Jan 2008 07:31:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1JEOTc-0005Km-Ti
for yang@ietf.org; Mon, 14 Jan 2008 07:31:40 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JEOTb-0002Ik-E9
for yang@ietf.org; Mon, 14 Jan 2008 07:31:40 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
5ED8B20D53; Mon, 14 Jan 2008 13:31:15 +0100 (CET)
X-AuditID: c1b4fb3c-b0f99bb0000030cf-35-478b561303af
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
38B3020D0D; Mon, 14 Jan 2008 13:31:15 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 14 Jan 2008 13:31:08 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by
esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 14 Jan 2008 13:31:08 +0100
Message-ID: <478B560C.5030105@ericsson.com>
Date: Mon, 14 Jan 2008 13:31:08 +0100
From: Balazs Lengyel <balazs.lengyel@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Martin Bjorklund <mbj@tail-f.com>, yang <yang@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Jan 2008 12:31:08.0701 (UTC)
FILETIME=[56DF84D0:01C856A9]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc:
Subject: [YANG] yin-element missing from pyang
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>,
<mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>,
<mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org
Hello Martin, Why is the yin-element statement necessary? IMHO it should be up to the application/compiler how it handles extensions. On the other hand I see no reason not to translate extensions to YIN. It would kill our statement that YANG and YIN are functionally equivalent. By the way pyang doesn't accept yin-element just now. Balazs -- Balazs Lengyel Ericsson Hungary Ltd. TSP System Manager ECN: 831 7320 Fax: +36 1 4377792 Tel: +36-1-437-7320 email: Balazs.Lengyel@ericsson.com _______________________________________________ YANG mailing list YANG@ietf.org https://www1.ietf.org/mailman/listinfo/yang
- [YANG] yin-element missing from pyang Balazs Lengyel