Re: [mmox] LLSD
"Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com> Fri, 20 February 2009 04:09 UTC
Return-Path: <infinity@lindenlab.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 37F543A6B7B for <mmox@core3.amsl.com>; Thu, 19 Feb 2009 20:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 hKy843H3l9dW for <mmox@core3.amsl.com>; Thu, 19 Feb 2009 20:09:54 -0800 (PST)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id 0BB0E3A6B0C for <mmox@ietf.org>; Thu, 19 Feb 2009 20:09:54 -0800 (PST)
Received: from [192.168.1.11] (dsl-63-249-112-43.cruzio.com [63.249.112.43]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tammy.lindenlab.com (Postfix) with ESMTP id 854613DBC45C; Thu, 19 Feb 2009 20:10:07 -0800 (PST)
Message-Id: <C803B307-0984-40AE-946A-00EDDA664502@lindenlab.com>
From: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
To: Charles Krinke <cfk@pacbell.net>
In-Reply-To: <29656.28734.qm@web82607.mail.mud.yahoo.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-2--902231836"
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 19 Feb 2009 20:10:05 -0800
References: <62BFE5680C037E4DA0B0A08946C0933D501FE18E@rrsmsx506.amr.corp.intel.com> <80E946E9-5C62-4E00-BE8C-A15513898F99@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933D50262DA8@rrsmsx506.amr.corp.intel.com> <29656.28734.qm@web82607.mail.mud.yahoo.com>
X-Mailer: Apple Mail (2.930.3)
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] LLSD
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: Fri, 20 Feb 2009 04:09:55 -0000
http://wiki.secondlife.com/wiki/MMOX is non-authoritative, but yes LLSD is one of the work items we have on the list. the objective of LLSD is to provide an abstract type system with multiple serializations. it also defines the mime types. however, to say that the LLSD draft exists only to define the serializations is akin to saying that ASN.1 exists only to provide input into DER or BER encodings. the two are linked, but each has a particular use. LLSD as an abstract type system allows us to define and reason about the semantics of structured data used in PDUs independent of an existing implementation language. the serialization rules allow us to format structured data prior to transport and later de-serialize it after receipt. the MIME type registrations allow us to identify the serialization scheme used on transports that support the use of MIME types. LLIDL (pronounced "little") defines the set of expected parameters to and responses from a resource access. LLSD was selected as the first draft to work on as it is used as a building block for other protocol interactions, some of which are published in draft form on the second life wiki. the further development of these protocols is also considered a task of the proposed working group. -cheers -meadhbh On Feb 19, 2009, at 7:52 PM, Charles Krinke wrote: > In looking at the secondlife wiki at http://wiki.secondlife.com/wiki/MMOX > it looks like one of the first proposals for this working group is > the LLSD draft specification. > > Am I correct in that the gist of the LLSD specification is > essentially to propose three mime formats and thats about it for now? > > application/llsd+xml > application/llsd+json > application/llsd+binary > > Charles > _______________________________________________ > mmox mailing list > mmox@ietf.org > https://www.ietf.org/mailman/listinfo/mmox
- [mmox] More LLIDL questions Hurliman, John
- Re: [mmox] More LLIDL questions Mark Lentczner
- Re: [mmox] More LLIDL questions Hurliman, John
- [mmox] LLSD Charles Krinke
- Re: [mmox] LLSD Meadhbh Hamrick (Infinity)
- Re: [mmox] More LLIDL questions Meadhbh Hamrick (Infinity)
- Re: [mmox] LLSD Charles Krinke
- Re: [mmox] LLSD Meadhbh Hamrick (Infinity)
- Re: [mmox] More LLIDL questions Hurliman, John
- Re: [mmox] LLSD Charles Krinke
- Re: [mmox] LLSD Jesrad
- Re: [mmox] LLSD Charles Krinke
- Re: [mmox] More LLIDL questions Mark Lentczner
- Re: [mmox] LLSD Meadhbh Hamrick (Infinity)
- [mmox] LLSD and content schema Jon Watte
- Re: [mmox] LLSD and content schema Morgaine
- Re: [mmox] LLSD and content schema Meadhbh Hamrick (Infinity)
- Re: [mmox] LLSD and content schema Jon Watte
- Re: [mmox] LLSD and content schema Lisa Dusseault
- Re: [mmox] LLSD and content schema Jon Watte