[Simple] Prescaps rep of token types

Paul Kyzivat <pkyzivat@cisco.com> Mon, 01 November 2004 17:03 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03628; Mon, 1 Nov 2004 12:03:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COfpl-0004IE-AB; Mon, 01 Nov 2004 12:19:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COf9g-0001WE-BO; Mon, 01 Nov 2004 11:35:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COekn-0002Du-Ft for simple@megatron.ietf.org; Mon, 01 Nov 2004 11:09:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26677 for <simple@ietf.org>; Mon, 1 Nov 2004 11:09:56 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COezi-0002Oa-DO for simple@ietf.org; Mon, 01 Nov 2004 11:25:23 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 01 Nov 2004 08:19:29 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA1G9GnC025340; Mon, 1 Nov 2004 08:09:17 -0800 (PST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMR94935; Mon, 1 Nov 2004 11:09:21 -0500 (EST)
Message-ID: <41865FB1.7080700@cisco.com>
Date: Mon, 01 Nov 2004 11:09:21 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mikko.lonnfors@nokia.com
References: <F87691D52CF92D4681560F97B237AAAA7FF160@esebe051.ntc.nokia.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: simple@ietf.org
Subject: [Simple] Prescaps rep of token types
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
Sender: simple-bounces@ietf.org
Errors-To: simple-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

I like the change in the representation for token-valued features, to 
the form that has <supported> and <notsupported> elements.

However, I am concerned about defining xml elements for each token. This 
begins to look like ASN.1 that most people seem to hate. It requires an 
excessive amount of schema definition, and makes it impossible to 
represent a value for which no schema definition is present.

I think it would be preferable to define them all the way <languages> is 
defined, with the individual tokens simply being defined as strings.

	Paul


_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple