[mmox] Basic data description

Catherine Pfeffer <cathypfeffer@gmail.com> Mon, 23 February 2009 10:58 UTC

Return-Path: <cathypfeffer@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AAD828C10B for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 02:58:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 NnYG9fplgFJY for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 02:58:23 -0800 (PST)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by core3.amsl.com (Postfix) with ESMTP id D258E28C20A for <mmox@ietf.org>; Mon, 23 Feb 2009 02:58:22 -0800 (PST)
Received: by nf-out-0910.google.com with SMTP id d3so366931nfc.39 for <mmox@ietf.org>; Mon, 23 Feb 2009 02:58:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=UquVtXsIxBFeahAEmT2ySKP50WJz0rFh84bX2S21YjE=; b=aGkX8+1FCVyhu9jTR6qr7hY9U4c9/N3YThImdlj/PV5NMBPfLFab25X8q1OT2VNmYD JZbOJfXg1br4U6a+g5eOY7yc5fbgMuPp7YgTN5rbSIVU/dJm2iwqINwqGNcaewdGpd+V dczeTahJRSTEYXIKWo+0EbMWeYQqeTWuLBW+c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=nAid2B0YXFufCa22HyaQNpVCbG073ho08HZMDaJvRzRbQI60xgD4SsPX0ESQNbUfX3 vQh4dn9pxtV30T1UNsM9zTidTSk11Qgphcgz5wtOjeu7I/CRMvqrUAznQwXkhueIrvVA NopXM3EhInSU9VBIFe59zVhLoD+9b4/2ICgy0=
MIME-Version: 1.0
Received: by 10.210.87.19 with SMTP id k19mr3363732ebb.75.1235386719883; Mon, 23 Feb 2009 02:58:39 -0800 (PST)
Date: Mon, 23 Feb 2009 11:58:39 +0100
Message-ID: <ebe4d1860902230258q4acf9431i533a5cae2fba7c8c@mail.gmail.com>
From: Catherine Pfeffer <cathypfeffer@gmail.com>
To: mmox@ietf.org
Content-Type: multipart/alternative; boundary="0015174c3c6099533e046393e23a"
Subject: [mmox] Basic data description
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 10:58:24 -0000

Jon Watte said:
> At a minimum, I think that "publication of LLSD draft" should be changed
> to something worded like "publication of a basic data description and
> serialization formats RFC."

Yes. That would allow an approach that is not biased towards LLSD, even
though LLSD remains a very valid potential choice.

I can see another reason for doing that. IETF, in my understanding, is a
communication standards organism. That means that abstract data types is out
of their mission, just like a programming language or an algorithm would be.
But serialization formats definitely are within their mission. So putting
the emphasis on the "serialization" part would, IMHO, help stick to their
mission statement.

-- 
Cathy