Re: WG Review: NETCONF Data Modeling Language (netmod)
Chris Newman <Chris.Newman@Sun.COM> Mon, 21 April 2008 07:20 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDE1A3A6F01; Mon, 21 Apr 2008 00:20:25 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86B543A68BF; Mon, 21 Apr 2008 00:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.046
X-Spam-Level:
X-Spam-Status: No, score=-3.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wdxo9dZuqGh; Mon, 21 Apr 2008 00:20:23 -0700 (PDT)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by core3.amsl.com (Postfix) with ESMTP id B1A043A69E1; Mon, 21 Apr 2008 00:20:23 -0700 (PDT)
Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3L7KUDJ002923; Mon, 21 Apr 2008 00:20:30 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JZN00701Z0V9C00@fe-sfbay-09.sun.com> (original mail from Chris.Newman@Sun.COM); Mon, 21 Apr 2008 00:20:30 -0700 (PDT)
Received: from [10.0.1.4] (75-142-59-194.static.mtpk.ca.charter.com [75.142.59.194]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JZN00MTKZ24OI00@fe-sfbay-09.sun.com>; Mon, 21 Apr 2008 00:20:30 -0700 (PDT)
Date: Mon, 21 Apr 2008 01:20:29 -0600
From: Chris Newman <Chris.Newman@Sun.COM>
Subject: Re: WG Review: NETCONF Data Modeling Language (netmod)
In-reply-to: <20080415183001.54B9C3A6C61@core3.amsl.com>
To: ietf@ietf.org
Message-id: <D50248ED6D20DB444FD88CD1@446E7922C82D299DB29D899F>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-disposition: inline
References: <20080415183001.54B9C3A6C61@core3.amsl.com>
Cc: ngo@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
--On April 15, 2008 13:30:01 -0700 IESG Secretary <iesg-secretary@ietf.org> wrote: > NETCONF Data Modeling Language (netmod) I support the creation of this WG. > 2. The YANG data modeling language and semantics (proposed > standard) ... > 5. Mapping rules of YANG to DSDL data modeling framework (ISO/IEC > 19757), including annotations for DSDL to preserve top-level > semantics during translation (proposed standard). A great deal of effort has been put into designing standard XML data modeling languages over many years and given that both DTD and XML Schema have significant weaknesses (particularly in the area of extensibility), a DML for XML is clearly difficult and requires special expertise. (5) is critical to demonstrating that YANG has learned from the mistakes of past XML-DMLs with respect to extensibility and other areas. The simpler (5) happens to be, the more confident I will become that YANG is following best practices for XML DMLs. > 4. YIN, a semantically equivalent fully reversible mapping to an > XML-based syntax for YANG. YIN is simply the data model in an XML syntax > that can be manipulated using existing XML tools (e.g., XSLT) (proposed > standard) If 5 is as simple as I think it should be, then I suspect there will be little semantic difference between 4 & 5 and much additional utility in 5. I'd prefer if the WG was free to drop work item 4 in the event I'm correct. If 2 provides the human-friendly form and 5 provides the form that best leverages existing standard XML tools and parsers then I see no value in 4 which is both less human-friendly than 2 and less XML-tool-friendly than 5. In the event I'm wrong and there are significant semantic differences between 2/4 and 5 that are well justified, then I don't object to continued work on 4. I suggest adding a sentence to the charter: In the event work items 4 and 5 are semantically similar, the WG may choose to omit work item 4. I'm interested in other opinions on this topic. - Chris _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: WG Review: NETCONF Data Modeling Language (ne… Chris Newman
- Re: [NGO] WG Review: NETCONF Data Modeling Langua… Phil Shafer
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- Re: WG Review: NETCONF Data Modeling Language (ne… Andy Bierman
- RE: WG Review: NETCONF Data Modeling Language (ne… Bert Wijnen - IETF
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- Re: WG Review: NETCONF Data Modeling Language (ne… Randy Presuhn
- Re: WG Review: NETCONF Data Modeling Language (ne… David Partain
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- Re: WG Review: NETCONF Data Modeling Language (ne… David Partain
- RE: WG Review: NETCONF Data Modeling Language (ne… Bert Wijnen - IETF
- Re: WG Review: NETCONF Data Modeling Language (ne… David Partain
- Re: WG Review: NETCONF Data Modeling Language (ne… Andy Bierman
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- RE: WG Review: NETCONF Data Modeling Language (ne… Bert Wijnen - IETF
- RE: WG Review: NETCONF Data Modeling Language (ne… Bert Wijnen - IETF
- Re: WG Review: NETCONF Data Modeling Language (ne… David Partain
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- Re: WG Review: NETCONF Data Modeling Language (ne… Randy Presuhn
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- Re: WG Review: NETCONF Data Modeling Language (ne… Dave Crocker
- Re: WG Review: NETCONF Data Modeling Language (ne… Randy Presuhn
- RE: WG Review: NETCONF Data Modeling Language (ne… David Harrington
- Re: WG Review: NETCONF Data Modeling Language (ne… Harald Alvestrand
- Re: WG Review: NETCONF Data Modeling Language (ne… David Partain
- Re: WG Review: NETCONF Data Modeling Language (ne… Eric Rescorla
- Re: WG Review: NETCONF Data Modeling Language (ne… Andy Bierman
- Rough consensus among WHOM? Dave Crocker
- RE: WG Review: NETCONF Data Modeling Language (ne… Mehmet Ersue
- RE: WG Review: NETCONF Data Modeling Language (ne… Bert Wijnen - IETF
- Re: WG Review: NETCONF Data Modeling Language (ne… Michael Thomas
- RE: WG Review: NETCONF Data Modeling Language (ne… David Harrington
- Re: WG Review: NETCONF Data Modeling Language (ne… Andy Bierman
- RE: WG Review: NETCONF Data Modeling Language (ne… Leslie Daigle
- Re: WG Review: NETCONF Data Modeling Language (ne… Wes Hardaker
- Re: WG Review: NETCONF Data Modeling Language (ne… Tom.Petch
- Re: WG Review: NETCONF Data Modeling Language (ne… David Partain
- Re: WG Review: NETCONF Data Modeling Language (ne… Bernard Aboba
- RE: WG Review: NETCONF Data Modeling Language (ne… David Harrington
- Re: WG Review: NETCONF Data Modeling Language (ne… Bernard Aboba
- Re: WG Review: NETCONF Data Modeling Language (ne… Randy Presuhn