Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt
"Natale, Bob" <RNATALE@mitre.org> Wed, 04 February 2009 13:18 UTC
Return-Path: <RNATALE@mitre.org>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8CF428C236 for <opsawg@core3.amsl.com>; Wed, 4 Feb 2009 05:18:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 3mQmUOwaCjqC for <opsawg@core3.amsl.com>; Wed, 4 Feb 2009 05:17:58 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 49E4E28C114 for <opsawg@ietf.org>; Wed, 4 Feb 2009 05:17:58 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n14DHblw004256 for <opsawg@ietf.org>; Wed, 4 Feb 2009 08:17:37 -0500
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n14DHb5I004247; Wed, 4 Feb 2009 08:17:37 -0500
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Wed, 4 Feb 2009 08:17:37 -0500
From: "Natale, Bob" <RNATALE@mitre.org>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Date: Wed, 04 Feb 2009 08:17:35 -0500
Thread-Topic: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt
Thread-Index: AcmGrvaD3XLdpr7sRY2f3vQ7vL18rwAGpE6A
Message-ID: <17969D855F28964C88D177D45B6CDF11F22974C5@IMCMBX2.MITRE.ORG>
References: <20090130021022.B4DA312DC3E3@newdev.eecs.harvard.edu> <0D6B0A42F7EE4DA1B50DC45C2990A849@BertLaptop>
In-Reply-To: <0D6B0A42F7EE4DA1B50DC45C2990A849@BertLaptop>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_17969D855F28964C88D177D45B6CDF11F22974C5IMCMBX2MITREORG_"
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 13:18:04 -0000
Hi Bert, Thanks for your comments and assessment. - The misspellings of "opaque" (with a "g") have been corrected. - The use of "datatypes" in the file name and title was, in fact, intended to refer to "SMI datatypes" as implied by the general usage in RFC 2578, Sec. 7.1, "Mapping of the Syntax Clause", to wit: "The SYNTAX clause, which must be present, defines the abstract data structure corresponding to that object. The data structure must be one of the following: a base type, the BITS construct, or a textual convention. (SEQUENCE OF and SEQUENCE are also possible for conceptual tables, see section 7.1.12). The base types are those defined in the ObjectSyntax CHOICE. A textual convention is a newly-defined type defined as a sub-type of a base type [3]." So, "datatypes" is used a bit loosely for "base types"...would you prefer that the latter term be used? (The document text currently makes it clear that it deals only with expressing the base types of RFC 2578 in XSD.) - Yes, the text that Juergen questioned is being removed (also had helpful guidance from David Harrington on this point), so that this "base types" document stands alone. Please confirm or clarify the second point...I will have the -05 version, reflecting final mods based on this last call round, ready immediately after expiration of the last call period (12-Feb-09). Cheers, BobN From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of Bert Wijnen (IETF) Sent: Wednesday, February 04, 2009 4:57 AM To: opsawg@ietf.org Subject: Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-datatypes-in-xsd-04.txt My comments: - page 7, section 4 - speaks about opague. I think you mean opaque (with a Q) You may also want to make an explicit statement that those are the datatype names as ytou specify them in XSD. I first though they were the datatypes as specified in SMIv2. - Opague (with a G) is again used in the 1st para of sect 5.3 and in the first bullet on page 12 and also 3rd bullet. I share/support Juergen Shoenwaelder's comment w.r.t. the discussion about 3 documents in a document set. Where, how is that otehr work scheduled/planned? Other than that, this document seems fine. Bert ----- Original Message ----- From: Scott O. Bradner<mailto:sob@harvard.edu> To: opsawg@ietf.org<mailto:opsawg@ietf.org> Sent: Friday, January 30, 2009 3:10 AM Subject: Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-datatypes-in-xsd-04.txt back on Nov 6th we sent out a WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt there was no response to that last call that I can find in the mail list archive (or in my memory) we gotta see a bit more interest than that to proceed with this document. So, I'll try again this is a WGLC for draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt please comment (one way or the other) by Feb 12 tnx Scott _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org<mailto:OPSAWG@ietf.org> https://www.ietf.org/mailman/listinfo/opsawg
- [OPSAWG] start WGLC on draft-ietf-opsawg-smi-data… Scott O. Bradner
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Scott O. Bradner
- Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-d… Romascanu, Dan (Dan)
- Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-d… Juergen Schoenwaelder
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Natale, Bob
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Mark Ellison
- Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-d… Bert Wijnen (IETF)
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Natale, Bob
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Mark Ellison
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Natale, Bob
- [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-datat… Ersue, Mehmet (NSN - DE/Munich)
- [OPSAWG] WGLC on draft-ietf-opsawg-smi-datatypes-… David B Harrington
- Re: [OPSAWG] WGLC on draft-ietf-opsawg-smi-dataty… Natale, Bob