Re: [MIB2RDML] Expressing SNMP SMI Datatypes in XML Schema Definition Language -03 draft submitted

Mark Ellison <Mark@EllisonSoftware.com> Mon, 28 July 2008 20:28 UTC

Return-Path: <mib2rdml-bounces@ietf.org>
X-Original-To: mib2rdml-archive@optimus.ietf.org
Delivered-To: ietfarch-mib2rdml-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA49C3A6B0C; Mon, 28 Jul 2008 13:28:17 -0700 (PDT)
X-Original-To: mib2rdml@core3.amsl.com
Delivered-To: mib2rdml@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53B803A6B0A for <mib2rdml@core3.amsl.com>; Mon, 28 Jul 2008 13:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level:
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_210=0.6, J_CHICKENPOX_29=0.6]
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 3u3h9kZ8db4L for <mib2rdml@core3.amsl.com>; Mon, 28 Jul 2008 13:28:15 -0700 (PDT)
Received: from omr11.networksolutionsemail.com (omr11.networksolutionsemail.com [205.178.146.61]) by core3.amsl.com (Postfix) with ESMTP id 4513E3A6B09 for <mib2rdml@ietf.org>; Mon, 28 Jul 2008 13:28:15 -0700 (PDT)
Received: from mail.networksolutionsemail.com (ns-omr11.mgt.hosting.dc2.netsol.com [10.49.6.74]) by omr11.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id m6SKSI05022400 for <mib2rdml@ietf.org>; Mon, 28 Jul 2008 16:28:25 -0400
Received: (qmail 28306 invoked by uid 78); 28 Jul 2008 20:28:17 -0000
Received: from unknown (HELO ?192.168.1.205?) (mark@ellisonsoftware.com@71.168.120.104) by ns-omr11.lb.hosting.dc2.netsol.com with SMTP; 28 Jul 2008 20:28:17 -0000
Message-ID: <488E2C7C.8010409@EllisonSoftware.com>
Date: Mon, 28 Jul 2008 16:30:52 -0400
From: Mark Ellison <Mark@EllisonSoftware.com>
Organization: Ellison Software Consulting, Inc.
User-Agent: Thunderbird 2.0b2 (X11/20070116)
MIME-Version: 1.0
To: j.schoenwaelder@jacobs-university.de
References: <4915F014FDD99049A9C3A8C1B832004F0277F329@IMCSRV2.MITRE.ORG> <4915F014FDD99049A9C3A8C1B832004F027F586E@IMCSRV2.MITRE.ORG> <4915F014FDD99049A9C3A8C1B832004F02DB3EFD@IMCSRV2.MITRE.ORG> <4915F014FDD99049A9C3A8C1B832004F02E47157@IMCSRV2.MITRE.ORG> <488E196F.2080304@EllisonSoftware.com> <20080728191837.GA9535@elstar.local>
In-Reply-To: <20080728191837.GA9535@elstar.local>
Cc: mib2rdml@ietf.org, opsawg@ietf.org
Subject: Re: [MIB2RDML] Expressing SNMP SMI Datatypes in XML Schema Definition Language -03 draft submitted
X-BeenThere: mib2rdml@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ellison@ieee.org
List-Id: converting MIB modules into resource models <mib2rdml.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib2rdml>, <mailto:mib2rdml-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mib2rdml>
List-Post: <mailto:mib2rdml@ietf.org>
List-Help: <mailto:mib2rdml-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib2rdml>, <mailto:mib2rdml-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1180444973=="
Sender: mib2rdml-bounces@ietf.org
Errors-To: mib2rdml-bounces@ietf.org

Hi Juergen,

Thanks for this reply.  My comments/clarifications are inline, below.

On 07/28/2008 03:18 PM, Juergen Schoenwaelder wrote:
> On Mon, Jul 28, 2008 at 03:09:35PM -0400, Mark Ellison wrote:
>
>   
>> - In section 5.2, "OctetString", second paragraph says "each octet is  
>> encoded as two hexadecimal digits" and the third bullet indicates the  
>> "maxLength" restriction of 65535 octets.  However, the xs:simpleType  
>> "OctetString" definition in section 4 indicates an xs:maxLength  
>> value="65535".  If the intent is to represent 65535 octets then the  
>> xs:maxLength value should be twice this number, "131070".
>>     
>
> I think the maxLength restriction is counted in the number of decoded
> bytes not the number of bytes needed for the encoding. Please check
> section 4.3.3 of <http://www.w3.org/TR/xmlschema-2/>. (I did run into
> this before; perhaps it is worth adding a comment so that we do not
> run into this question again - or worse someone "fixes" this later
> on.)
>
>   
Good- section  4.3.3 of <http://www.w3.org/TR/xmlschema-2/> is helpful, 
I see now how I became confused by the current text in the second 
paragraph.  I agree with your suggestion to add some text/comment to 
clarify.
>> - [more of a personal wish] In section 5.5, "ObjectIdentifier", I  
>> realize the text is written to be faithful to the definition of the SMI  
>> OBJECT IDENTIFIER.  In this regard, it is probably not appropriate to  
>> place support for "OID fragments" here.  I find I use a lot of OID  
>> fragments (1 or more subids that do not have the initial 2 subid  
>> restrictions) to represent instance components for a set of related  
>> OBJECT-TYPE OIDs.  Possibly there is a place, either in this memo, or in  
>> another related memo to support the notion of an OID fragment?  I  
>> suppose I could use the ObjectIdentifier "as is" by prepending any  
>> fragment with 1.1, but I regard this as a programmatic contortion with  
>> undesirable overhead.
>>     
>
> Your ObjectIdentifierFragment simply is not an ObjectIdentifier...
>   
Yes I agree with this- hopefully there is a proper place for defining an 
ObjectIdentifierFragment...
> /js
>   
Thanks,

Mark

_______________________________________________
MIB2RDML mailing list
MIB2RDML@ietf.org
https://www.ietf.org/mailman/listinfo/mib2rdml