IETF Logo Mail Archive

RE: analysis of YANG vs. RELAX NG

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 28 November 2007 13:24 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 1IxMuI-0000X4-6G; Wed, 28 Nov 2007 08:24:50 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IxMuH-0000Wt-Bb for discuss-confirm+ok@megatron.ietf.org; Wed, 28 Nov 2007 08:24:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxMuH-0000Wj-1g for discuss@apps.ietf.org; Wed, 28 Nov 2007 08:24:49 -0500
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100] helo=nj300815-nj-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxMuG-00006F-Ic for discuss@apps.ietf.org; Wed, 28 Nov 2007 08:24:49 -0500
X-IronPort-AV: E=Sophos;i="4.23,224,1194238800"; d="scan'208";a="81910981"
Received: from 5.6.8.135.in-addr.arpa (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 28 Nov 2007 08:24:48 -0500
X-IronPort-AV: E=Sophos;i="4.23,224,1194238800"; d="scan'208";a="128925070"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 28 Nov 2007 08:24:44 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: analysis of YANG vs. RELAX NG
Date: Wed, 28 Nov 2007 14:22:21 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04683C74@307622ANEX5.global.avaya.com>
In-Reply-To: <474D6A11.50708@it.su.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: analysis of YANG vs. RELAX NG
Thread-Index: AcgxwPHzbMyxF903RjGHT2k+zOU98AAAIELA
References: <20071127.130355.18118495.mbj@tail-f.com> <474C116A.1080001@it.su.se><20071127163727.GA27816@elstar.local><03A9505C-36BB-4C69-9626-8FFADE5BFC68@osafoundation.org> <474D6A11.50708@it.su.se>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Leif Johansson" <leifj@it.su.se>, "Lisa Dusseault" <lisa@osafoundation.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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


 
 

> -----Original Message-----
> From: Leif Johansson [mailto:leifj@it.su.se] 
> Sent: Wednesday, November 28, 2007 3:16 PM
> To: Lisa Dusseault
> Cc: discuss@apps.ietf.org
> Subject: Re: analysis of YANG vs. RELAX NG
> 
> 
> >
> > My experience with description languages or other formalizations is 
> > that these often take the place of proper specification.  Authors 
> > think that they are done when they've written the code that 
> describes 
> > the format.  However, the most important aspect to a new standard 
> > schema is usually what it *means*.
> >
> I could not agree more. A formal language *can* make the 
> specification more precise and less readable (and useful) at 
> the same time.
> 
> Having said that I've found that using formal languages for 
> ontologies can help, especially if you actually plan on 
> producing "stuff" from the ontology (code for instance). I 
> don't think MIBs would be very useful if they were written in 
> English :-)
> 
>     Cheers Leif
> 

Well, actually the common practice is that MIBs take a mid-way approach
using a formal data language and plain English DESCRIPTION clauses
associated with the definition of each object. 

Dan

v2.8.7 | Report a Bug | By Email