Re: [vwrap] Working Draft: SNOW-375

Dzonatas Sol <dzonatas@gmail.com> Tue, 03 August 2010 16:17 UTC

Return-Path: <dzonatas@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15A213A6974 for <vwrap@core3.amsl.com>; Tue, 3 Aug 2010 09:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599]
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 2LlaTm4qY+No for <vwrap@core3.amsl.com>; Tue, 3 Aug 2010 09:17:48 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id EB3453A6937 for <vwrap@ietf.org>; Tue, 3 Aug 2010 09:17:47 -0700 (PDT)
Received: by pvd12 with SMTP id 12so1940266pvd.31 for <vwrap@ietf.org>; Tue, 03 Aug 2010 09:18:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=vZ2rHxYK4mnj379dnpCEqPqHFY1DVJ9GraELNHtc9WQ=; b=vwovI2gkCBqlu2s/2JAnmB8KRHFTDbbzei20IcbROBpXezxb/JohN0mAJXMwAgDy/Q jo1xBPDyuOmsRRwiyXFWFkfre9RDa74yCMxIhJXlXSHoXAG/ETLo6ZJps3YdMFAeUpsK Rz3Av5ilgQKdAdYbQNaIJb87AcKeqa/PI3xgs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=LXqZqVXUVaEcnVU0qIKVDih9AzLPFAssGYnaesipF2GnpJdRGqKIXKv0meUoKfCgcG wFcoAk1Cfro2aEFV667VbnzhUIIue6hBicz65oPH23i97dZJiJnh8xhVC2tg5C0js4wS iOayy0++7Y82Ykq09zV8wZyd342EtBIEx2JAQ=
Received: by 10.142.215.7 with SMTP id n7mr6780802wfg.194.1280852296646; Tue, 03 Aug 2010 09:18:16 -0700 (PDT)
Received: from [192.168.0.50] (adsl-68-124-103-250.dsl.scrm01.pacbell.net [68.124.103.250]) by mx.google.com with ESMTPS id y16sm9351100wff.2.2010.08.03.09.18.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 03 Aug 2010 09:18:15 -0700 (PDT)
Message-ID: <4C58443F.80502@gmail.com>
Date: Tue, 03 Aug 2010 09:30:55 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100329)
MIME-Version: 1.0
To: Dzonatas Sol <dzonatas@gmail.com>, "vwrap@ietf.org" <vwrap@ietf.org>
References: <4C542CAC.1090301@gmail.com> <AANLkTinLVdcwHGWWuXztN6EnBA5jL56iaRvX9pR54vOX@mail.gmail.com> <4C572A6E.8070905@gmail.com> <AANLkTik1ukKWhNcJ0TgWfREf0YCd_oLutcxk8_j4b+=e@mail.gmail.com> <4C573C43.5060905@gmail.com>
In-Reply-To: <4C573C43.5060905@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [vwrap] Working Draft: SNOW-375
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2010 16:17:49 -0000

Dzonatas Sol wrote:
>
> I don't see how JSON is an improvement from that.
>
> --- https://twitter.com/Dzonatas_Sol ---
> Web Development, Software Engineering, Virtual Reality, Consultant
>
>

In fact, JSON's best feature is being able to do the eval(), yet those 
of us that written VMs should already know this. Verification killed 
that feature when they tried to use it in out-of-domain style.

On that note, I suggest to change the VWRAP docs where if people request 
JSON (i.e. "application/json-*" ) that they actually want RSS or ATOM 
styled structures. Instead, only offer RSS or ATOM structured JSON (i.e. 
"application/json-atom" ). If they want more raw than that, then it just 
makes sense to use XML. It's too costly for "us", and they don't realize it.

There may be other formats besides RSS or ATOM, so its not a moratorium, 
yet these two are popular solutions already well established. I'm sure 
different audiences are going to quibble, but I leave it up to you to 
decide on support steps to change and how to present them.

-- 
--- https://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering, Virtual Reality, Consultant