Re: [Rfid] XML vs. Text vs. Binary

Marshall Rose <mrose+internet.ietf.rfid@dbc.mtview.ca.us> Sat, 23 July 2005 03:47 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwAyk-0004AH-Ry; Fri, 22 Jul 2005 23:47:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwAyh-00047b-ML for rfid@megatron.ietf.org; Fri, 22 Jul 2005 23:47:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05578 for <rfid@ietf.org>; Fri, 22 Jul 2005 23:47:04 -0400 (EDT)
Received: from [24.244.171.76] (helo=mail.sarbserve.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DwBT0-0005Bc-TX for rfid@ietf.org; Sat, 23 Jul 2005 00:18:30 -0400
Received: from [IPv6:::1] (mrose@localhost.localdomain [127.0.0.1]) by mail.sarbserve.com (8.13.4/8.13.4/Debian-3) with ESMTP id j6N3i9e4030139; Fri, 22 Jul 2005 20:44:11 -0700
In-Reply-To: <p062007ccbf06aca8d9aa@[192.168.1.105]>
References: <0E03681B885F3B4296B999E34435A16E01234C2B@ms08.mse3.exchange.ms> <p062007c3bf05ec0041ed@[192.168.1.105]> <B327225C-65DB-44B2-859C-F645C2A36AA1@dbc.mtview.ca.us> <p062007ccbf06aca8d9aa@[192.168.1.105]>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <DD9FF084-9F10-4098-B930-5893CDB93935@dbc.mtview.ca.us>
Content-Transfer-Encoding: 7bit
From: Marshall Rose <mrose+internet.ietf.rfid@dbc.mtview.ca.us>
Subject: Re: [Rfid] XML vs. Text vs. Binary
Date: Sat, 23 Jul 2005 09:16:35 +0530
To: Margaret Wasserman <margaret@thingmagic.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: rfid@ietf.org
X-BeenThere: rfid@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Control and Access of Infrastructure for RFID Operations Discussion List <rfid.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rfid>
List-Post: <mailto:rfid@lists.ietf.org>
List-Help: <mailto:rfid-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=subscribe>
Sender: rfid-bounces@lists.ietf.org
Errors-To: rfid-bounces@lists.ietf.org

margaret - apologies, for not quoting from your email, but i think  
the issues i raised in my original reply remain untouched, or perhaps  
are now amplified by your reply.

the problem is agreeing on a subset is that we now have to design/ 
write/debug/use an entirely different set of libraries than the  
"standard" ones. it takes both hands to count the number of different  
encoding rules that have been defined/implemented for use with ASN.1  
over the years. none of them achieved anywhere near the usage of the  
original BER, which was the thing that folks were complaining about  
to begin with.

in other words, the compromise becomes more complicated than either  
purist extreme; it  looks like one of those little white lies one  
tells in polite company that, over the course of the comversation,  
have to become increasingly more complex so as to avoid discovery  
through contradiction or non-sequitor.

this brings us back full circle: as soon as you have any level of  
nesting, human type-in becomes problematic. as soon as you decide  
that human type-in isn't mandatory, it is trivial to include a  
standard library to do the heavy lifting while the humans invoke the  
tool using textual commands.

in other words, from where i sit, XML, cXML, etc., enjoy all the  
drawbacks of both purist approaches.

/mtr






_______________________________________________
Rfid mailing list
Rfid@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/rfid