
From carlo@alinoe.com  Mon Nov  2 03:49:51 2009
Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D6E13A685A for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 03:49:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.876
X-Spam-Level: 
X-Spam-Status: No, score=0.876 tagged_above=-999 required=5 tests=[AWL=-0.294,  BAYES_50=0.001, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 YVjkk-TwDm4i for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 03:49:50 -0800 (PST)
Received: from viefep16-int.chello.at (viefep16-int.chello.at [62.179.121.36]) by core3.amsl.com (Postfix) with ESMTP id 2519E3A6819 for <ogpx@ietf.org>; Mon,  2 Nov 2009 03:49:49 -0800 (PST)
Received: from edge02.upc.biz ([192.168.13.237]) by viefep16-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20091102115008.HYIW27636.viefep16-int.chello.at@edge02.upc.biz>; Mon, 2 Nov 2009 12:50:08 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge02.upc.biz with edge id 0Bq51d0Lg0FlQed02Bq7RJ; Mon, 02 Nov 2009 12:50:08 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1N4vPd-0004sb-Qb; Mon, 02 Nov 2009 12:49:29 +0100
Date: Mon, 2 Nov 2009 12:49:29 +0100
From: Carlo Wood <carlo@alinoe.com>
To: Joshua Bell <josh@lindenlab.com>
Message-ID: <20091102114929.GA19073@alinoe.com>
References: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com> <3a880e2c0910160116g7a7e488fpe03b10d9b534aa35@mail.gmail.com> <9b8a8de40910160635j268ef9c9mae55781221c94d7e@mail.gmail.com> <20091029134353.GB2298@alinoe.com> <e0b04bba0910300029jd385ea7s1ab66a6d67b084d4@mail.gmail.com> <f72742de0910301023i266832d3ta7c96cc13985e959@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f72742de0910301023i266832d3ta7c96cc13985e959@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Tourist use case
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2009 11:49:51 -0000

Using common sense, I'd say:

* If you try to rez an object, policy comes in to determine if that is allowed.

* Once an object is rezzed, EVERYONE that is in the region (that is allowed to
  enter the region thus) can SEE that object (and interact with it).

I realize that it is *possible* for the region to implement a policy
where it selectively shows data to some people and not to others, but
I don't think we have to officially support every possible way to screw
up shared experience in VWRAP, just because it would be possible to do so.

Compare with a protocol like SMPT: that dictates that if some email is
received, it is required to react in one of a few given ways. There are
other ways, but that would make the system stop functioning as intended,
so that is Not The Idea.


I agree with you that information needed to see a rezzed object should
come from the region (simulator), so -- in principle there is no direct
reason that a viewer needs to have access to every asset server whose
assets are rezzed.


An interesting question is now: what about assets that make up an
avatar? Once in-world, attaching a new attachment, or changing clothes
or shape, is just the same as rezzing of course: if the asset server
allows access (by that region) than the region can buffer it and show
it to everyone; otherwise attachment, or change of appearance, is disallowed.
However, in the case of teleportation I think we need to act more
intelligent than just black or white (allow or disallow the TP):
I'm in favour of allowing the TP independent of assets being used at
that moment, but instead detach assets and/or Ruth the avatar if
need be (at least, give the user that option).

On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:
> Be careful about blurring the use of "asset services" between "stuff in
> regions" and "stuff I have". I think there is a big intersection - and may have
> the same characteristics and/or protocols, but I also think they are are
> distinct. I would guess that there will be asset services associated with both
> agents and regions - off the top of my head:
> 
> Uses of an agent-associated "asset" service:
> * content to client app (inspect your inventory)
> * content from client app (upload/import to inventory)
> * content to region (rez something)
> * content from region (buy/take something)
> * content to agent (give something)
> * content from agent (receive something)
> 
> Uses of an region-associated "asset" service:
> * content to client app (see the world)
> * content from client app (upload/import to region)
> * content to region (during teleport/region crossing)
> * content from region (during teleport/region crossing)
> * content to agent (buy/take something)
> * content from agent (rez something)
> 
> I'm using "asset" in quotes since that term may be overloaded. "Content" might
> be a better term.

-- 
Carlo Wood <carlo@alinoe.com>

From morgaine.dinova@googlemail.com  Mon Nov  2 06:04:46 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FA803A659B for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 06:04:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.628
X-Spam-Level: 
X-Spam-Status: No, score=-0.628 tagged_above=-999 required=5 tests=[AWL=-0.141, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, 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 8Z3AdPwWAYio for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 06:04:45 -0800 (PST)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by core3.amsl.com (Postfix) with ESMTP id AB1B73A6944 for <ogpx@ietf.org>; Mon,  2 Nov 2009 06:04:44 -0800 (PST)
Received: by ey-out-2122.google.com with SMTP id 25so422579eya.51 for <ogpx@ietf.org>; Mon, 02 Nov 2009 06:05:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=vAtvVuP47KByGaOUwufAoA/HibypXVnSeBkLT758G4s=; b=K3Taqb5J54jw9pvDIPLkr/yzpeZ4R2PRpvLO8KXAU+g1Rg2r/17fpvpvkHL77ueb94 OfyO+KmKPJP0pR0p8ZC5rsfrl1ajGv7Lrbr96ImIRwGqFoi3pESOYtiLySIhrHoEzMKr X6rthDJdJiwLed2S87lKHVTj93oiD+yiuRmfQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=W6N4M2e0vQ6PnzBsyKF0T9hOManYy7mhE22mO1/xxilH46dXtoOcYc3y1Np0V/N+BU c08TACUu3lwuZ6ltq9mrTnyl6/AK6NSLQXJq07Ih0I39S2b24xU99nP98CNqK+xwKzjl 3+cjessqZY/mEWMgiTbJvnjrI8HoDbsRdr9d8=
MIME-Version: 1.0
Received: by 10.216.87.203 with SMTP id y53mr4538485wee.177.1257170700828;  Mon, 02 Nov 2009 06:05:00 -0800 (PST)
In-Reply-To: <20091102114929.GA19073@alinoe.com>
References: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com> <3a880e2c0910160116g7a7e488fpe03b10d9b534aa35@mail.gmail.com> <9b8a8de40910160635j268ef9c9mae55781221c94d7e@mail.gmail.com> <20091029134353.GB2298@alinoe.com> <e0b04bba0910300029jd385ea7s1ab66a6d67b084d4@mail.gmail.com> <f72742de0910301023i266832d3ta7c96cc13985e959@mail.gmail.com> <20091102114929.GA19073@alinoe.com>
Date: Mon, 2 Nov 2009 14:05:00 +0000
Message-ID: <e0b04bba0911020605k2e097f3fx58a91f8d9c69cdee@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d9a3290b8baf047763dde5
Subject: Re: [ogpx] Tourist use case
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2009 14:04:46 -0000

--0016e6d9a3290b8baf047763dde5
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:

>
> I agree with you that information needed to see a rezzed object should
> come from the region (simulator), so -- in principle there is no direct
> reason that a viewer needs to have access to every asset server whose
> assets are rezzed.
>


The region certainly needs to indicate *which* objects are rezzed in it ---
it is the single authority that holds that information --- there is no other
place where this information could come from in the current model.

However, that does not mean that it has to actually *hold* the data, but
merely to indicate *which it is *so that it can be fetched.  Indeed, *
requiring* the region to hold the data or to proxy it would be really bad
for protocol scalability.  In any case, that's a policy choice --- our
mechanism needs to be more flexible than this in its service endpoint
choices, and not *require* the data to come from the region.  It is highly
likely that many implementations will aim for higher scalability than is
possible to achieve by routing assets through a sim.  Indeed, that's a
primary reason for using caps for accessing decoupled services in a
REST-like manner.

Decoupling the simulation from the storage is one of the most important
things that this protocol will achieve if we get it right.  We probably do
need to ensure that SL's existing "proxy everything" model can be expressed
through appropriate policy or deployment choices as it is likely to be a
requirement, but this should not constrain what the protocol can do under
different policies or deployment scenarios.


Morgaine.






======================================

On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:

> Using common sense, I'd say:
>
> * If you try to rez an object, policy comes in to determine if that is
> allowed.
>
> * Once an object is rezzed, EVERYONE that is in the region (that is allowed
> to
>  enter the region thus) can SEE that object (and interact with it).
>
> I realize that it is *possible* for the region to implement a policy
> where it selectively shows data to some people and not to others, but
> I don't think we have to officially support every possible way to screw
> up shared experience in VWRAP, just because it would be possible to do so.
>
> Compare with a protocol like SMPT: that dictates that if some email is
> received, it is required to react in one of a few given ways. There are
> other ways, but that would make the system stop functioning as intended,
> so that is Not The Idea.
>
>
> I agree with you that information needed to see a rezzed object should
> come from the region (simulator), so -- in principle there is no direct
> reason that a viewer needs to have access to every asset server whose
> assets are rezzed.
>
>
> An interesting question is now: what about assets that make up an
> avatar? Once in-world, attaching a new attachment, or changing clothes
> or shape, is just the same as rezzing of course: if the asset server
> allows access (by that region) than the region can buffer it and show
> it to everyone; otherwise attachment, or change of appearance, is
> disallowed.
> However, in the case of teleportation I think we need to act more
> intelligent than just black or white (allow or disallow the TP):
> I'm in favour of allowing the TP independent of assets being used at
> that moment, but instead detach assets and/or Ruth the avatar if
> need be (at least, give the user that option).
>
> On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:
> > Be careful about blurring the use of "asset services" between "stuff in
> > regions" and "stuff I have". I think there is a big intersection - and
> may have
> > the same characteristics and/or protocols, but I also think they are are
> > distinct. I would guess that there will be asset services associated with
> both
> > agents and regions - off the top of my head:
> >
> > Uses of an agent-associated "asset" service:
> > * content to client app (inspect your inventory)
> > * content from client app (upload/import to inventory)
> > * content to region (rez something)
> > * content from region (buy/take something)
> > * content to agent (give something)
> > * content from agent (receive something)
> >
> > Uses of an region-associated "asset" service:
> > * content to client app (see the world)
> > * content from client app (upload/import to region)
> > * content to region (during teleport/region crossing)
> > * content from region (during teleport/region crossing)
> > * content to agent (buy/take something)
> > * content from agent (rez something)
> >
> > I'm using "asset" in quotes since that term may be overloaded. "Content"
> might
> > be a better term.
>
> --
> Carlo Wood <carlo@alinoe.com>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>

--0016e6d9a3290b8baf047763dde5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <span dir=3D"ltr">&lt;<a href=
=3D"mailto:carlo@alinoe.com">carlo@alinoe.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204,=
 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

<br><div style=3D"margin-left: 40px;">
I agree with you that information needed to see a rezzed object should<br>
come from the region (simulator), so -- in principle there is no direct<br>
reason that a viewer needs to have access to every asset server whose<br>
assets are rezzed.</div></blockquote><br><br>The region certainly needs to =
indicate <i><b>which</b></i> objects are rezzed in it --- it is the single =
authority that holds that information --- there is no other place where thi=
s information could come from in the current model.<br>
<br>However, that does not mean that it has to actually <b><i>hold</i></b> =
the data, but merely to indicate <b><i>which it is</i> </b>so that it can b=
e fetched.=A0 Indeed, <i>requiring</i> the region to hold the data or to pr=
oxy it would be really bad for protocol scalability.=A0 In any case, that&#=
39;s a policy choice --- our mechanism needs to be more flexible than this =
in its service endpoint choices, and not <i>require</i> the data to come fr=
om the region.=A0 It is highly likely that many implementations will aim fo=
r higher scalability than is possible to achieve by routing assets through =
a sim.=A0 Indeed, that&#39;s a primary reason for using caps for accessing =
decoupled services in a REST-like manner.<br>
<br>Decoupling the simulation from the storage is one of the most important=
 things that this protocol will achieve if we get it right.=A0 We probably =
do need to ensure that SL&#39;s existing &quot;proxy everything&quot; model=
 can be expressed through appropriate policy or deployment choices as it is=
 likely to be a requirement, but this should not constrain what the protoco=
l can do under different policies or deployment scenarios.<br>
<br><br>Morgaine.<br><br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br><br><div class=3D"gmail_quote">On Mon, Nov 2, 2009 at 11:49 AM=
, Carlo Wood <span dir=3D"ltr">&lt;<a href=3D"mailto:carlo@alinoe.com">carl=
o@alinoe.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Using common sens=
e, I&#39;d say:<br>
<br>
* If you try to rez an object, policy comes in to determine if that is allo=
wed.<br>
<br>
* Once an object is rezzed, EVERYONE that is in the region (that is allowed=
 to<br>
 =A0enter the region thus) can SEE that object (and interact with it).<br>
<br>
I realize that it is *possible* for the region to implement a policy<br>
where it selectively shows data to some people and not to others, but<br>
I don&#39;t think we have to officially support every possible way to screw=
<br>
up shared experience in VWRAP, just because it would be possible to do so.<=
br>
<br>
Compare with a protocol like SMPT: that dictates that if some email is<br>
received, it is required to react in one of a few given ways. There are<br>
other ways, but that would make the system stop functioning as intended,<br=
>
so that is Not The Idea.<br>
<br>
<br>
I agree with you that information needed to see a rezzed object should<br>
come from the region (simulator), so -- in principle there is no direct<br>
reason that a viewer needs to have access to every asset server whose<br>
assets are rezzed.<br>
<br>
<br>
An interesting question is now: what about assets that make up an<br>
avatar? Once in-world, attaching a new attachment, or changing clothes<br>
or shape, is just the same as rezzing of course: if the asset server<br>
allows access (by that region) than the region can buffer it and show<br>
it to everyone; otherwise attachment, or change of appearance, is disallowe=
d.<br>
However, in the case of teleportation I think we need to act more<br>
intelligent than just black or white (allow or disallow the TP):<br>
I&#39;m in favour of allowing the TP independent of assets being used at<br=
>
that moment, but instead detach assets and/or Ruth the avatar if<br>
need be (at least, give the user that option).<br>
<div class=3D"im"><br>
On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:<br>
&gt; Be careful about blurring the use of &quot;asset services&quot; betwee=
n &quot;stuff in<br>
&gt; regions&quot; and &quot;stuff I have&quot;. I think there is a big int=
ersection - and may have<br>
&gt; the same characteristics and/or protocols, but I also think they are a=
re<br>
&gt; distinct. I would guess that there will be asset services associated w=
ith both<br>
&gt; agents and regions - off the top of my head:<br>
&gt;<br>
&gt; Uses of an agent-associated &quot;asset&quot; service:<br>
&gt; * content to client app (inspect your inventory)<br>
&gt; * content from client app (upload/import to inventory)<br>
&gt; * content to region (rez something)<br>
&gt; * content from region (buy/take something)<br>
&gt; * content to agent (give something)<br>
&gt; * content from agent (receive something)<br>
&gt;<br>
&gt; Uses of an region-associated &quot;asset&quot; service:<br>
&gt; * content to client app (see the world)<br>
&gt; * content from client app (upload/import to region)<br>
&gt; * content to region (during teleport/region crossing)<br>
&gt; * content from region (during teleport/region crossing)<br>
&gt; * content to agent (buy/take something)<br>
&gt; * content from agent (rez something)<br>
&gt;<br>
&gt; I&#39;m using &quot;asset&quot; in quotes since that term may be overl=
oaded. &quot;Content&quot; might<br>
&gt; be a better term.<br>
<br>
</div>--<br>
<div><div></div><div class=3D"h5">Carlo Wood &lt;<a href=3D"mailto:carlo@al=
inoe.com">carlo@alinoe.com</a>&gt;<br>
_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
</div></div></blockquote></div><br>

--0016e6d9a3290b8baf047763dde5--

From han.sontse.sl@gmail.com  Mon Nov  2 13:13:13 2009
Return-Path: <han.sontse.sl@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E94CC3A691B for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 13:13:13 -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 Ug3Zl8mFxEnH for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 13:13:12 -0800 (PST)
Received: from mail-pz0-f204.google.com (mail-pz0-f204.google.com [209.85.222.204]) by core3.amsl.com (Postfix) with ESMTP id C19EB3A6808 for <ogpx@ietf.org>; Mon,  2 Nov 2009 13:13:11 -0800 (PST)
Received: by pzk42 with SMTP id 42so4132683pzk.31 for <ogpx@ietf.org>; Mon, 02 Nov 2009 13:13:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:mime-version:subject:date:references :x-mailer; bh=s6PI4R7fAWP+STYTUoKcDpLMpeiILlaOMIBEYtFclyI=; b=LHn7xhmP/e527dARM9a2s2DtVTDPBzG0yGpZPGLFWL6zRbj9SPtNwI7u07iTdBvoeU lpJyu6wNbWaqG9G6dZtDp7IsdjaETGC/6iuhsbkQNh7UOBX4QrNu4/B8TvnFuxL0Ukt6 9Q9E5H4pWI9NVXwqd77tpiUOxcpBKOU/GVzNk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type:mime-version:subject :date:references:x-mailer; b=b2kSm748gBCVktNxfIpfbibCPqe6KLbKiq72z3wVHwNunhgbHFLccezzoAbaEd9t+/ U0jhwnH6P2RbpBJv3++RF7DdT1wLT5P3BIoYYYLRFHLNbvggAMF1Bc1luDf+xJbSv4qy SxUzIxq+MjNuX6lj9tVCDI7eZhrKZv/1CxWNg=
Received: by 10.114.44.10 with SMTP id r10mr9554374war.77.1257196407674; Mon, 02 Nov 2009 13:13:27 -0800 (PST)
Received: from ?192.168.1.57? ([98.125.239.57]) by mx.google.com with ESMTPS id 22sm404189pxi.14.2009.11.02.13.13.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 02 Nov 2009 13:13:27 -0800 (PST)
Message-Id: <640E4EB8-6EFB-4FD7-A5F0-F580CE06A8C1@gmail.com>
From: Han Sontse <han.sontse.sl@gmail.com>
To: ogpx@ietf.org
In-Reply-To: <e0b04bba0911020605k2e097f3fx58a91f8d9c69cdee@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1--283668424
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 2 Nov 2009 13:13:25 -0800
References: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com> <3a880e2c0910160116g7a7e488fpe03b10d9b534aa35@mail.gmail.com> <9b8a8de40910160635j268ef9c9mae55781221c94d7e@mail.gmail.com> <20091029134353.GB2298@alinoe.com> <e0b04bba0910300029jd385ea7s1ab66a6d67b084d4@mail.gmail.com> <f72742de0910301023i266832d3ta7c96cc13985e959@mail.gmail.com> <20091102114929.GA19073@alinoe.com> <e0b04bba0911020605k2e097f3fx58a91f8d9c69cdee@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Subject: Re: [ogpx] Tourist use case
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2009 21:14:13 -0000

--Apple-Mail-1--283668424
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

On Nov 2, 2009, at 6:05 AM, Morgaine wrote:
 > Decoupling the simulation from the storage is one of the most  
important things that this protocol will achieve if we
 > get it right.  We probably do need to ensure that SL's existing  
"proxy everything" model can be expressed through
 > appropriate policy or deployment choices as it is likely to be a  
requirement, but this should not constrain what the
 > protocol can do under different policies or deployment scenarios.

Removing the 'proxy everything'  from the sim seems to me to be fairly  
straight forward.  A connected client might get a list of region-local  
UUIDs for content that has presence in the Sim.  As the client works  
through the process of building a local representation, some or all of  
the UUIDs might actually 'redirect' to another service that provides  
the representation.  The Sim in effect is saying, "I don't have a  
representation for this object, but you can get the properties @ <url>? 
=<Sim_id>,<UUID>  or some such...  A client requesting this asset  
representation is also communicating where it got redirected from, so  
that the correct instance of that asset is accessed.

At the same time the Sim might have a partial representation of this  
object!  This partial representation includes only the information the  
Sim needs to manage the interaction of this object with the rest of  
the Sim.   This management information is likely to be a very  
restricted set of properties, and may not be static in nature.  It  
could however provide some public information so that clients with  
policy or capability restrictions in requesting the full  
representation might still acquire a 'default' representation as a  
placeholder.

In thinking about this it occurs to me the asset might be a dynamic  
service that has NO static representation, such that the Sim sees (for  
example) the service as a dynamic, shifting, set of bounding volumes.  
An untrusted user/client might see a low resolution stream of textured  
meshes. A more trusted user/client might get a complete .obj model and  
be receiving only skeletal updates from the asset service.

Abstracting a bit further, an asset is a service in and of itself.   
The Sim provides a url to the relevant instance of the service.  The  
client, asset service, and Sim negotiate a cooperative context/ 
representation for the service.  This is true even if the service is  
local to the Sim.

If the asset service wants to require some kind of authentication for  
privileged representations of the service they are welcome to do so.   
The Sim operator may already have some baseline relationship with the  
asset-service.  Each user/client might have a different relationship  
with that service.

In this context a tourist might see minimal representations from asset  
services that have restrictive access policies and more complete  
representations from services that have less restrictive policies.     
What a tourist "sees" through the client has more to do with their  
trust relationship with the asset service community than with the Sim  
community.   Though I see no reason that such trust relationships be  
mutually exclusive, nor even required.

Han


On Nov 2, 2009, at 6:05 AM, Morgaine wrote:

> On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
>
> I agree with you that information needed to see a rezzed object should
> come from the region (simulator), so -- in principle there is no  
> direct
> reason that a viewer needs to have access to every asset server whose
> assets are rezzed.
>
>
> The region certainly needs to indicate which objects are rezzed in  
> it --- it is the single authority that holds that information ---  
> there is no other place where this information could come from in  
> the current model.
>
> However, that does not mean that it has to actually hold the data,  
> but merely to indicate which it is so that it can be fetched.   
> Indeed, requiring the region to hold the data or to proxy it would  
> be really bad for protocol scalability.  In any case, that's a  
> policy choice --- our mechanism needs to be more flexible than this  
> in its service endpoint choices, and not require the data to come  
> from the region.  It is highly likely that many implementations will  
> aim for higher scalability than is possible to achieve by routing  
> assets through a sim.  Indeed, that's a primary reason for using  
> caps for accessing decoupled services in a REST-like manner.
>
> Decoupling the simulation from the storage is one of the most  
> important things that this protocol will achieve if we get it  
> right.  We probably do need to ensure that SL's existing "proxy  
> everything" model can be expressed through appropriate policy or  
> deployment choices as it is likely to be a requirement, but this  
> should not constrain what the protocol can do under different  
> policies or deployment scenarios.
>
>
> Morgaine.
>
>
>
>
>
>
> ======================================
>
> On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
> Using common sense, I'd say:
>
> * If you try to rez an object, policy comes in to determine if that  
> is allowed.
>
> * Once an object is rezzed, EVERYONE that is in the region (that is  
> allowed to
>  enter the region thus) can SEE that object (and interact with it).
>
> I realize that it is *possible* for the region to implement a policy
> where it selectively shows data to some people and not to others, but
> I don't think we have to officially support every possible way to  
> screw
> up shared experience in VWRAP, just because it would be possible to  
> do so.
>
> Compare with a protocol like SMPT: that dictates that if some email is
> received, it is required to react in one of a few given ways. There  
> are
> other ways, but that would make the system stop functioning as  
> intended,
> so that is Not The Idea.
>
>
> I agree with you that information needed to see a rezzed object should
> come from the region (simulator), so -- in principle there is no  
> direct
> reason that a viewer needs to have access to every asset server whose
> assets are rezzed.
>
>
> An interesting question is now: what about assets that make up an
> avatar? Once in-world, attaching a new attachment, or changing clothes
> or shape, is just the same as rezzing of course: if the asset server
> allows access (by that region) than the region can buffer it and show
> it to everyone; otherwise attachment, or change of appearance, is  
> disallowed.
> However, in the case of teleportation I think we need to act more
> intelligent than just black or white (allow or disallow the TP):
> I'm in favour of allowing the TP independent of assets being used at
> that moment, but instead detach assets and/or Ruth the avatar if
> need be (at least, give the user that option).
>
> On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:
> > Be careful about blurring the use of "asset services" between  
> "stuff in
> > regions" and "stuff I have". I think there is a big intersection -  
> and may have
> > the same characteristics and/or protocols, but I also think they  
> are are
> > distinct. I would guess that there will be asset services  
> associated with both
> > agents and regions - off the top of my head:
> >
> > Uses of an agent-associated "asset" service:
> > * content to client app (inspect your inventory)
> > * content from client app (upload/import to inventory)
> > * content to region (rez something)
> > * content from region (buy/take something)
> > * content to agent (give something)
> > * content from agent (receive something)
> >
> > Uses of an region-associated "asset" service:
> > * content to client app (see the world)
> > * content from client app (upload/import to region)
> > * content to region (during teleport/region crossing)
> > * content from region (during teleport/region crossing)
> > * content to agent (buy/take something)
> > * content from agent (rez something)
> >
> > I'm using "asset" in quotes since that term may be overloaded.  
> "Content" might
> > be a better term.
>
> --
> Carlo Wood <carlo@alinoe.com>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx


--Apple-Mail-1--283668424
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;"><font class=3D"Apple-style-span" =
color=3D"#144FAE"><span class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 0); ">On Nov 2, 2009, at 6:05 AM, Morgaine =
wrote:</span></font></blockquote><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;">&gt; Decoupling the simulation from the storage is =
one of the most important things that this protocol will achieve if =
we&nbsp;</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin: 0 0 0 40px; border: none; padding: 0px;">&gt; get it =
right.&nbsp; We probably do need to ensure that SL's existing "proxy =
everything" model can be expressed through&nbsp;</blockquote><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;">&gt; appropriate policy or deployment choices as it =
is likely to be a requirement, but this should not constrain what =
the&nbsp;</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin: 0 0 0 40px; border: none; padding: 0px;">&gt; protocol =
can do under different policies or deployment =
scenarios.</blockquote><div><br></div><div>Removing the 'proxy =
everything' &nbsp;from the sim seems to me to be fairly straight =
forward. &nbsp;A connected client might get a list of region-local UUIDs =
for content that has presence in the Sim. &nbsp;As the client works =
through the process of building a local representation, some or all of =
the UUIDs might actually 'redirect' to another service that provides the =
representation. &nbsp;The Sim in effect is saying, "I don't have a =
representation for this object, but you can get the properties @ =
&lt;url&gt;?=3D&lt;Sim_id&gt;,&lt;UUID&gt; &nbsp;or some such... &nbsp;A =
client requesting this asset representation is also communicating where =
it got redirected from, so that the correct instance of that asset is =
accessed. &nbsp;</div><div><br></div><div>At the same time the Sim might =
have a partial representation of this object! &nbsp;This partial =
representation includes only the information the Sim needs to manage the =
interaction of this object with the rest of the Sim. &nbsp; This =
management information is likely to be a very restricted set of =
properties, and may not be static in nature. &nbsp;It could however =
provide some public information so that clients with policy or =
capability restrictions in requesting the full representation might =
still acquire a 'default' representation as a =
placeholder.&nbsp;</div><div><br></div><div>In thinking about this it =
occurs to me the asset might be a dynamic service that has NO static =
representation, such that the Sim sees (for example) the service as a =
dynamic, shifting, set of bounding volumes. An untrusted user/client =
might see a low resolution stream of textured meshes. A more trusted =
user/client might get a complete .obj model and be receiving only =
skeletal updates from the asset =
service.</div><div><br></div><div>Abstracting a bit further, an asset is =
a service in and of itself. &nbsp;The Sim provides a url to the relevant =
instance of the service. &nbsp;The client, asset service, and Sim =
negotiate a cooperative context/representation for the service. =
&nbsp;This is true even if the service is local to the =
Sim.</div><div><br></div><div>If the asset service wants to require some =
kind of authentication for privileged representations of the service =
they are welcome to do so. &nbsp;The Sim operator may already have some =
baseline relationship with the asset-service. &nbsp;Each user/client =
might have a different relationship with that =
service.</div><div><br></div><div>In this context a tourist might see =
minimal representations from asset services that have restrictive access =
policies and more complete representations from services that have less =
restrictive policies. &nbsp; &nbsp;What a tourist "sees" through the =
client has more to do with their trust relationship with the asset =
service community than with the Sim community. &nbsp; Though I see no =
reason that such trust relationships be mutually exclusive, nor even =
required. =
&nbsp;</div><div><br></div><div>Han</div><div><br></div><br><div><div>On =
Nov 2, 2009, at 6:05 AM, Morgaine wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">On Mon, =
Nov 2, 2009 at 11:49 AM, Carlo Wood <span dir=3D"ltr">&lt;<a =
href=3D"mailto:carlo@alinoe.com">carlo@alinoe.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px =
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: =
1ex;"> <br><div style=3D"margin-left: 40px;"> I agree with you that =
information needed to see a rezzed object should<br> come from the =
region (simulator), so -- in principle there is no direct<br> reason =
that a viewer needs to have access to every asset server whose<br> =
assets are rezzed.</div></blockquote><br><br>The region certainly needs =
to indicate <i><b>which</b></i> objects are rezzed in it --- it is the =
single authority that holds that information --- there is no other place =
where this information could come from in the current model.<br> =
<br>However, that does not mean that it has to actually =
<b><i>hold</i></b> the data, but merely to indicate <b><i>which it =
is</i> </b>so that it can be fetched.&nbsp; Indeed, <i>requiring</i> the =
region to hold the data or to proxy it would be really bad for protocol =
scalability.&nbsp; In any case, that's a policy choice --- our mechanism =
needs to be more flexible than this in its service endpoint choices, and =
not <i>require</i> the data to come from the region.&nbsp; It is highly =
likely that many implementations will aim for higher scalability than is =
possible to achieve by routing assets through a sim.&nbsp; Indeed, =
that's a primary reason for using caps for accessing decoupled services =
in a REST-like manner.<br> <br>Decoupling the simulation from the =
storage is one of the most important things that this protocol will =
achieve if we get it right.&nbsp; We probably do need to ensure that =
SL's existing "proxy everything" model can be expressed through =
appropriate policy or deployment choices as it is likely to be a =
requirement, but this should not constrain what the protocol can do =
under different policies or deployment scenarios.<br> =
<br><br>Morgaine.<br><br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br><br><div class=3D"gmail_quote">On Mon, Nov 2, 2009 at 11:49 =
AM, Carlo Wood <span dir=3D"ltr">&lt;<a =
href=3D"mailto:carlo@alinoe.com">carlo@alinoe.com</a>&gt;</span> =
wrote:<br> <blockquote class=3D"gmail_quote" style=3D"border-left: 1px =
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: =
1ex;">Using common sense, I'd say:<br> <br> * If you try to rez an =
object, policy comes in to determine if that is allowed.<br> <br> * Once =
an object is rezzed, EVERYONE that is in the region (that is allowed =
to<br> &nbsp;enter the region thus) can SEE that object (and interact =
with it).<br> <br> I realize that it is *possible* for the region to =
implement a policy<br> where it selectively shows data to some people =
and not to others, but<br> I don't think we have to officially support =
every possible way to screw<br> up shared experience in VWRAP, just =
because it would be possible to do so.<br> <br> Compare with a protocol =
like SMPT: that dictates that if some email is<br> received, it is =
required to react in one of a few given ways. There are<br> other ways, =
but that would make the system stop functioning as intended,<br> so that =
is Not The Idea.<br> <br> <br> I agree with you that information needed =
to see a rezzed object should<br> come from the region (simulator), so =
-- in principle there is no direct<br> reason that a viewer needs to =
have access to every asset server whose<br> assets are rezzed.<br> <br> =
<br> An interesting question is now: what about assets that make up =
an<br> avatar? Once in-world, attaching a new attachment, or changing =
clothes<br> or shape, is just the same as rezzing of course: if the =
asset server<br> allows access (by that region) than the region can =
buffer it and show<br> it to everyone; otherwise attachment, or change =
of appearance, is disallowed.<br> However, in the case of teleportation =
I think we need to act more<br> intelligent than just black or white =
(allow or disallow the TP):<br> I'm in favour of allowing the TP =
independent of assets being used at<br> that moment, but instead detach =
assets and/or Ruth the avatar if<br> need be (at least, give the user =
that option).<br> <div class=3D"im"><br> On Fri, Oct 30, 2009 at =
10:23:43AM -0700, Joshua Bell wrote:<br> &gt; Be careful about blurring =
the use of "asset services" between "stuff in<br> &gt; regions" and =
"stuff I have". I think there is a big intersection - and may have<br> =
&gt; the same characteristics and/or protocols, but I also think they =
are are<br> &gt; distinct. I would guess that there will be asset =
services associated with both<br> &gt; agents and regions - off the top =
of my head:<br> &gt;<br> &gt; Uses of an agent-associated "asset" =
service:<br> &gt; * content to client app (inspect your inventory)<br> =
&gt; * content from client app (upload/import to inventory)<br> &gt; * =
content to region (rez something)<br> &gt; * content from region =
(buy/take something)<br> &gt; * content to agent (give something)<br> =
&gt; * content from agent (receive something)<br> &gt;<br> &gt; Uses of =
an region-associated "asset" service:<br> &gt; * content to client app =
(see the world)<br> &gt; * content from client app (upload/import to =
region)<br> &gt; * content to region (during teleport/region =
crossing)<br> &gt; * content from region (during teleport/region =
crossing)<br> &gt; * content to agent (buy/take something)<br> &gt; * =
content from agent (rez something)<br> &gt;<br> &gt; I'm using "asset" =
in quotes since that term may be overloaded. "Content" might<br> &gt; be =
a better term.<br> <br> </div>--<br> <div><div></div><div =
class=3D"h5">Carlo Wood &lt;<a =
href=3D"mailto:carlo@alinoe.com">carlo@alinoe.com</a>&gt;<br> =
_______________________________________________<br> ogpx mailing =
list<br> <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br> <a =
href=3D"https://www.ietf.org/mailman/listinfo/ogpx" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/ogpx</a><br> =
</div></div></blockquote></div><br> =
_______________________________________________<br>ogpx mailing =
list<br><a =
href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/ogpx<br></blockquote></div><br></body></html>=

--Apple-Mail-1--283668424--

From han.sontse.sl@gmail.com  Mon Nov  2 13:21:14 2009
Return-Path: <han.sontse.sl@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78EB73A692D for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 13:21:14 -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=[AWL=-0.000, 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 TrheXCwFdmT9 for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 13:21:12 -0800 (PST)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id 79B563A691B for <ogpx@ietf.org>; Mon,  2 Nov 2009 13:21:12 -0800 (PST)
Received: by pwi4 with SMTP id 4so2221657pwi.29 for <ogpx@ietf.org>; Mon, 02 Nov 2009 13:21:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:mime-version:subject:date:references:x-mailer; bh=e8DdkrIn5TBAMmR1Wp1L5zThn6gN/k98GOgMJgcQgM4=; b=cBR7QtUh1IK36ZSP9rz0S4N1l3PhcwjCzyzjX+LuKctP1RwXu8Ktpnq0uHKCD52lER qI4Fa/Wmj7eTW5x9YOpx8ynuZ+gc5ccoGClKHjal0wfnzZoMgwcJYuoinndGn1CnuF+i e8UWX2dj2lSCl2ywXE7Q1VNlagI4U7wneo8KA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:mime-version:subject:date :references:x-mailer; b=G/xQ3wT2nKTCFZN5Q5CGrFirxcyDDkF55fwsCsSyog+HZO9Ocb16DrDPP7aqbae+Ra Ip0VVJ9QG69uXsLMJB87emyFBABNot78226kLclLzvnsNow0P2WHGEePyd56PCSSMe5l vrX3UcAPL6AMJbZivL7HlG3wQ2hv4iRE6YTf8=
Received: by 10.115.67.10 with SMTP id u10mr9544493wak.203.1257196890163; Mon, 02 Nov 2009 13:21:30 -0800 (PST)
Received: from ?192.168.1.57? ([98.125.239.57]) by mx.google.com with ESMTPS id 22sm366959pxi.6.2009.11.02.13.21.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 02 Nov 2009 13:21:29 -0800 (PST)
Message-Id: <1CAAEFF5-E0B8-4A54-A4F6-6F85A845A7AD@gmail.com>
From: Han Sontse <han.sontse.sl@gmail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=Apple-Mail-2--283185784
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 2 Nov 2009 13:21:28 -0800
References: <640E4EB8-6EFB-4FD7-A5F0-F580CE06A8C1@gmail.com>
X-Mailer: Apple Mail (2.936)
Subject: Re: [ogpx] Tourist use case
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2009 21:21:14 -0000

--Apple-Mail-2--283185784
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit



Begin forwarded message:

> From: Han Sontse <Han.Sontse@gmail.com>
> Date: November 2, 2009 1:13:25 PM PST
> To: ogpx@ietf.org
> Subject: Re: [ogpx] Tourist use case
>
> On Nov 2, 2009, at 6:05 AM, Morgaine wrote:
> > Decoupling the simulation from the storage is one of the most  
> important things that this protocol will achieve if we
> > get it right.  We probably do need to ensure that SL's existing  
> "proxy everything" model can be expressed through
> > appropriate policy or deployment choices as it is likely to be a  
> requirement, but this should not constrain what the
> > protocol can do under different policies or deployment scenarios.
>
> Removing the 'proxy everything'  from the sim seems to me to be  
> fairly straight forward.  A connected client might get a list of  
> region-local UUIDs for content that has presence in the Sim.  As the  
> client works through the process of building a local representation,  
> some or all of the UUIDs might actually 'redirect' to another  
> service that provides the representation.  The Sim in effect is  
> saying, "I don't have a representation for this object, but you can  
> get the properties @ <url>?=<Sim_id>,<UUID>  or some such...  A  
> client requesting this asset representation is also communicating  
> where it got redirected from, so that the correct instance of that  
> asset is accessed.
>
> At the same time the Sim might have a partial representation of this  
> object!  This partial representation includes only the information  
> the Sim needs to manage the interaction of this object with the rest  
> of the Sim.   This management information is likely to be a very  
> restricted set of properties, and may not be static in nature.  It  
> could however provide some public information so that clients with  
> policy or capability restrictions in requesting the full  
> representation might still acquire a 'default' representation as a  
> placeholder.
>
> In thinking about this it occurs to me the asset might be a dynamic  
> service that has NO static representation, such that the Sim sees  
> (for example) the service as a dynamic, shifting, set of bounding  
> volumes. An untrusted user/client might see a low resolution stream  
> of textured meshes. A more trusted user/client might get a  
> complete .obj model and be receiving only skeletal updates from the  
> asset service.
>
> Abstracting a bit further, an asset is a service in and of itself.   
> The Sim provides a url to the relevant instance of the service.  The  
> client, asset service, and Sim negotiate a cooperative context/ 
> representation for the service.  This is true even if the service is  
> local to the Sim.
>
> If the asset service wants to require some kind of authentication  
> for privileged representations of the service they are welcome to do  
> so.  The Sim operator may already have some baseline relationship  
> with the asset-service.  Each user/client might have a different  
> relationship with that service.
>
> In this context a tourist might see minimal representations from  
> asset services that have restrictive access policies and more  
> complete representations from services that have less restrictive  
> policies.    What a tourist "sees" through the client has more to do  
> with their trust relationship with the asset service community than  
> with the Sim community.   Though I see no reason that such trust  
> relationships be mutually exclusive, nor even required.
>
> Han
>
>
> On Nov 2, 2009, at 6:05 AM, Morgaine wrote:
>
>> On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
>>
>> I agree with you that information needed to see a rezzed object  
>> should
>> come from the region (simulator), so -- in principle there is no  
>> direct
>> reason that a viewer needs to have access to every asset server whose
>> assets are rezzed.
>>
>>
>> The region certainly needs to indicate which objects are rezzed in  
>> it --- it is the single authority that holds that information ---  
>> there is no other place where this information could come from in  
>> the current model.
>>
>> However, that does not mean that it has to actually hold the data,  
>> but merely to indicate which it is so that it can be fetched.   
>> Indeed, requiring the region to hold the data or to proxy it would  
>> be really bad for protocol scalability.  In any case, that's a  
>> policy choice --- our mechanism needs to be more flexible than this  
>> in its service endpoint choices, and not require the data to come  
>> from the region.  It is highly likely that many implementations  
>> will aim for higher scalability than is possible to achieve by  
>> routing assets through a sim.  Indeed, that's a primary reason for  
>> using caps for accessing decoupled services in a REST-like manner.
>>
>> Decoupling the simulation from the storage is one of the most  
>> important things that this protocol will achieve if we get it  
>> right.  We probably do need to ensure that SL's existing "proxy  
>> everything" model can be expressed through appropriate policy or  
>> deployment choices as it is likely to be a requirement, but this  
>> should not constrain what the protocol can do under different  
>> policies or deployment scenarios.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>>
>> ======================================
>>
>> On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
>> Using common sense, I'd say:
>>
>> * If you try to rez an object, policy comes in to determine if that  
>> is allowed.
>>
>> * Once an object is rezzed, EVERYONE that is in the region (that is  
>> allowed to
>>  enter the region thus) can SEE that object (and interact with it).
>>
>> I realize that it is *possible* for the region to implement a policy
>> where it selectively shows data to some people and not to others, but
>> I don't think we have to officially support every possible way to  
>> screw
>> up shared experience in VWRAP, just because it would be possible to  
>> do so.
>>
>> Compare with a protocol like SMPT: that dictates that if some email  
>> is
>> received, it is required to react in one of a few given ways. There  
>> are
>> other ways, but that would make the system stop functioning as  
>> intended,
>> so that is Not The Idea.
>>
>>
>> I agree with you that information needed to see a rezzed object  
>> should
>> come from the region (simulator), so -- in principle there is no  
>> direct
>> reason that a viewer needs to have access to every asset server whose
>> assets are rezzed.
>>
>>
>> An interesting question is now: what about assets that make up an
>> avatar? Once in-world, attaching a new attachment, or changing  
>> clothes
>> or shape, is just the same as rezzing of course: if the asset server
>> allows access (by that region) than the region can buffer it and show
>> it to everyone; otherwise attachment, or change of appearance, is  
>> disallowed.
>> However, in the case of teleportation I think we need to act more
>> intelligent than just black or white (allow or disallow the TP):
>> I'm in favour of allowing the TP independent of assets being used at
>> that moment, but instead detach assets and/or Ruth the avatar if
>> need be (at least, give the user that option).
>>
>> On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:
>> > Be careful about blurring the use of "asset services" between  
>> "stuff in
>> > regions" and "stuff I have". I think there is a big intersection  
>> - and may have
>> > the same characteristics and/or protocols, but I also think they  
>> are are
>> > distinct. I would guess that there will be asset services  
>> associated with both
>> > agents and regions - off the top of my head:
>> >
>> > Uses of an agent-associated "asset" service:
>> > * content to client app (inspect your inventory)
>> > * content from client app (upload/import to inventory)
>> > * content to region (rez something)
>> > * content from region (buy/take something)
>> > * content to agent (give something)
>> > * content from agent (receive something)
>> >
>> > Uses of an region-associated "asset" service:
>> > * content to client app (see the world)
>> > * content from client app (upload/import to region)
>> > * content to region (during teleport/region crossing)
>> > * content from region (during teleport/region crossing)
>> > * content to agent (buy/take something)
>> > * content from agent (rez something)
>> >
>> > I'm using "asset" in quotes since that term may be overloaded.  
>> "Content" might
>> > be a better term.
>>
>> --
>> Carlo Wood <carlo@alinoe.com>
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>>
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>


--Apple-Mail-2--283185784
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><br><div>Begin =
forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><b>From: =
</b></font><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">Han Sontse &lt;<a =
href=3D"mailto:Han.Sontse@gmail.com">Han.Sontse@gmail.com</a>&gt;</font></=
div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" =
color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><b>Date: </b></font><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">November 2, 2009 1:13:25 PM =
PST</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"3" color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><b>To: </b></font><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica"><a =
href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><b>Subject: =
</b></font><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica"><b>Re: [ogpx] Tourist use case</b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> </div><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;"><font class=3D"Apple-style-span" =
color=3D"#144FAE"><span class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 0); ">On Nov 2, 2009, at 6:05 AM, Morgaine =
wrote:</span></font></blockquote><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;">&gt; Decoupling the simulation from the storage is =
one of the most important things that this protocol will achieve if =
we&nbsp;</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin: 0 0 0 40px; border: none; padding: 0px;">&gt; get it =
right.&nbsp; We probably do need to ensure that SL's existing "proxy =
everything" model can be expressed through&nbsp;</blockquote><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;">&gt; appropriate policy or deployment choices as it =
is likely to be a requirement, but this should not constrain what =
the&nbsp;</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin: 0 0 0 40px; border: none; padding: 0px;">&gt; protocol =
can do under different policies or deployment =
scenarios.</blockquote><div><br></div><div>Removing the 'proxy =
everything' &nbsp;from the sim seems to me to be fairly straight =
forward. &nbsp;A connected client might get a list of region-local UUIDs =
for content that has presence in the Sim. &nbsp;As the client works =
through the process of building a local representation, some or all of =
the UUIDs might actually 'redirect' to another service that provides the =
representation. &nbsp;The Sim in effect is saying, "I don't have a =
representation for this object, but you can get the properties @ =
&lt;url&gt;?=3D&lt;Sim_id&gt;,&lt;UUID&gt; &nbsp;or some such... &nbsp;A =
client requesting this asset representation is also communicating where =
it got redirected from, so that the correct instance of that asset is =
accessed. &nbsp;</div><div><br></div><div>At the same time the Sim might =
have a partial representation of this object! &nbsp;This partial =
representation includes only the information the Sim needs to manage the =
interaction of this object with the rest of the Sim. &nbsp; This =
management information is likely to be a very restricted set of =
properties, and may not be static in nature. &nbsp;It could however =
provide some public information so that clients with policy or =
capability restrictions in requesting the full representation might =
still acquire a 'default' representation as a =
placeholder.&nbsp;</div><div><br></div><div>In thinking about this it =
occurs to me the asset might be a dynamic service that has NO static =
representation, such that the Sim sees (for example) the service as a =
dynamic, shifting, set of bounding volumes. An untrusted user/client =
might see a low resolution stream of textured meshes. A more trusted =
user/client might get a complete .obj model and be receiving only =
skeletal updates from the asset =
service.</div><div><br></div><div>Abstracting a bit further, an asset is =
a service in and of itself. &nbsp;The Sim provides a url to the relevant =
instance of the service. &nbsp;The client, asset service, and Sim =
negotiate a cooperative context/representation for the service. =
&nbsp;This is true even if the service is local to the =
Sim.</div><div><br></div><div>If the asset service wants to require some =
kind of authentication for privileged representations of the service =
they are welcome to do so. &nbsp;The Sim operator may already have some =
baseline relationship with the asset-service. &nbsp;Each user/client =
might have a different relationship with that =
service.</div><div><br></div><div>In this context a tourist might see =
minimal representations from asset services that have restrictive access =
policies and more complete representations from services that have less =
restrictive policies. &nbsp; &nbsp;What a tourist "sees" through the =
client has more to do with their trust relationship with the asset =
service community than with the Sim community. &nbsp; Though I see no =
reason that such trust relationships be mutually exclusive, nor even =
required. =
&nbsp;</div><div><br></div><div>Han</div><div><br></div><br><div><div>On =
Nov 2, 2009, at 6:05 AM, Morgaine wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">On Mon, =
Nov 2, 2009 at 11:49 AM, Carlo Wood <span dir=3D"ltr">&lt;<a =
href=3D"mailto:carlo@alinoe.com">carlo@alinoe.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px =
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: =
1ex;"> <br><div style=3D"margin-left: 40px;"> I agree with you that =
information needed to see a rezzed object should<br> come from the =
region (simulator), so -- in principle there is no direct<br> reason =
that a viewer needs to have access to every asset server whose<br> =
assets are rezzed.</div></blockquote><br><br>The region certainly needs =
to indicate <i><b>which</b></i> objects are rezzed in it --- it is the =
single authority that holds that information --- there is no other place =
where this information could come from in the current model.<br> =
<br>However, that does not mean that it has to actually =
<b><i>hold</i></b> the data, but merely to indicate <b><i>which it =
is</i> </b>so that it can be fetched.&nbsp; Indeed, <i>requiring</i> the =
region to hold the data or to proxy it would be really bad for protocol =
scalability.&nbsp; In any case, that's a policy choice --- our mechanism =
needs to be more flexible than this in its service endpoint choices, and =
not <i>require</i> the data to come from the region.&nbsp; It is highly =
likely that many implementations will aim for higher scalability than is =
possible to achieve by routing assets through a sim.&nbsp; Indeed, =
that's a primary reason for using caps for accessing decoupled services =
in a REST-like manner.<br> <br>Decoupling the simulation from the =
storage is one of the most important things that this protocol will =
achieve if we get it right.&nbsp; We probably do need to ensure that =
SL's existing "proxy everything" model can be expressed through =
appropriate policy or deployment choices as it is likely to be a =
requirement, but this should not constrain what the protocol can do =
under different policies or deployment scenarios.<br> =
<br><br>Morgaine.<br><br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br><br><div class=3D"gmail_quote">On Mon, Nov 2, 2009 at 11:49 =
AM, Carlo Wood <span dir=3D"ltr">&lt;<a =
href=3D"mailto:carlo@alinoe.com">carlo@alinoe.com</a>&gt;</span> =
wrote:<br> <blockquote class=3D"gmail_quote" style=3D"border-left: 1px =
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: =
1ex;">Using common sense, I'd say:<br> <br> * If you try to rez an =
object, policy comes in to determine if that is allowed.<br> <br> * Once =
an object is rezzed, EVERYONE that is in the region (that is allowed =
to<br> &nbsp;enter the region thus) can SEE that object (and interact =
with it).<br> <br> I realize that it is *possible* for the region to =
implement a policy<br> where it selectively shows data to some people =
and not to others, but<br> I don't think we have to officially support =
every possible way to screw<br> up shared experience in VWRAP, just =
because it would be possible to do so.<br> <br> Compare with a protocol =
like SMPT: that dictates that if some email is<br> received, it is =
required to react in one of a few given ways. There are<br> other ways, =
but that would make the system stop functioning as intended,<br> so that =
is Not The Idea.<br> <br> <br> I agree with you that information needed =
to see a rezzed object should<br> come from the region (simulator), so =
-- in principle there is no direct<br> reason that a viewer needs to =
have access to every asset server whose<br> assets are rezzed.<br> <br> =
<br> An interesting question is now: what about assets that make up =
an<br> avatar? Once in-world, attaching a new attachment, or changing =
clothes<br> or shape, is just the same as rezzing of course: if the =
asset server<br> allows access (by that region) than the region can =
buffer it and show<br> it to everyone; otherwise attachment, or change =
of appearance, is disallowed.<br> However, in the case of teleportation =
I think we need to act more<br> intelligent than just black or white =
(allow or disallow the TP):<br> I'm in favour of allowing the TP =
independent of assets being used at<br> that moment, but instead detach =
assets and/or Ruth the avatar if<br> need be (at least, give the user =
that option).<br> <div class=3D"im"><br> On Fri, Oct 30, 2009 at =
10:23:43AM -0700, Joshua Bell wrote:<br> &gt; Be careful about blurring =
the use of "asset services" between "stuff in<br> &gt; regions" and =
"stuff I have". I think there is a big intersection - and may have<br> =
&gt; the same characteristics and/or protocols, but I also think they =
are are<br> &gt; distinct. I would guess that there will be asset =
services associated with both<br> &gt; agents and regions - off the top =
of my head:<br> &gt;<br> &gt; Uses of an agent-associated "asset" =
service:<br> &gt; * content to client app (inspect your inventory)<br> =
&gt; * content from client app (upload/import to inventory)<br> &gt; * =
content to region (rez something)<br> &gt; * content from region =
(buy/take something)<br> &gt; * content to agent (give something)<br> =
&gt; * content from agent (receive something)<br> &gt;<br> &gt; Uses of =
an region-associated "asset" service:<br> &gt; * content to client app =
(see the world)<br> &gt; * content from client app (upload/import to =
region)<br> &gt; * content to region (during teleport/region =
crossing)<br> &gt; * content from region (during teleport/region =
crossing)<br> &gt; * content to agent (buy/take something)<br> &gt; * =
content from agent (rez something)<br> &gt;<br> &gt; I'm using "asset" =
in quotes since that term may be overloaded. "Content" might<br> &gt; be =
a better term.<br> <br> </div>--<br> <div><div></div><div =
class=3D"h5">Carlo Wood &lt;<a =
href=3D"mailto:carlo@alinoe.com">carlo@alinoe.com</a>&gt;<br> =
_______________________________________________<br> ogpx mailing =
list<br> <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br> <a =
href=3D"https://www.ietf.org/mailman/listinfo/ogpx" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/ogpx</a><br> =
</div></div></blockquote></div><br> =
_______________________________________________<br>ogpx mailing =
list<br><a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/ogpx">https://www.ietf.org/m=
ailman/listinfo/ogpx</a><br></blockquote></div><br></div></blockquote></di=
v><br></body></html>=

--Apple-Mail-2--283185784--

From carlo@alinoe.com  Mon Nov  2 15:31:02 2009
Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4347A3A6933 for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 15:31:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.391
X-Spam-Level: 
X-Spam-Status: No, score=-0.391 tagged_above=-999 required=5 tests=[AWL=1.039,  BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 bhZ12IZ+2ecQ for <ogpx@core3.amsl.com>; Mon,  2 Nov 2009 15:31:01 -0800 (PST)
Received: from viefep16-int.chello.at (viefep16-int.chello.at [62.179.121.36]) by core3.amsl.com (Postfix) with ESMTP id CF6B03A686B for <ogpx@ietf.org>; Mon,  2 Nov 2009 15:31:00 -0800 (PST)
Received: from edge03.upc.biz ([192.168.13.238]) by viefep16-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20091102233120.QEAT27636.viefep16-int.chello.at@edge03.upc.biz>; Tue, 3 Nov 2009 00:31:20 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge03.upc.biz with edge id 0PXJ1d02F0FlQed03PXK0S; Tue, 03 Nov 2009 00:31:20 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1N56MC-00031j-62; Tue, 03 Nov 2009 00:30:40 +0100
Date: Tue, 3 Nov 2009 00:30:40 +0100
From: Carlo Wood <carlo@alinoe.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Message-ID: <20091102233040.GA11532@alinoe.com>
References: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com> <3a880e2c0910160116g7a7e488fpe03b10d9b534aa35@mail.gmail.com> <9b8a8de40910160635j268ef9c9mae55781221c94d7e@mail.gmail.com> <20091029134353.GB2298@alinoe.com> <e0b04bba0910300029jd385ea7s1ab66a6d67b084d4@mail.gmail.com> <f72742de0910301023i266832d3ta7c96cc13985e959@mail.gmail.com> <20091102114929.GA19073@alinoe.com> <e0b04bba0911020605k2e097f3fx58a91f8d9c69cdee@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e0b04bba0911020605k2e097f3fx58a91f8d9c69cdee@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Tourist use case
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2009 23:31:02 -0000

This only advantage that I can see by this (the region only tells you
that object "xyz" is at position P with orientation O), is that then
you might be able to cache objects on the viewer.

However, THAT is only possible if 'xyz' is unique (some UUID) that changes
as soon as an object is editted in anyway, expect position and orientation
of course (rez parameters, not part of the object).

On Mon, Nov 02, 2009 at 02:05:00PM +0000, Morgaine wrote:
> On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
> 
> 
>     I agree with you that information needed to see a rezzed object should
>     come from the region (simulator), so -- in principle there is no direct
>     reason that a viewer needs to have access to every asset server whose
>     assets are rezzed.
> 
> 
> 
> The region certainly needs to indicate which objects are rezzed in it --- it is
> the single authority that holds that information --- there is no other place
> where this information could come from in the current model.
> 
> However, that does not mean that it has to actually hold the data, but merely
> to indicate which it is so that it can be fetched.  Indeed, requiring the
> region to hold the data or to proxy it would be really bad for protocol
> scalability.  In any case, that's a policy choice --- our mechanism needs to be
> more flexible than this in its service endpoint choices, and not require the
> data to come from the region.  It is highly likely that many implementations
> will aim for higher scalability than is possible to achieve by routing assets
> through a sim.  Indeed, that's a primary reason for using caps for accessing
> decoupled services in a REST-like manner.
> 
> Decoupling the simulation from the storage is one of the most important things
> that this protocol will achieve if we get it right.  We probably do need to
> ensure that SL's existing "proxy everything" model can be expressed through
> appropriate policy or deployment choices as it is likely to be a requirement,
> but this should not constrain what the protocol can do under different policies
> or deployment scenarios.
> 
> 
> Morgaine.
> 
> 
> 
> 
> 
> 
> ======================================
> 
> On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
> 
>     Using common sense, I'd say:
> 
>     * If you try to rez an object, policy comes in to determine if that is
>     allowed.
> 
>     * Once an object is rezzed, EVERYONE that is in the region (that is allowed
>     to
>      enter the region thus) can SEE that object (and interact with it).
> 
>     I realize that it is *possible* for the region to implement a policy
>     where it selectively shows data to some people and not to others, but
>     I don't think we have to officially support every possible way to screw
>     up shared experience in VWRAP, just because it would be possible to do so.
> 
>     Compare with a protocol like SMPT: that dictates that if some email is
>     received, it is required to react in one of a few given ways. There are
>     other ways, but that would make the system stop functioning as intended,
>     so that is Not The Idea.
> 
> 
>     I agree with you that information needed to see a rezzed object should
>     come from the region (simulator), so -- in principle there is no direct
>     reason that a viewer needs to have access to every asset server whose
>     assets are rezzed.
> 
> 
>     An interesting question is now: what about assets that make up an
>     avatar? Once in-world, attaching a new attachment, or changing clothes
>     or shape, is just the same as rezzing of course: if the asset server
>     allows access (by that region) than the region can buffer it and show
>     it to everyone; otherwise attachment, or change of appearance, is
>     disallowed.
>     However, in the case of teleportation I think we need to act more
>     intelligent than just black or white (allow or disallow the TP):
>     I'm in favour of allowing the TP independent of assets being used at
>     that moment, but instead detach assets and/or Ruth the avatar if
>     need be (at least, give the user that option).
> 
>     On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:
>     > Be careful about blurring the use of "asset services" between "stuff in
>     > regions" and "stuff I have". I think there is a big intersection - and
>     may have
>     > the same characteristics and/or protocols, but I also think they are are
>     > distinct. I would guess that there will be asset services associated with
>     both
>     > agents and regions - off the top of my head:
>     >
>     > Uses of an agent-associated "asset" service:
>     > * content to client app (inspect your inventory)
>     > * content from client app (upload/import to inventory)
>     > * content to region (rez something)
>     > * content from region (buy/take something)
>     > * content to agent (give something)
>     > * content from agent (receive something)
>     >
>     > Uses of an region-associated "asset" service:
>     > * content to client app (see the world)
>     > * content from client app (upload/import to region)
>     > * content to region (during teleport/region crossing)
>     > * content from region (during teleport/region crossing)
>     > * content to agent (buy/take something)
>     > * content from agent (rez something)
>     >
>     > I'm using "asset" in quotes since that term may be overloaded. "Content"
>     might
>     > be a better term.
> 
>     --
>     Carlo Wood <carlo@alinoe.com>
>     _______________________________________________
>     ogpx mailing list
>     ogpx@ietf.org
>     https://www.ietf.org/mailman/listinfo/ogpx
> 
> 

> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx


-- 
Carlo Wood <carlo@alinoe.com>

From morgaine.dinova@googlemail.com  Tue Nov  3 01:45:23 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 347993A6821 for <ogpx@core3.amsl.com>; Tue,  3 Nov 2009 01:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.591
X-Spam-Level: 
X-Spam-Status: No, score=-1.591 tagged_above=-999 required=5 tests=[AWL=0.385,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 dZvXbj4k1efP for <ogpx@core3.amsl.com>; Tue,  3 Nov 2009 01:45:21 -0800 (PST)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id F1B3A3A69AA for <ogpx@ietf.org>; Tue,  3 Nov 2009 01:45:20 -0800 (PST)
Received: by ewy3 with SMTP id 3so1768875ewy.37 for <ogpx@ietf.org>; Tue, 03 Nov 2009 01:45:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=MpRGA1mcuwJYe04I+/h5nX+tQwdKowyefmD01IEnjpk=; b=vG5UB4Hg6yA+06mvBPi5yopPJqE3XpE1fuATIr35NEteCWB1QqMv7hwlTv2t4FWGz+ LgXq4VOM8RZp6g+dS8OljTrmBkHm60ac8W/eSKS1AzNGnU/o36bSvs7wI8CMT7qRp37B 2DGPMsOlMJMNoia9fkaP7KLj41pBI5Pz4DTu0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=c2AFv/2HL4mwxpo+kDktp7W64by6kO6GpzgxwaKWuUjuX5VK++HoALc/KVSahApR1R 5tJQFBhcHxAfDHcttgRtP5y/zXy2UYshuT1hKWDAkkIbORu7hX04XjvPAzolCFwj92g8 uk4NllTC1QtlHXbmQoGbGxnwh+uwGPOOYd8Gs=
MIME-Version: 1.0
Received: by 10.216.85.5 with SMTP id t5mr6125170wee.142.1257241537061; Tue,  03 Nov 2009 01:45:37 -0800 (PST)
In-Reply-To: <20091102233040.GA11532@alinoe.com>
References: <9b8a8de40910160034j11dcb94fm401f29814aed60a8@mail.gmail.com> <3a880e2c0910160116g7a7e488fpe03b10d9b534aa35@mail.gmail.com> <9b8a8de40910160635j268ef9c9mae55781221c94d7e@mail.gmail.com> <20091029134353.GB2298@alinoe.com> <e0b04bba0910300029jd385ea7s1ab66a6d67b084d4@mail.gmail.com> <f72742de0910301023i266832d3ta7c96cc13985e959@mail.gmail.com> <20091102114929.GA19073@alinoe.com> <e0b04bba0911020605k2e097f3fx58a91f8d9c69cdee@mail.gmail.com> <20091102233040.GA11532@alinoe.com>
Date: Tue, 3 Nov 2009 09:45:36 +0000
Message-ID: <e0b04bba0911030145q10ebda9n93e6861b16940721@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d6486136abee0477745bc9
Subject: Re: [ogpx] Tourist use case
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2009 09:45:23 -0000

--0016e6d6486136abee0477745bc9
Content-Type: text/plain; charset=ISO-8859-1

The main reason why we're using REST and HTTP is to leverage the
infrastructure of the web and hence give ourselves massive scalability.  It
opens up the possibility of transparent caching and proxies and load
balancing and a lot of other good things, which we're going to need if
virtual worlds are going to become all-pervasive.  But to achieve that we
need to leave behind the narrow focus on sims and "free the services", which
is what REST and caps allows us.

The potential advantages really are huge, and go beyond mere caching in the
viewer.


Morgaine.



================================

On Mon, Nov 2, 2009 at 11:30 PM, Carlo Wood <carlo@alinoe.com> wrote:

> This only advantage that I can see by this (the region only tells you
> that object "xyz" is at position P with orientation O), is that then
> you might be able to cache objects on the viewer.
>
> However, THAT is only possible if 'xyz' is unique (some UUID) that changes
> as soon as an object is editted in anyway, expect position and orientation
> of course (rez parameters, not part of the object).
>
> On Mon, Nov 02, 2009 at 02:05:00PM +0000, Morgaine wrote:
> > On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
> >
> >
> >     I agree with you that information needed to see a rezzed object
> should
> >     come from the region (simulator), so -- in principle there is no
> direct
> >     reason that a viewer needs to have access to every asset server whose
> >     assets are rezzed.
> >
> >
> >
> > The region certainly needs to indicate which objects are rezzed in it ---
> it is
> > the single authority that holds that information --- there is no other
> place
> > where this information could come from in the current model.
> >
> > However, that does not mean that it has to actually hold the data, but
> merely
> > to indicate which it is so that it can be fetched.  Indeed, requiring the
> > region to hold the data or to proxy it would be really bad for protocol
> > scalability.  In any case, that's a policy choice --- our mechanism needs
> to be
> > more flexible than this in its service endpoint choices, and not require
> the
> > data to come from the region.  It is highly likely that many
> implementations
> > will aim for higher scalability than is possible to achieve by routing
> assets
> > through a sim.  Indeed, that's a primary reason for using caps for
> accessing
> > decoupled services in a REST-like manner.
> >
> > Decoupling the simulation from the storage is one of the most important
> things
> > that this protocol will achieve if we get it right.  We probably do need
> to
> > ensure that SL's existing "proxy everything" model can be expressed
> through
> > appropriate policy or deployment choices as it is likely to be a
> requirement,
> > but this should not constrain what the protocol can do under different
> policies
> > or deployment scenarios.
> >
> >
> > Morgaine.
> >
> >
> >
> >
> >
> >
> > ======================================
> >
> > On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood <carlo@alinoe.com> wrote:
> >
> >     Using common sense, I'd say:
> >
> >     * If you try to rez an object, policy comes in to determine if that
> is
> >     allowed.
> >
> >     * Once an object is rezzed, EVERYONE that is in the region (that is
> allowed
> >     to
> >      enter the region thus) can SEE that object (and interact with it).
> >
> >     I realize that it is *possible* for the region to implement a policy
> >     where it selectively shows data to some people and not to others, but
> >     I don't think we have to officially support every possible way to
> screw
> >     up shared experience in VWRAP, just because it would be possible to
> do so.
> >
> >     Compare with a protocol like SMPT: that dictates that if some email
> is
> >     received, it is required to react in one of a few given ways. There
> are
> >     other ways, but that would make the system stop functioning as
> intended,
> >     so that is Not The Idea.
> >
> >
> >     I agree with you that information needed to see a rezzed object
> should
> >     come from the region (simulator), so -- in principle there is no
> direct
> >     reason that a viewer needs to have access to every asset server whose
> >     assets are rezzed.
> >
> >
> >     An interesting question is now: what about assets that make up an
> >     avatar? Once in-world, attaching a new attachment, or changing
> clothes
> >     or shape, is just the same as rezzing of course: if the asset server
> >     allows access (by that region) than the region can buffer it and show
> >     it to everyone; otherwise attachment, or change of appearance, is
> >     disallowed.
> >     However, in the case of teleportation I think we need to act more
> >     intelligent than just black or white (allow or disallow the TP):
> >     I'm in favour of allowing the TP independent of assets being used at
> >     that moment, but instead detach assets and/or Ruth the avatar if
> >     need be (at least, give the user that option).
> >
> >     On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:
> >     > Be careful about blurring the use of "asset services" between
> "stuff in
> >     > regions" and "stuff I have". I think there is a big intersection -
> and
> >     may have
> >     > the same characteristics and/or protocols, but I also think they
> are are
> >     > distinct. I would guess that there will be asset services
> associated with
> >     both
> >     > agents and regions - off the top of my head:
> >     >
> >     > Uses of an agent-associated "asset" service:
> >     > * content to client app (inspect your inventory)
> >     > * content from client app (upload/import to inventory)
> >     > * content to region (rez something)
> >     > * content from region (buy/take something)
> >     > * content to agent (give something)
> >     > * content from agent (receive something)
> >     >
> >     > Uses of an region-associated "asset" service:
> >     > * content to client app (see the world)
> >     > * content from client app (upload/import to region)
> >     > * content to region (during teleport/region crossing)
> >     > * content from region (during teleport/region crossing)
> >     > * content to agent (buy/take something)
> >     > * content from agent (rez something)
> >     >
> >     > I'm using "asset" in quotes since that term may be overloaded.
> "Content"
> >     might
> >     > be a better term.
> >
> >     --
> >     Carlo Wood <carlo@alinoe.com>
> >     _______________________________________________
> >     ogpx mailing list
> >     ogpx@ietf.org
> >     https://www.ietf.org/mailman/listinfo/ogpx
> >
> >
>
> > _______________________________________________
> > ogpx mailing list
> > ogpx@ietf.org
> > https://www.ietf.org/mailman/listinfo/ogpx
>
>
> --
> Carlo Wood <carlo@alinoe.com>
>

--0016e6d6486136abee0477745bc9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The main reason why we&#39;re using REST and HTTP is to leverage the infras=
tructure of the web and hence give ourselves massive scalability.=A0 It ope=
ns up the possibility of transparent caching and proxies and load balancing=
 and a lot of other good things, which we&#39;re going to need if virtual w=
orlds are going to become all-pervasive.=A0 But to achieve that we need to =
leave behind the narrow focus on sims and &quot;free the services&quot;, wh=
ich is what REST and caps allows us.<br>
<br>The potential advantages really are huge, and go beyond mere caching in=
 the viewer.<br><br><br>Morgaine.<br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
><br><div class=3D"gmail_quote">On Mon, Nov 2, 2009 at 11:30 PM, Carlo Wood=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:carlo@alinoe.com">carlo@alinoe.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This only advanta=
ge that I can see by this (the region only tells you<br>
that object &quot;xyz&quot; is at position P with orientation O), is that t=
hen<br>
you might be able to cache objects on the viewer.<br>
<br>
However, THAT is only possible if &#39;xyz&#39; is unique (some UUID) that =
changes<br>
as soon as an object is editted in anyway, expect position and orientation<=
br>
of course (rez parameters, not part of the object).<br>
<div><div></div><div class=3D"h5"><br>
On Mon, Nov 02, 2009 at 02:05:00PM +0000, Morgaine wrote:<br>
&gt; On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood &lt;<a href=3D"mailto:carl=
o@alinoe.com">carlo@alinoe.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 I agree with you that information needed to see a rezzed objec=
t should<br>
&gt; =A0 =A0 come from the region (simulator), so -- in principle there is =
no direct<br>
&gt; =A0 =A0 reason that a viewer needs to have access to every asset serve=
r whose<br>
&gt; =A0 =A0 assets are rezzed.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The region certainly needs to indicate which objects are rezzed in it =
--- it is<br>
&gt; the single authority that holds that information --- there is no other=
 place<br>
&gt; where this information could come from in the current model.<br>
&gt;<br>
&gt; However, that does not mean that it has to actually hold the data, but=
 merely<br>
&gt; to indicate which it is so that it can be fetched. =A0Indeed, requirin=
g the<br>
&gt; region to hold the data or to proxy it would be really bad for protoco=
l<br>
&gt; scalability. =A0In any case, that&#39;s a policy choice --- our mechan=
ism needs to be<br>
&gt; more flexible than this in its service endpoint choices, and not requi=
re the<br>
&gt; data to come from the region. =A0It is highly likely that many impleme=
ntations<br>
&gt; will aim for higher scalability than is possible to achieve by routing=
 assets<br>
&gt; through a sim. =A0Indeed, that&#39;s a primary reason for using caps f=
or accessing<br>
&gt; decoupled services in a REST-like manner.<br>
&gt;<br>
&gt; Decoupling the simulation from the storage is one of the most importan=
t things<br>
&gt; that this protocol will achieve if we get it right. =A0We probably do =
need to<br>
&gt; ensure that SL&#39;s existing &quot;proxy everything&quot; model can b=
e expressed through<br>
&gt; appropriate policy or deployment choices as it is likely to be a requi=
rement,<br>
&gt; but this should not constrain what the protocol can do under different=
 policies<br>
&gt; or deployment scenarios.<br>
&gt;<br>
&gt;<br>
&gt; Morgaine.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt; On Mon, Nov 2, 2009 at 11:49 AM, Carlo Wood &lt;<a href=3D"mailto:carl=
o@alinoe.com">carlo@alinoe.com</a>&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 Using common sense, I&#39;d say:<br>
&gt;<br>
&gt; =A0 =A0 * If you try to rez an object, policy comes in to determine if=
 that is<br>
&gt; =A0 =A0 allowed.<br>
&gt;<br>
&gt; =A0 =A0 * Once an object is rezzed, EVERYONE that is in the region (th=
at is allowed<br>
&gt; =A0 =A0 to<br>
&gt; =A0 =A0 =A0enter the region thus) can SEE that object (and interact wi=
th it).<br>
&gt;<br>
&gt; =A0 =A0 I realize that it is *possible* for the region to implement a =
policy<br>
&gt; =A0 =A0 where it selectively shows data to some people and not to othe=
rs, but<br>
&gt; =A0 =A0 I don&#39;t think we have to officially support every possible=
 way to screw<br>
&gt; =A0 =A0 up shared experience in VWRAP, just because it would be possib=
le to do so.<br>
&gt;<br>
&gt; =A0 =A0 Compare with a protocol like SMPT: that dictates that if some =
email is<br>
&gt; =A0 =A0 received, it is required to react in one of a few given ways. =
There are<br>
&gt; =A0 =A0 other ways, but that would make the system stop functioning as=
 intended,<br>
&gt; =A0 =A0 so that is Not The Idea.<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 I agree with you that information needed to see a rezzed objec=
t should<br>
&gt; =A0 =A0 come from the region (simulator), so -- in principle there is =
no direct<br>
&gt; =A0 =A0 reason that a viewer needs to have access to every asset serve=
r whose<br>
&gt; =A0 =A0 assets are rezzed.<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 An interesting question is now: what about assets that make up=
 an<br>
&gt; =A0 =A0 avatar? Once in-world, attaching a new attachment, or changing=
 clothes<br>
&gt; =A0 =A0 or shape, is just the same as rezzing of course: if the asset =
server<br>
&gt; =A0 =A0 allows access (by that region) than the region can buffer it a=
nd show<br>
&gt; =A0 =A0 it to everyone; otherwise attachment, or change of appearance,=
 is<br>
&gt; =A0 =A0 disallowed.<br>
&gt; =A0 =A0 However, in the case of teleportation I think we need to act m=
ore<br>
&gt; =A0 =A0 intelligent than just black or white (allow or disallow the TP=
):<br>
&gt; =A0 =A0 I&#39;m in favour of allowing the TP independent of assets bei=
ng used at<br>
&gt; =A0 =A0 that moment, but instead detach assets and/or Ruth the avatar =
if<br>
&gt; =A0 =A0 need be (at least, give the user that option).<br>
&gt;<br>
&gt; =A0 =A0 On Fri, Oct 30, 2009 at 10:23:43AM -0700, Joshua Bell wrote:<b=
r>
&gt; =A0 =A0 &gt; Be careful about blurring the use of &quot;asset services=
&quot; between &quot;stuff in<br>
&gt; =A0 =A0 &gt; regions&quot; and &quot;stuff I have&quot;. I think there=
 is a big intersection - and<br>
&gt; =A0 =A0 may have<br>
&gt; =A0 =A0 &gt; the same characteristics and/or protocols, but I also thi=
nk they are are<br>
&gt; =A0 =A0 &gt; distinct. I would guess that there will be asset services=
 associated with<br>
&gt; =A0 =A0 both<br>
&gt; =A0 =A0 &gt; agents and regions - off the top of my head:<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; Uses of an agent-associated &quot;asset&quot; service:<br=
>
&gt; =A0 =A0 &gt; * content to client app (inspect your inventory)<br>
&gt; =A0 =A0 &gt; * content from client app (upload/import to inventory)<br=
>
&gt; =A0 =A0 &gt; * content to region (rez something)<br>
&gt; =A0 =A0 &gt; * content from region (buy/take something)<br>
&gt; =A0 =A0 &gt; * content to agent (give something)<br>
&gt; =A0 =A0 &gt; * content from agent (receive something)<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; Uses of an region-associated &quot;asset&quot; service:<b=
r>
&gt; =A0 =A0 &gt; * content to client app (see the world)<br>
&gt; =A0 =A0 &gt; * content from client app (upload/import to region)<br>
&gt; =A0 =A0 &gt; * content to region (during teleport/region crossing)<br>
&gt; =A0 =A0 &gt; * content from region (during teleport/region crossing)<b=
r>
&gt; =A0 =A0 &gt; * content to agent (buy/take something)<br>
&gt; =A0 =A0 &gt; * content from agent (rez something)<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; I&#39;m using &quot;asset&quot; in quotes since that term=
 may be overloaded. &quot;Content&quot;<br>
&gt; =A0 =A0 might<br>
&gt; =A0 =A0 &gt; be a better term.<br>
&gt;<br>
&gt; =A0 =A0 --<br>
&gt; =A0 =A0 Carlo Wood &lt;<a href=3D"mailto:carlo@alinoe.com">carlo@alino=
e.com</a>&gt;<br>
&gt; =A0 =A0 _______________________________________________<br>
&gt; =A0 =A0 ogpx mailing list<br>
&gt; =A0 =A0 <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
&gt; =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;<br>
&gt;<br>
<br>
&gt; _______________________________________________<br>
&gt; ogpx mailing list<br>
&gt; <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class=3D"h5">Carlo Wood &lt;<a href=3D"mailto:carlo@al=
inoe.com">carlo@alinoe.com</a>&gt;<br>
</div></div></blockquote></div><br>

--0016e6d6486136abee0477745bc9--

From morgaine.dinova@googlemail.com  Mon Nov  9 19:55:39 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A24CA3A6930 for <ogpx@core3.amsl.com>; Mon,  9 Nov 2009 19:55:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.85
X-Spam-Level: 
X-Spam-Status: No, score=-0.85 tagged_above=-999 required=5 tests=[AWL=-0.294,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SARE_ADULT2=1.42]
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 6O361fjQ6HK8 for <ogpx@core3.amsl.com>; Mon,  9 Nov 2009 19:55:38 -0800 (PST)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id 5A6183A685B for <ogpx@ietf.org>; Mon,  9 Nov 2009 19:55:37 -0800 (PST)
Received: by ewy3 with SMTP id 3so3866693ewy.37 for <ogpx@ietf.org>; Mon, 09 Nov 2009 19:56:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=EJNADJ7/c1zoFNp0XkFXI9G/YklS5CNEHY4GoT8AoIg=; b=EKThE+dotLfTTgUWr0IPwcfqWvTLwBTvBK+AnMr02m6ywhorwB2Tm/0U0pPrJCIEHm A3co6UYupayByJFqJiO5LTEcA66EqVA6VsAYmHPuZA1yxA/wdf+jd66Gzi8vQ5SY2pjM hhxcjXH8JwbNT8K9GAa5FfdpxdlHDRkVmKIjk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=e+DvWKvFCK9AmqaN8oiu/B38lpnaCJu0dSWyGJKlefenjiEA79VfwPvTMU64170e4J Hf8fHBdOkQ8O/X0n6m5Gt0gV9p5wEDDZ5zqxR0EEP4It1/jUWWm7ahI8n/VPt05GIbbP boJ6m9Jgl/W6VsjOEcfazl24SSe+plt+0XDpI=
MIME-Version: 1.0
Received: by 10.216.89.11 with SMTP id b11mr152370wef.171.1257825361234; Mon,  09 Nov 2009 19:56:01 -0800 (PST)
In-Reply-To: <f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com>
References: <e0b04bba0910262215td0cf125lb3129947e8f81891@mail.gmail.com> <f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com>
Date: Tue, 10 Nov 2009 03:56:01 +0000
Message-ID: <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d643fad88f580477fc49c6
Subject: Re: [ogpx] Limits to interoperability of scripted objects
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 03:55:39 -0000

--0016e6d643fad88f580477fc49c6
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell <josh@lindenlab.com> wrote:

>
> * Your (3) (common scripting environment) is intriguing. Sun's Project
> Wonderland uses Java (obviously...) as the common format, and (vastly
> simplifying) all objects in the VW are Java objects. I'd love to learn more
> from them about the challenges and successes. That said, at a protocol
> level, I don't think we'd ever dictate a common environment, so going down
> this road might turn into a de-facto common case of the content negotiation
> (just as the Web technically allows for client-side scripting languages
> other than Javascript, although they are used incredibly infrequently in
> practice).
>
> * Client-side scripts are also intriguing. If I think about what this means
> in practice, it's that the client is able to manipulate the state of objects
> in-world. Well, duh - that's what editing and appearance tools do! So...
> that capability (pun intended!) is a requirement at the protocol level,
> although I don't think we've even brushed on how to define it yet. It would
> be intriguing if the protocol were such that the client could expose a
> DOM-like view of the world to local scripts to observe and mutate.
>
>
>  I like both of those ideas.  I wonder if we could support them both in
principle with minimal effort by providing a generic hook using script
metadata.  Let some attribute select between "region" (for scripts running
in the current region as in SL), "avatar" (for HUD scripts that run in-world
but don't need region events so they can be run in a separate load-balaced
server pool), "home" (for scripts that always run in the agent's home
region), and "client" (for client-side scripts or plugins).  Further
attributes could specify the language and maybe a startup argument list
too.  (These are just random ideas, not cohesive.)

Thinking about the scripting languages themselves, presumably nobody would
argue in favour of turning LSL into an interop standard given the poverty of
its syntax, but even worse is the tortuous and complex semantic of its
system calls which would be very problematic to standardize, or maybe
impossible.  The SL scripting environment has evolved in a way that isn't
conducive to portability, not only because the implementation is closed and
quite unique, but also because it's tied fairly strongly to a proprietary
physics engine for events/simulation and to a rather esoteric communications
model.  These things conspire to make standardising around the SL scripting
mechanism very unlikely.  This gives us a solution to cross off the list,
but unfortunately doesn't offer us anything in its place.

Being realistic, forcing language commonality at this early stage is just
not going to happen, so we might as well lubricate the protocol machinery to
allow multiple scripting systems to be supported.  Eventually a de-facto
standard will emerge as happened with Javascript.  Let people with more
spare time than we have sort it out, and may the best idea win. :-)

As lubrication, I think we should provide at the very least some generic and
extensible metadata hooks in the protocol for this, otherwise the spec will
be modified incompatibly outside of the standard to support the diverse
scripting requirements of worlds, and then interop suffers.


Morgaine.





=========================================

On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell <josh@lindenlab.com> wrote:

> Good analysis as usual, Morgaine!
>
>
> On Mon, Oct 26, 2009 at 10:15 PM, Morgaine <morgaine.dinova@googlemail.com
> > wrote:
>
>> Being pragmatic about the situation, if we wish to see interop of
>> scripting in the relatively near future, we need to find an approach that is
>> inherently interoperable.  Here are some ideas that might be relevant to
>> this end (these are alternatives, they don't all apply simultaneously):
>>
>>
>>    1. Make script state transfer a deployment option:  both source and
>>    destination regions have to allow script state transfer for it to happen.
>>    2. Worlds running different scripting engine implementations do not
>>    transfer state and hence scripts are initialized on teleport.
>>    3. Define a common scripting language and virtual machine environment
>>    --- ie. a web-like Javascript approach but for regions.
>>    4. If script state continuity is desired on teleports between worlds
>>    running different script engines, let such scripts run client-side.
>>
>>
> A few thoughts on the above:
>
> * Even though the Web appears to have given up on content negotiation over
> HTTP, I'm still a fan and I think cross-system interop like this is a good
> place for it. During Region-to-Region state transfer, you could imagine the
> destination region advertising the script state types it accepts
> (vendor/com.lindenlab.secondlife.lsl2mono, vendor/org.opensim.dotnetengine,
> ...), and the source region delivering one tagged with appropriate type. I
> would imagine we'll need similar logic for static content as well - articles
> of clothing could have have "prim" or "mesh" based versions, and regions may
> prefer one type to another. (Although it would be more likely to have both
> available on the region, and have content negotiation occur on the
> region->viewer resource transfer.)
>
> * Given the desire for "tourist" models (using the term loosely - I "live"
> on my home grid, but like to visit other grids), it doesn't seem like
> there's a one-size-fits-all approach (since region-to-region teleports in my
> home grid and region-to-region teleports between grids utilize the same
> protocol). So... this is definitely part of the protocol's mandate to sort
> out.
>
> * Combining the above two points, it implies that attachments will have to
> cope with moving from areas where they have scripts running to scripts not
> running (if the code/state is not compatible with the hosting region).
> Fortunately, we have precedent for that. :)
>
> * Infinity and I very briefly hand-waved about whether "portable" content
> (primarily, attachments to avatars) should even be executed within the
> region domain. Perhaps they should be executing in the agent domain? That's
> a radical departure from how SL or OpenSim work today. (If you squint your
> eyes and partition the current services, at least.) - at any rate, today
> there is no script execution outside of a region. It's an intriguing idea,
> but by no means complete - how such fine grained state might be updated
> between domains, for example. Vehicles come to mind as another case, and
> those have no clear "home base" for script execution. I suspect this is not
> tractable for the first iteration of VWRAP, but I don't want to dismiss it.
>
> * Your (3) (common scripting environment) is intriguing. Sun's Project
> Wonderland uses Java (obviously...) as the common format, and (vastly
> simplifying) all objects in the VW are Java objects. I'd love to learn more
> from them about the challenges and successes. That said, at a protocol
> level, I don't think we'd ever dictate a common environment, so going down
> this road might turn into a de-facto common case of the content negotiation
> (just as the Web technically allows for client-side scripting languages
> other than Javascript, although they are used incredibly infrequently in
> practice).
>
> * Client-side scripts are also intriguing. If I think about what this means
> in practice, it's that the client is able to manipulate the state of objects
> in-world. Well, duh - that's what editing and appearance tools do! So...
> that capability (pun intended!) is a requirement at the protocol level,
> although I don't think we've even brushed on how to define it yet. It would
> be intriguing if the protocol were such that the client could expose a
> DOM-like view of the world to local scripts to observe and mutate.
>
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>

--0016e6d643fad88f580477fc49c6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:josh@lindenlab.com">josh@lindenlab.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"border=
-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-lef=
t: 1ex;">
<br><div style=3D"margin-left: 40px;">* Your (3) (common scripting environm=
ent) is intriguing. Sun&#39;s
Project Wonderland uses Java (obviously...) as the common format, and
(vastly simplifying) all objects in the VW are Java objects. I&#39;d love
to learn more from them about the challenges and successes. That said,
at a protocol level, I don&#39;t think we&#39;d ever dictate a common
environment, so going down this road might turn into a de-facto common
case of the content negotiation (just as the Web technically allows for
client-side scripting languages other than Javascript, although they
are used incredibly infrequently in practice).=A0 <br><br>* Client-side scr=
ipts are also intriguing. If I think about what
this means in practice, it&#39;s that the client is able to manipulate the
state of objects in-world. Well, duh - that&#39;s what editing and
appearance tools do! So... that capability (pun intended!) is a
requirement at the protocol level, although I don&#39;t think we&#39;ve eve=
n
brushed on how to define it yet. It would be intriguing if the protocol
were such that the client could expose a DOM-like view of the world to
local scripts to observe and mutate.<br></div>

<br>
<br></blockquote><div>=A0I like both of those ideas.=A0 I wonder if we coul=
d support them both in principle with minimal effort by providing a generic=
 hook using script metadata.=A0 Let some attribute select between &quot;reg=
ion&quot; (for scripts running in the current region as in SL), &quot;avata=
r&quot; (for HUD scripts that run in-world but don&#39;t need region events=
 so they can be run in a separate load-balaced server pool), &quot;home&quo=
t; (for scripts that always run in the agent&#39;s home region), and &quot;=
client&quot; (for client-side scripts or plugins).=A0 Further attributes co=
uld specify the language and maybe a startup argument list too.=A0 (These a=
re just random ideas, not cohesive.)<br>
<br>Thinking about the scripting languages themselves, presumably nobody wo=
uld argue in favour of turning LSL into an interop standard given the pover=
ty of its syntax, but even worse is the tortuous and complex semantic of it=
s system calls which would be very problematic to standardize, or maybe imp=
ossible.=A0 The SL scripting environment has evolved in a way that isn&#39;=
t conducive to portability, not only because the implementation is closed a=
nd quite unique, but also because it&#39;s tied fairly strongly to a propri=
etary physics engine for events/simulation and to a rather esoteric communi=
cations model.=A0 These things conspire to make standardising around the SL=
 scripting mechanism very unlikely.=A0 This gives us a solution to cross of=
f the list, but unfortunately doesn&#39;t offer us anything in its place.<b=
r>
<br>Being realistic, forcing language commonality at this early stage is ju=
st not going to happen, so we might as well lubricate the protocol machiner=
y to allow multiple scripting systems to be supported.=A0 Eventually a de-f=
acto standard will emerge as happened with Javascript.=A0 Let people with m=
ore spare time than we have sort it out, and may the best idea win. :-)<br>
<br>As lubrication, I think we should provide at the very least some generi=
c and extensible metadata hooks in the protocol for this, otherwise the spe=
c will be modified incompatibly outside of the standard to support the dive=
rse scripting requirements of worlds, and then interop suffers.<br>
</div></div><br><br>Morgaine.<br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">On Tue, Oct 2=
7, 2009 at 4:51 PM, Joshua Bell <span dir=3D"ltr">&lt;<a href=3D"mailto:jos=
h@lindenlab.com">josh@lindenlab.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class=3D"gma=
il_quote">Good analysis as usual, Morgaine!<div class=3D"im"><br><br>On Mon=
, Oct 26, 2009 at 10:15 PM, Morgaine <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:morgaine.dinova@googlemail.com" target=3D"_blank">morgaine.dinova@googlem=
ail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Being pragmatic a=
bout the situation, if we wish to see interop of scripting in the relativel=
y near future, we need to find an approach that is inherently interoperable=
.=A0 Here are some ideas that might be relevant to this end (these are alte=
rnatives, they don&#39;t all apply simultaneously):<br>


<br><ol><li>Make script state transfer a deployment option:=A0 both source =
and destination regions have to allow script state transfer for it to happe=
n.</li><li>Worlds running different scripting engine implementations do not=
 transfer state and hence scripts are initialized on teleport.</li>


<li>Define a common scripting language and virtual machine environment --- =
ie. a web-like Javascript approach but for regions.</li><li>If script state=
 continuity is desired on teleports between worlds running different script=
 engines, let such scripts run client-side.<br>


</li></ol></blockquote></div></div><br>A few thoughts on the above:<br><br>=
* Even though the Web appears to have given up on content negotiation over =
HTTP, I&#39;m still a fan and I think cross-system interop like this is a g=
ood place for it. During Region-to-Region state transfer, you could imagine=
 the destination region advertising the script state types it accepts (vend=
or/com.lindenlab.secondlife.lsl2mono, vendor/org.opensim.dotnetengine, ...)=
, and the source region delivering one tagged with appropriate type. I woul=
d imagine we&#39;ll need similar logic for static content as well - article=
s of clothing could have have &quot;prim&quot; or &quot;mesh&quot; based ve=
rsions, and regions may prefer one type to another. (Although it would be m=
ore likely to have both available on the region, and have content negotiati=
on occur on the region-&gt;viewer resource transfer.)<br>

<br>* Given the desire for &quot;tourist&quot; models (using the term loose=
ly - I &quot;live&quot; on my home grid, but like to visit other grids), it=
 doesn&#39;t seem like there&#39;s a one-size-fits-all approach (since regi=
on-to-region teleports in my home grid and region-to-region teleports betwe=
en grids utilize the same protocol). So... this is definitely part of the p=
rotocol&#39;s mandate to sort out.<br>

<br>* Combining the above two points, it implies that attachments will have=
 to cope with moving from areas where they have scripts running to scripts =
not running (if the code/state is not compatible with the hosting region). =
Fortunately, we have precedent for that. :)<br>

<br>* Infinity and I very briefly hand-waved about whether &quot;portable&q=
uot; content (primarily, attachments to avatars) should even be executed wi=
thin the region domain. Perhaps they should be executing in the agent domai=
n? That&#39;s a radical departure from how SL or OpenSim work today. (If yo=
u squint your eyes and partition the current services, at least.) - at any =
rate, today there is no script execution outside of a region. It&#39;s an i=
ntriguing idea, but by no means complete - how such fine grained state migh=
t be updated between domains, for example. Vehicles come to mind as another=
 case, and those have no clear &quot;home base&quot; for script execution. =
I suspect this is not tractable for the first iteration of VWRAP, but I don=
&#39;t want to dismiss it.<br>

<br>* Your (3) (common scripting environment) is intriguing. Sun&#39;s Proj=
ect Wonderland uses Java (obviously...) as the common format, and (vastly s=
implifying) all objects in the VW are Java objects. I&#39;d love to learn m=
ore from them about the challenges and successes. That said, at a protocol =
level, I don&#39;t think we&#39;d ever dictate a common environment, so goi=
ng down this road might turn into a de-facto common case of the content neg=
otiation (just as the Web technically allows for client-side scripting lang=
uages other than Javascript, although they are used incredibly infrequently=
 in practice).=A0 <br>

<br>* Client-side scripts are also intriguing. If I think about what this m=
eans in practice, it&#39;s that the client is able to manipulate the state =
of objects in-world. Well, duh - that&#39;s what editing and appearance too=
ls do! So... that capability (pun intended!) is a requirement at the protoc=
ol level, although I don&#39;t think we&#39;ve even brushed on how to defin=
e it yet. It would be intriguing if the protocol were such that the client =
could expose a DOM-like view of the world to local scripts to observe and m=
utate.<br>

<br>
<br>_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
<br></blockquote></div><br>

--0016e6d643fad88f580477fc49c6--

From lenglish5@cox.net  Mon Nov  9 20:32:06 2009
Return-Path: <lenglish5@cox.net>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FE8F3A69AE for <ogpx@core3.amsl.com>; Mon,  9 Nov 2009 20:32:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.466
X-Spam-Level: 
X-Spam-Status: No, score=-1.466 tagged_above=-999 required=5 tests=[AWL=-0.287, BAYES_00=-2.599, SARE_ADULT2=1.42]
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 cB5sMtn+1++t for <ogpx@core3.amsl.com>; Mon,  9 Nov 2009 20:32:04 -0800 (PST)
Received: from fed1rmmtao105.cox.net (fed1rmmtao105.cox.net [68.230.241.41]) by core3.amsl.com (Postfix) with ESMTP id 9ABFE3A680F for <ogpx@ietf.org>; Mon,  9 Nov 2009 20:32:04 -0800 (PST)
Received: from fed1rmimpo03.cox.net ([70.169.32.75]) by fed1rmmtao105.cox.net (InterMail vM.8.00.01.00 201-2244-105-20090324) with ESMTP id <20091110043232.MVAT21106.fed1rmmtao105.cox.net@fed1rmimpo03.cox.net>; Mon, 9 Nov 2009 23:32:32 -0500
Received: from ip72-200-121-127.tc.ph.cox.net ([72.200.121.127]) by fed1rmimpo03.cox.net with bizsmtp id 3GYX1d0012l1Ksg04GYXfq; Mon, 09 Nov 2009 23:32:31 -0500
X-VR-Score: -150.00
X-Authority-Analysis: v=1.0 c=1 a=bAL6ikEbh6YA:10 a=Wajolswj7cQA:10 a=cfHPFXhNAAAA:8 a=iXggwkVfAAAA:8 a=mK_AVkanAAAA:8 a=48vgC7mUAAAA:8 a=Jpa5mPCZqXTC3dl-DtgA:9 a=b5v2ElUMFtu7Pj4dLiEA:7 a=JS9MPh-RegsMxNK3B6XUgm1aKxkA:4 a=oXxgVVfU3OUA:10 a=x6U5xrJgyBEA:10 a=9xyTavCNlvEA:10 a=lZB815dzVvQA:10 a=ZmViHxVqXD6zOegd:21 a=SCE_-stLeQkWYoVk:21
X-CM-Score: 0.00
Message-ID: <4AF8ECDE.2010900@cox.net>
Date: Mon, 09 Nov 2009 21:32:30 -0700
From: Lawson English <lenglish5@cox.net>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Morgaine <morgaine.dinova@googlemail.com>
References: <e0b04bba0910262215td0cf125lb3129947e8f81891@mail.gmail.com>	<f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com> <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com>
In-Reply-To: <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Limits to interoperability of scripted objects
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: lenglish5@cox.net
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 04:32:06 -0000

Morgaine has seen me hype this many types, but perhaps Joshua and others 
have not not:

http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discussion ...


There's many uses for client-side scripting, from custom GUIs to 
manipulation of elements (avatars, objects, etc) going out to the sim 
directly, to manipulating objects client-side only say for use in a 
mechanima play where only the other characters in the play can see what 
is going on. Hybrid situations, as is done with the puppeteering code 
mentioned at the bottom of the page, could delay updating until 
everything is resolved client-side. A collection of avatars could be 
participating in a private play, battle, simulation, whatever, and only 
use the main simulator to provide a backdrop for whatever it is they are 
doing with or without eventually updating the simulator as to their 
position/actions/etc.

And no doubt there are many other scenarios that we haven't conceived of 
yet where "client side scripting" would be useful. And one extreme is 
the Second Life use-case where the server handles virtually every aspect 
of the avatar except limited user input. At the other end is the 
Croquet/Cobalt case where clients act as servers for their own private 
worlds that are, in principle, P2P in nature. While the VWRAP scenario 
assumes more Second Life-ish scenarios, there's plenty of room for more 
Croquet-like situations,  IMHO. The server(s) need not know what input 
the client is working with. Perhaps there's enhanced physics being used 
in a special MC Escher style world. or perhaps the client is getting a 
direct feed of planetarium data to light up the sky. Both situations 
exist or are being worked on in a rudimentary way in Second Life itself. 
There's no reason to assume ANY limitations save those required for 
security/trust issues, and those will need to be applied on the server 
side for any realistically secure scenario (assuming that the 
client-side plug-ins are trustworthy for the end-user's purposes, of course)

 
Lawson



Morgaine wrote:
> On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell <josh@lindenlab.com 
> <mailto:josh@lindenlab.com>> wrote:
>
>
>     * Your (3) (common scripting environment) is intriguing. Sun's
>     Project Wonderland uses Java (obviously...) as the common format,
>     and (vastly simplifying) all objects in the VW are Java objects.
>     I'd love to learn more from them about the challenges and
>     successes. That said, at a protocol level, I don't think we'd ever
>     dictate a common environment, so going down this road might turn
>     into a de-facto common case of the content negotiation (just as
>     the Web technically allows for client-side scripting languages
>     other than Javascript, although they are used incredibly
>     infrequently in practice). 
>
>     * Client-side scripts are also intriguing. If I think about what
>     this means in practice, it's that the client is able to manipulate
>     the state of objects in-world. Well, duh - that's what editing and
>     appearance tools do! So... that capability (pun intended!) is a
>     requirement at the protocol level, although I don't think we've
>     even brushed on how to define it yet. It would be intriguing if
>     the protocol were such that the client could expose a DOM-like
>     view of the world to local scripts to observe and mutate.
>
>
>  I like both of those ideas.  I wonder if we could support them both 
> in principle with minimal effort by providing a generic hook using 
> script metadata.  Let some attribute select between "region" (for 
> scripts running in the current region as in SL), "avatar" (for HUD 
> scripts that run in-world but don't need region events so they can be 
> run in a separate load-balaced server pool), "home" (for scripts that 
> always run in the agent's home region), and "client" (for client-side 
> scripts or plugins).  Further attributes could specify the language 
> and maybe a startup argument list too.  (These are just random ideas, 
> not cohesive.)
>
> Thinking about the scripting languages themselves, presumably nobody 
> would argue in favour of turning LSL into an interop standard given 
> the poverty of its syntax, but even worse is the tortuous and complex 
> semantic of its system calls which would be very problematic to 
> standardize, or maybe impossible.  The SL scripting environment has 
> evolved in a way that isn't conducive to portability, not only because 
> the implementation is closed and quite unique, but also because it's 
> tied fairly strongly to a proprietary physics engine for 
> events/simulation and to a rather esoteric communications model.  
> These things conspire to make standardising around the SL scripting 
> mechanism very unlikely.  This gives us a solution to cross off the 
> list, but unfortunately doesn't offer us anything in its place.
>
> Being realistic, forcing language commonality at this early stage is 
> just not going to happen, so we might as well lubricate the protocol 
> machinery to allow multiple scripting systems to be supported.  
> Eventually a de-facto standard will emerge as happened with 
> Javascript.  Let people with more spare time than we have sort it out, 
> and may the best idea win. :-)
>
> As lubrication, I think we should provide at the very least some 
> generic and extensible metadata hooks in the protocol for this, 
> otherwise the spec will be modified incompatibly outside of the 
> standard to support the diverse scripting requirements of worlds, and 
> then interop suffers.
>
>
> Morgaine.
>
>
>
>
>
> =========================================
>
> On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell <josh@lindenlab.com 
> <mailto:josh@lindenlab.com>> wrote:
>
>     Good analysis as usual, Morgaine!
>
>
>     On Mon, Oct 26, 2009 at 10:15 PM, Morgaine
>     <morgaine.dinova@googlemail.com
>     <mailto:morgaine.dinova@googlemail.com>> wrote:
>
>         Being pragmatic about the situation, if we wish to see interop
>         of scripting in the relatively near future, we need to find an
>         approach that is inherently interoperable.  Here are some
>         ideas that might be relevant to this end (these are
>         alternatives, they don't all apply simultaneously):
>
>            1. Make script state transfer a deployment option:  both
>               source and destination regions have to allow script
>               state transfer for it to happen.
>            2. Worlds running different scripting engine
>               implementations do not transfer state and hence scripts
>               are initialized on teleport.
>            3. Define a common scripting language and virtual machine
>               environment --- ie. a web-like Javascript approach but
>               for regions.
>            4. If script state continuity is desired on teleports
>               between worlds running different script engines, let
>               such scripts run client-side.
>
>
>     A few thoughts on the above:
>
>     * Even though the Web appears to have given up on content
>     negotiation over HTTP, I'm still a fan and I think cross-system
>     interop like this is a good place for it. During Region-to-Region
>     state transfer, you could imagine the destination region
>     advertising the script state types it accepts
>     (vendor/com.lindenlab.secondlife.lsl2mono,
>     vendor/org.opensim.dotnetengine, ...), and the source region
>     delivering one tagged with appropriate type. I would imagine we'll
>     need similar logic for static content as well - articles of
>     clothing could have have "prim" or "mesh" based versions, and
>     regions may prefer one type to another. (Although it would be more
>     likely to have both available on the region, and have content
>     negotiation occur on the region->viewer resource transfer.)
>
>     * Given the desire for "tourist" models (using the term loosely -
>     I "live" on my home grid, but like to visit other grids), it
>     doesn't seem like there's a one-size-fits-all approach (since
>     region-to-region teleports in my home grid and region-to-region
>     teleports between grids utilize the same protocol). So... this is
>     definitely part of the protocol's mandate to sort out.
>
>     * Combining the above two points, it implies that attachments will
>     have to cope with moving from areas where they have scripts
>     running to scripts not running (if the code/state is not
>     compatible with the hosting region). Fortunately, we have
>     precedent for that. :)
>
>     * Infinity and I very briefly hand-waved about whether "portable"
>     content (primarily, attachments to avatars) should even be
>     executed within the region domain. Perhaps they should be
>     executing in the agent domain? That's a radical departure from how
>     SL or OpenSim work today. (If you squint your eyes and partition
>     the current services, at least.) - at any rate, today there is no
>     script execution outside of a region. It's an intriguing idea, but
>     by no means complete - how such fine grained state might be
>     updated between domains, for example. Vehicles come to mind as
>     another case, and those have no clear "home base" for script
>     execution. I suspect this is not tractable for the first iteration
>     of VWRAP, but I don't want to dismiss it.
>
>     * Your (3) (common scripting environment) is intriguing. Sun's
>     Project Wonderland uses Java (obviously...) as the common format,
>     and (vastly simplifying) all objects in the VW are Java objects.
>     I'd love to learn more from them about the challenges and
>     successes. That said, at a protocol level, I don't think we'd ever
>     dictate a common environment, so going down this road might turn
>     into a de-facto common case of the content negotiation (just as
>     the Web technically allows for client-side scripting languages
>     other than Javascript, although they are used incredibly
>     infrequently in practice). 
>
>     * Client-side scripts are also intriguing. If I think about what
>     this means in practice, it's that the client is able to manipulate
>     the state of objects in-world. Well, duh - that's what editing and
>     appearance tools do! So... that capability (pun intended!) is a
>     requirement at the protocol level, although I don't think we've
>     even brushed on how to define it yet. It would be intriguing if
>     the protocol were such that the client could expose a DOM-like
>     view of the world to local scripts to observe and mutate.
>
>
>     _______________________________________________
>     ogpx mailing list
>     ogpx@ietf.org <mailto:ogpx@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ogpx
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>   


From josh@lindenlab.com  Tue Nov 10 09:19:11 2009
Return-Path: <josh@lindenlab.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D5163A6B2B for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 09:19:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[AWL=0.315,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 UYKRkwn1AZC8 for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 09:19:10 -0800 (PST)
Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com [209.85.223.186]) by core3.amsl.com (Postfix) with ESMTP id 2C8473A6B1A for <ogpx@ietf.org>; Tue, 10 Nov 2009 09:19:10 -0800 (PST)
Received: by iwn16 with SMTP id 16so199562iwn.29 for <ogpx@ietf.org>; Tue, 10 Nov 2009 09:19:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.168.131 with SMTP id u3mr532550iby.26.1257873573274; Tue,  10 Nov 2009 09:19:33 -0800 (PST)
In-Reply-To: <4AF8ECDE.2010900@cox.net>
References: <e0b04bba0910262215td0cf125lb3129947e8f81891@mail.gmail.com> <f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com> <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com> <4AF8ECDE.2010900@cox.net>
Date: Tue, 10 Nov 2009 09:19:33 -0800
Message-ID: <f72742de0911100919r76c337b6i980736db91f7f53c@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: lenglish5@cox.net
Content-Type: multipart/alternative; boundary=001636b1451381e5310478078371
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Limits to interoperability of scripted objects
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 17:19:11 -0000

--001636b1451381e5310478078371
Content-Type: text/plain; charset=UTF-8

On Mon, Nov 9, 2009 at 8:32 PM, Lawson English <lenglish5@cox.net> wrote:

> Morgaine has seen me hype this many types, but perhaps Joshua and others
> have not not:
>
> http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discussion ...
>
>
Nifty stuff. What do you think needs to be exposed at a protocol level to
enable these scenarios, and do you think that fits into any of the currently
sketched out drafts or forms a part of an as-yet unidentified draft? It
sounds like much of it is captured by the use case: clients are able to
manipulate simulation state for avatars and other objects.

  At the other end is the Croquet/Cobalt case where clients act as servers
> for their own private worlds that are, in principle, P2P in nature. While
> the VWRAP scenario assumes more Second Life-ish scenarios, there's plenty of
> room for more Croquet-like situations,  IMHO.


No disagreement. It's also interesting to think about stretching the VWRAP
model towards P2P scenarios. The model dictates that there is an
authoritative service for a region, but it's conceivable that if I invite
you to my space, I have a single application on my personal host that is
providing both the agent services and region services, and negotiates with
your personal host's agent service.


> There's no reason to assume ANY limitations save those required for
> security/trust issues, and those will need to be applied on the server side
> for any realistically secure scenario (assuming that the client-side
> plug-ins are trustworthy for the end-user's purposes, of course)
>

...which points out there are at least two scenarios for client-side dynamic
code: stuff that runs with effectively full trust of the user (basically has
unfettered access to agent and region services on the user's behalf) and
stuff that must be sandboxed. The former category would include the client
application itself as well as "Greasemonkey"-style extensions. The latter
would include content from arbitrary objects, much like JavaScript within a
web page running within the browser security context. Intriguing... it seems
like the Same Origin Policy from the web could apply directly to any set of
VWRAP services as well, although if the logic is coming from user-generated
content rather than the region authority itself, this runs into the same
exciting world that Google and others face with advertisement-hosted scripts
which need to be further sandboxed so that ads can't monkey with your
account, despite being served from the same domain.

--001636b1451381e5310478078371
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Mon, Nov 9, 2009 at 8:32 PM, Lawson English <=
span dir=3D"ltr">&lt;<a href=3D"mailto:lenglish5@cox.net">lenglish5@cox.net=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"border=
-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-lef=
t: 1ex;">
Morgaine has seen me hype this many types, but perhaps Joshua and others ha=
ve not not:<br>
<br>
<a href=3D"http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discu=
ssion" target=3D"_blank">http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn=
/Plugins_discussion</a> ...<br>
<br></blockquote><div><br>Nifty stuff. What do you think needs to be expose=
d at a protocol level to enable these scenarios, and do you think that fits=
 into any of the currently sketched out drafts or forms a part of an as-yet=
 unidentified draft? It sounds like much of it is captured by the use case:=
 clients are able to manipulate simulation state for avatars and other obje=
cts. <br>
<br></div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid=
 rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">=C2=A0
At the other end is the Croquet/Cobalt case where clients act as servers fo=
r their own private worlds that are, in principle, P2P in nature. While the=
 VWRAP scenario assumes more Second Life-ish scenarios, there&#39;s plenty =
of room for more Croquet-like situations, =C2=A0IMHO. </blockquote>
<div><br>No disagreement. It&#39;s also interesting to think about stretchi=
ng the VWRAP model towards P2P scenarios. The model dictates that there is =
an authoritative service for a region, but it&#39;s conceivable that if I i=
nvite you to my space, I have a single application on my personal host that=
 is providing both the agent services and region services, and negotiates w=
ith your personal host&#39;s agent service.<br>
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px sol=
id rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">There=
&#39;s no reason to assume ANY limitations save those required for security=
/trust issues, and those will need to be applied on the server side for any=
 realistically secure scenario (assuming that the client-side plug-ins are =
trustworthy for the end-user&#39;s purposes, of course)<br>
</blockquote></div><br>...which points out there are at least two scenarios=
 for client-side dynamic code: stuff that runs with effectively full trust =
of the user (basically has unfettered access to agent and region services o=
n the user&#39;s behalf) and stuff that must be sandboxed. The former categ=
ory would include the client application itself as well as &quot;Greasemonk=
ey&quot;-style extensions. The latter would include content from arbitrary =
objects, much like JavaScript within a web page running within the browser =
security context. Intriguing... it seems like the Same Origin Policy from t=
he web could apply directly to any set of VWRAP services as well, although =
if the logic is coming from user-generated content rather than the region a=
uthority itself, this runs into the same exciting world that Google and oth=
ers face with advertisement-hosted scripts which need to be further sandbox=
ed so that ads can&#39;t monkey with your account, despite being served fro=
m the same domain.<br>
<br>

--001636b1451381e5310478078371--

From carlo@alinoe.com  Tue Nov 10 12:12:44 2009
Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC3B13A69F1 for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 12:12:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.712
X-Spam-Level: 
X-Spam-Status: No, score=0.712 tagged_above=-999 required=5 tests=[AWL=-0.272,  BAYES_40=-0.185, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 S+jvAWMPRjvM for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 12:12:44 -0800 (PST)
Received: from viefep15-int.chello.at (viefep15-int.chello.at [62.179.121.35]) by core3.amsl.com (Postfix) with ESMTP id 8582B3A69AF for <ogpx@ietf.org>; Tue, 10 Nov 2009 12:12:43 -0800 (PST)
Received: from edge01.upc.biz ([192.168.13.236]) by viefep15-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20091110201309.YYKM8249.viefep15-int.chello.at@edge01.upc.biz>; Tue, 10 Nov 2009 21:13:09 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge01.upc.biz with edge id 3YD71d08L0FlQed01YD8pF; Tue, 10 Nov 2009 21:13:09 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1N7x4H-0001Fr-6A; Tue, 10 Nov 2009 21:11:57 +0100
Date: Tue, 10 Nov 2009 21:11:57 +0100
From: Carlo Wood <carlo@alinoe.com>
To: Joshua Bell <josh@lindenlab.com>
Message-ID: <20091110201157.GA10861@alinoe.com>
References: <e0b04bba0910262215td0cf125lb3129947e8f81891@mail.gmail.com> <f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com> <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com> <4AF8ECDE.2010900@cox.net> <f72742de0911100919r76c337b6i980736db91f7f53c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f72742de0911100919r76c337b6i980736db91f7f53c@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: lenglish5@cox.net, ogpx@ietf.org
Subject: Re: [ogpx] Limits to interoperability of scripted objects
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 20:12:44 -0000

On Tue, Nov 10, 2009 at 09:19:33AM -0800, Joshua Bell wrote:
> sketched out drafts or forms a part of an as-yet unidentified draft? It sounds
> like much of it is captured by the use case: clients are able to manipulate
> simulation state for avatars and other objects.

I'd also like to ask some attention for synchronization:

Apart from vehicles (which totally don't work for me in SL due to lag)
there are lots of cases where a desync could be avoided by having
the client calculate (locally) what is the position of that what
it's avatar interacts with.

Most common example: hugging another avatar. Right now avatars are
clumpsy bumping into eachother in an attempt to "sync" the distance
and then stick an arm straight to their friends stomach, or attempt
to hug the air completely.

Assuming client-side scripting, I hope there will be SOME way to
make animated hugs (or any couple animations) really work (with
effort). In my mind this would mean that two (or more?) viewers
negotiate what couple (or multi-) animation they want to play
and then ask the server for a mere 'start signal', after which
each client plays all the animations for all the avatars involved
locally, until the server says: ok, animation terminated.

-- 
Carlo Wood <carlo@alinoe.com>

From carlo@alinoe.com  Tue Nov 10 12:42:46 2009
Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91EC43A68AF for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 12:42:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.83
X-Spam-Level: 
X-Spam-Status: No, score=0.83 tagged_above=-999 required=5 tests=[AWL=-0.340,  BAYES_50=0.001, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 QgdIi7f7vcTU for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 12:42:42 -0800 (PST)
Received: from viefep15-int.chello.at (viefep15-int.chello.at [62.179.121.35]) by core3.amsl.com (Postfix) with ESMTP id 46B653A67E4 for <ogpx@ietf.org>; Tue, 10 Nov 2009 12:42:42 -0800 (PST)
Received: from edge01.upc.biz ([192.168.13.236]) by viefep15-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20091110204308.DEJ8249.viefep15-int.chello.at@edge01.upc.biz> for <ogpx@ietf.org>; Tue, 10 Nov 2009 21:43:08 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge01.upc.biz with edge id 3Yj51d0Gj0FlQed01Yj6rb; Tue, 10 Nov 2009 21:43:08 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1N7xXH-0001ew-0t for ogpx@ietf.org; Tue, 10 Nov 2009 21:41:55 +0100
Date: Tue, 10 Nov 2009 21:41:55 +0100
From: Carlo Wood <carlo@alinoe.com>
To: ogpx@ietf.org
Message-ID: <20091110204155.GA5757@alinoe.com>
References: <e0b04bba0910262215td0cf125lb3129947e8f81891@mail.gmail.com> <f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com> <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com> <4AF8ECDE.2010900@cox.net> <f72742de0911100919r76c337b6i980736db91f7f53c@mail.gmail.com> <20091110201157.GA10861@alinoe.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091110201157.GA10861@alinoe.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [ogpx] Synchronization of gestures (was: Limits to interoperability of scripted objects)
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 20:42:46 -0000

On Tue, Nov 10, 2009 at 09:11:57PM +0100, Carlo Wood wrote:
> make animated hugs (or any couple animations) really work (with
> effort).

without*


Here is an idea of how it could work:

* Viewer A (or object) initiates Multi-gesture Request
  to N (other) viewers, this involves a list of the
  animations (UUID) to play for each of the avatars
  involved, and sounds to play etc, and the starting
  position in the world of each avatar.
* Each viewer reacts with: Ok, will try; or Nope, I won't.
  If any viewer denies the request (or times out?)
  then the server informs all viewers that the multi-
  animation was aborted (and why). [ An optional flag
  could be to continue anyway, but without the avatar(s)
  that don't want to. ]
* Once all avatars that want to play the multi-animation
  are known, the server sends them a message: "We have a go!"
* All viewers that have all the needed information to
  continue (downloaded and cached the animations, sounds etc)
  send a message to the server: "ready!"
* As soon as all viewers are ready (optionally, a parameter
  of the original request includes a timeout after which
  the delayed avatar is considered to have said "no"),
  the server informs all viewers to start playing the
  multi-gesture.

And YAY! finally a completely synchronized couple (and
multi) animation, even synced with sound!

Options in case of delays (timeouts) should be:
- Play as soon data available locally,
- Wait till at least N, or at least those, avatars
  are ready.
- Abort completely if any can't play in time.
- If someone is delayed and the rest already plays
  the animation, then the viewer can decide to abort
  or play the animations locally anyway, as soon as
  they become avaiable, etc etc... All those possibilities
  are mere bits in already existing messages, so why not.

As a side effect of this it should be possible to
play a gesture involving animation and sound by ONE
avatar (as are the gestures in SL now) but *synchronized*:
everyone sees it at the same time, and the animations ARE
synced with the sound once the start to play (unlike now,
where the animation is played and 30 seconds later you
hear the sound).

-- 
Carlo Wood <carlo@alinoe.com>

From morgaine.dinova@googlemail.com  Tue Nov 10 14:36:29 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DC223A68BF for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 14:36:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.833
X-Spam-Level: 
X-Spam-Status: No, score=-0.833 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SARE_ADULT2=1.42]
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 Gdn4ng7Up58m for <ogpx@core3.amsl.com>; Tue, 10 Nov 2009 14:36:26 -0800 (PST)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id D2FAA3A68AE for <ogpx@ietf.org>; Tue, 10 Nov 2009 14:36:23 -0800 (PST)
Received: by ewy3 with SMTP id 3so579286ewy.37 for <ogpx@ietf.org>; Tue, 10 Nov 2009 14:36:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=aHzhkccASUYO96guEslKDC/9wvFchHg6C6UKAgSKHhg=; b=XOtN0iYNGtralVnn1hti2WTsCUIbL/ffCynzBWm8RELnf3X7fzqbvvs36Er3LkJ2S9 AeuxbxbMQ8qlzazBIvkH/Uu3VHtX+R+c1LUu8RmmVv3opz/cAdwzcw5vxcNlgCLSYisu PJZVpEk/CRh+NYvOozuUw9DKbQcI4rEXOj1YI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=fDE8tqAywJ3Sam9rD/QO4mYwevEZY7FGZLZPQk/DhtVPbWDvgx3JDuo8RIft0BdZaq imMZEMpFBtC3ZXC5xQbnM6p5afzeuJrAqf/O9h7PGOnYlXWt9+5dE1vdYNzkIgOLimgf SqHhC4SJPV+Tq5z+Txxf6RxxhakvNQOwbYpFM=
MIME-Version: 1.0
Received: by 10.216.85.137 with SMTP id u9mr208503wee.214.1257892605216; Tue,  10 Nov 2009 14:36:45 -0800 (PST)
In-Reply-To: <4AF8ECDE.2010900@cox.net>
References: <e0b04bba0910262215td0cf125lb3129947e8f81891@mail.gmail.com> <f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com> <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com> <4AF8ECDE.2010900@cox.net>
Date: Tue, 10 Nov 2009 22:36:45 +0000
Message-ID: <e0b04bba0911101436ve9855f1u34f6fa229cfea72c@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6db2dcbe6480004780bf195
Subject: Re: [ogpx] Limits to interoperability of scripted objects
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 22:36:29 -0000

--0016e6db2dcbe6480004780bf195
Content-Type: text/plain; charset=ISO-8859-1

+1 Lawson. :-)

I don't want to endorse any single linguistic approach to client-side
scripting, as that would deny the opportunity for progress along many
different language fronts in parallel.  It would also limit the scope for
using the many language-specific development tools available today, and it
would not harness the skills that people have earned with particular
languages and tools.

In my view, the right approach to client-side scripting is to "*provide none
but support all*", through the simple strategy of defining a socket API for
scripts that attach to viewers as regular system processes.  This
automatically provides support for hundreds of languages that have socket
libraries, makes full use of multiple cores with zero effort in
parallelization, and avoids the vast majority of pitfalls associated with
concurrent programming using threads and shared memory.  It delivers a large
number of other benefits as well, too many to describe here.

For more detailed information on this approach, the wiki page at
https://wiki.secondlife.com/wiki/Multi-Process_Client_VAG_--_draft provides
a wealth of considerations for an entire viewer structured around such a
design.

For client-side scripting within existing SL viewers, the language-agnostic
/ scripts-as-processes idea was captured a year ago in a tentative subsystem
design for the third-party Imprudence viewer (derived from LL's GPL
sources).  The overall architecture is illustrated in this diagram --
http://imprudenceviewer.org/w/images/4/48/Plugin_system_flow_APIs.png .
Further details can be found in the threads marked "Plugins" in the
Imprudence Development forum --
http://imprudenceviewer.org/forums/viewforum.php?f=7  .

So how does all this tie in with VWRAP?  The way I think it should be tied
in is by thinking of the client-side "consumer" of the protocol not as an
application, but as an API that can be used by many different types of
application.

Focusing on a "viewer" in traditional SL terms will tend to drive protocol
design towards a non-automated future with poor computational properties, in
much the way that the focus on human-controlled browsers has led to websites
that need to be scraped for data --- a very inferior way of developing
interfaces to systems.

The SL viewer was designed in "the browser way" (the intended consumer is
expected to be a human with all relevant limbs and senses available), as a
result of which there is no clear inner API to which a client-side scripting
engine can be cleanly interfaced, nor is there a clear means of adapting the
endpoint for accessibility, nor for automation.

We can improve on this by thinking of the client end of the protocol as an
LLSD-based API and ensuring that it is full-featured and well supported by
the protocol, rather than as an application as the OGP documents currently
describe it.  Full applications usually have a rather ill-defined feature
set, whereas APIs can be tightly defined and checked for coverage, which
translates immediately into a more understandable design and far more
testable implementations.

I'd like to see a change of emphasis from "viewer application" to "viewer
API" for the above reasons, as a generalization of the software that hosts
the client-side endpoint.  Even more concretely, we should be thinking in
terms of *libraries* as concrete implementations of VWRAP, in exactly the
same way that libomv did when it reverse-engineered the SL legacy protocol.

A self-contained protocol library would be a far cleaner and more
maintainable factoring of the software, compared to dispersing the protocol
implementation into the mysterious depths of a very large monolithic viewer
that is widely acknowledged to be poorly structured and too monolithic.
Adding even more code to the main body of the application just compounds the
current problem.

Unfortunately, "dispersing the protocol implementation into the mysterious
depths of a very large monolithic viewer" is exactly the route currently
being taken for prototyping the protocol.  I believe that choosing that
approach was a mistake on several grounds, not the least of which is that it
provides a very obscure and inflexible platform for testing and modifying
our protocols as they evolve.  Protocol development and testing requires the
opposite of these properties.

I recommend that that decision be reconsidered before more time and effort
is spent in a direction that has limited utility for protocol development.
A protocol library would be far easier to understand, maintain, and
develop.  It would not bloat the main body of viewer code further, it would
be testable with far greater ease by calling it from scripts, and it would
be open to far more eyeballs than the current viewer which represents a
substantial challenge to practically all its developers.


Morgaine.




===========================================

On Tue, Nov 10, 2009 at 4:32 AM, Lawson English <lenglish5@cox.net> wrote:

> Morgaine has seen me hype this many types, but perhaps Joshua and others
> have not not:
>
> http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discussion ...
>
>
> There's many uses for client-side scripting, from custom GUIs to
> manipulation of elements (avatars, objects, etc) going out to the sim
> directly, to manipulating objects client-side only say for use in a
> mechanima play where only the other characters in the play can see what is
> going on. Hybrid situations, as is done with the puppeteering code mentioned
> at the bottom of the page, could delay updating until everything is resolved
> client-side. A collection of avatars could be participating in a private
> play, battle, simulation, whatever, and only use the main simulator to
> provide a backdrop for whatever it is they are doing with or without
> eventually updating the simulator as to their position/actions/etc.
>
> And no doubt there are many other scenarios that we haven't conceived of
> yet where "client side scripting" would be useful. And one extreme is the
> Second Life use-case where the server handles virtually every aspect of the
> avatar except limited user input. At the other end is the Croquet/Cobalt
> case where clients act as servers for their own private worlds that are, in
> principle, P2P in nature. While the VWRAP scenario assumes more Second
> Life-ish scenarios, there's plenty of room for more Croquet-like situations,
>  IMHO. The server(s) need not know what input the client is working with.
> Perhaps there's enhanced physics being used in a special MC Escher style
> world. or perhaps the client is getting a direct feed of planetarium data to
> light up the sky. Both situations exist or are being worked on in a
> rudimentary way in Second Life itself. There's no reason to assume ANY
> limitations save those required for security/trust issues, and those will
> need to be applied on the server side for any realistically secure scenario
> (assuming that the client-side plug-ins are trustworthy for the end-user's
> purposes, of course)
>
>
> Lawson
>
>
>
> Morgaine wrote:
>
>> On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell <josh@lindenlab.com <mailto:
>> josh@lindenlab.com>> wrote:
>>
>>
>>    * Your (3) (common scripting environment) is intriguing. Sun's
>>    Project Wonderland uses Java (obviously...) as the common format,
>>    and (vastly simplifying) all objects in the VW are Java objects.
>>    I'd love to learn more from them about the challenges and
>>    successes. That said, at a protocol level, I don't think we'd ever
>>    dictate a common environment, so going down this road might turn
>>    into a de-facto common case of the content negotiation (just as
>>    the Web technically allows for client-side scripting languages
>>    other than Javascript, although they are used incredibly
>>    infrequently in practice).
>>    * Client-side scripts are also intriguing. If I think about what
>>    this means in practice, it's that the client is able to manipulate
>>    the state of objects in-world. Well, duh - that's what editing and
>>    appearance tools do! So... that capability (pun intended!) is a
>>    requirement at the protocol level, although I don't think we've
>>    even brushed on how to define it yet. It would be intriguing if
>>    the protocol were such that the client could expose a DOM-like
>>    view of the world to local scripts to observe and mutate.
>>
>>
>>  I like both of those ideas.  I wonder if we could support them both in
>> principle with minimal effort by providing a generic hook using script
>> metadata.  Let some attribute select between "region" (for scripts running
>> in the current region as in SL), "avatar" (for HUD scripts that run in-world
>> but don't need region events so they can be run in a separate load-balaced
>> server pool), "home" (for scripts that always run in the agent's home
>> region), and "client" (for client-side scripts or plugins).  Further
>> attributes could specify the language and maybe a startup argument list too.
>>  (These are just random ideas, not cohesive.)
>>
>> Thinking about the scripting languages themselves, presumably nobody would
>> argue in favour of turning LSL into an interop standard given the poverty of
>> its syntax, but even worse is the tortuous and complex semantic of its
>> system calls which would be very problematic to standardize, or maybe
>> impossible.  The SL scripting environment has evolved in a way that isn't
>> conducive to portability, not only because the implementation is closed and
>> quite unique, but also because it's tied fairly strongly to a proprietary
>> physics engine for events/simulation and to a rather esoteric communications
>> model.  These things conspire to make standardising around the SL scripting
>> mechanism very unlikely.  This gives us a solution to cross off the list,
>> but unfortunately doesn't offer us anything in its place.
>>
>> Being realistic, forcing language commonality at this early stage is just
>> not going to happen, so we might as well lubricate the protocol machinery to
>> allow multiple scripting systems to be supported.  Eventually a de-facto
>> standard will emerge as happened with Javascript.  Let people with more
>> spare time than we have sort it out, and may the best idea win. :-)
>>
>> As lubrication, I think we should provide at the very least some generic
>> and extensible metadata hooks in the protocol for this, otherwise the spec
>> will be modified incompatibly outside of the standard to support the diverse
>> scripting requirements of worlds, and then interop suffers.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>> =========================================
>>
>> On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell <josh@lindenlab.com <mailto:
>> josh@lindenlab.com>> wrote:
>>
>>    Good analysis as usual, Morgaine!
>>
>>
>>    On Mon, Oct 26, 2009 at 10:15 PM, Morgaine
>>    <morgaine.dinova@googlemail.com
>>    <mailto:morgaine.dinova@googlemail.com>> wrote:
>>
>>        Being pragmatic about the situation, if we wish to see interop
>>        of scripting in the relatively near future, we need to find an
>>        approach that is inherently interoperable.  Here are some
>>        ideas that might be relevant to this end (these are
>>        alternatives, they don't all apply simultaneously):
>>
>>           1. Make script state transfer a deployment option:  both
>>
>>              source and destination regions have to allow script
>>              state transfer for it to happen.
>>           2. Worlds running different scripting engine
>>
>>              implementations do not transfer state and hence scripts
>>              are initialized on teleport.
>>           3. Define a common scripting language and virtual machine
>>
>>              environment --- ie. a web-like Javascript approach but
>>              for regions.
>>           4. If script state continuity is desired on teleports
>>
>>              between worlds running different script engines, let
>>              such scripts run client-side.
>>
>>
>>    A few thoughts on the above:
>>
>>    * Even though the Web appears to have given up on content
>>    negotiation over HTTP, I'm still a fan and I think cross-system
>>    interop like this is a good place for it. During Region-to-Region
>>    state transfer, you could imagine the destination region
>>    advertising the script state types it accepts
>>    (vendor/com.lindenlab.secondlife.lsl2mono,
>>    vendor/org.opensim.dotnetengine, ...), and the source region
>>    delivering one tagged with appropriate type. I would imagine we'll
>>    need similar logic for static content as well - articles of
>>    clothing could have have "prim" or "mesh" based versions, and
>>    regions may prefer one type to another. (Although it would be more
>>    likely to have both available on the region, and have content
>>    negotiation occur on the region->viewer resource transfer.)
>>
>>    * Given the desire for "tourist" models (using the term loosely -
>>    I "live" on my home grid, but like to visit other grids), it
>>    doesn't seem like there's a one-size-fits-all approach (since
>>    region-to-region teleports in my home grid and region-to-region
>>    teleports between grids utilize the same protocol). So... this is
>>    definitely part of the protocol's mandate to sort out.
>>
>>    * Combining the above two points, it implies that attachments will
>>    have to cope with moving from areas where they have scripts
>>    running to scripts not running (if the code/state is not
>>    compatible with the hosting region). Fortunately, we have
>>    precedent for that. :)
>>
>>    * Infinity and I very briefly hand-waved about whether "portable"
>>    content (primarily, attachments to avatars) should even be
>>    executed within the region domain. Perhaps they should be
>>    executing in the agent domain? That's a radical departure from how
>>    SL or OpenSim work today. (If you squint your eyes and partition
>>    the current services, at least.) - at any rate, today there is no
>>    script execution outside of a region. It's an intriguing idea, but
>>    by no means complete - how such fine grained state might be
>>    updated between domains, for example. Vehicles come to mind as
>>    another case, and those have no clear "home base" for script
>>    execution. I suspect this is not tractable for the first iteration
>>    of VWRAP, but I don't want to dismiss it.
>>
>>    * Your (3) (common scripting environment) is intriguing. Sun's
>>    Project Wonderland uses Java (obviously...) as the common format,
>>    and (vastly simplifying) all objects in the VW are Java objects.
>>    I'd love to learn more from them about the challenges and
>>    successes. That said, at a protocol level, I don't think we'd ever
>>    dictate a common environment, so going down this road might turn
>>    into a de-facto common case of the content negotiation (just as
>>    the Web technically allows for client-side scripting languages
>>    other than Javascript, although they are used incredibly
>>    infrequently in practice).
>>    * Client-side scripts are also intriguing. If I think about what
>>    this means in practice, it's that the client is able to manipulate
>>    the state of objects in-world. Well, duh - that's what editing and
>>    appearance tools do! So... that capability (pun intended!) is a
>>    requirement at the protocol level, although I don't think we've
>>    even brushed on how to define it yet. It would be intriguing if
>>    the protocol were such that the client could expose a DOM-like
>>    view of the world to local scripts to observe and mutate.
>>
>>
>>    _______________________________________________
>>    ogpx mailing list
>>    ogpx@ietf.org <mailto:ogpx@ietf.org>
>>
>>    https://www.ietf.org/mailman/listinfo/ogpx
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>>
>>
>
>

--0016e6db2dcbe6480004780bf195
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1 Lawson. :-)<br><br>I don&#39;t want to endorse any single linguistic app=
roach to client-side scripting, as that would deny the opportunity for prog=
ress along many different language fronts in parallel.=A0 It would also lim=
it the scope for using the many language-specific development tools availab=
le today, and it would not harness the skills that people have earned with =
particular languages and tools.<br>
<br>In my view, the right approach to client-side scripting is to &quot;<b>=
<i>provide none but support all</i></b>&quot;, through the simple strategy =
of defining a socket API for scripts that attach to viewers as regular syst=
em processes.=A0 This automatically provides support for hundreds of langua=
ges that have socket libraries, makes full use of multiple cores with zero =
effort in parallelization, and avoids the vast majority of pitfalls associa=
ted with concurrent programming using threads and shared memory.=A0 It deli=
vers a large number of other benefits as well, too many to describe here.<b=
r>
<br>For more detailed information on this approach, the wiki page at <a hre=
f=3D"https://wiki.secondlife.com/wiki/Multi-Process_Client_VAG_--_draft">ht=
tps://wiki.secondlife.com/wiki/Multi-Process_Client_VAG_--_draft</a> provid=
es a wealth of considerations for an entire viewer structured around such a=
 design.<br>
<br>For client-side scripting within existing SL viewers, the language-agno=
stic / scripts-as-processes idea was captured a year ago in a tentative sub=
system design for the third-party Imprudence viewer (derived from LL&#39;s =
GPL sources).=A0 The overall architecture is illustrated in this diagram --=
=A0 <a href=3D"http://imprudenceviewer.org/w/images/4/48/Plugin_system_flow=
_APIs.png">http://imprudenceviewer.org/w/images/4/48/Plugin_system_flow_API=
s.png</a> .=A0 Further details can be found in the threads marked &quot;Plu=
gins&quot; in the Imprudence Development forum --=A0=A0 <a href=3D"http://i=
mprudenceviewer.org/forums/viewforum.php?f=3D7">http://imprudenceviewer.org=
/forums/viewforum.php?f=3D7</a>=A0 .<br>
<br>So how does all this tie in with VWRAP?=A0 The way I think it should be=
 tied in is by thinking of the client-side &quot;consumer&quot; of the prot=
ocol not as an application, but as an API that can be used by many differen=
t types of application.<br>
<br>Focusing on a &quot;viewer&quot; in traditional SL terms will tend to d=
rive protocol design towards a non-automated future with poor computational=
 properties, in much the way that the focus on human-controlled browsers ha=
s led to websites that need to be scraped for data --- a very inferior way =
of developing interfaces to systems.<br>
<br>The SL viewer was designed in &quot;the browser way&quot; (the intended=
 consumer is expected to be a human with all relevant limbs and senses avai=
lable), as a result of which there is no clear inner API to which a client-=
side scripting engine can be cleanly interfaced, nor is there a clear means=
 of adapting the endpoint for accessibility, nor for automation.<br>
<br>We can improve on this by thinking of the client end of the protocol as=
 an LLSD-based API and ensuring that it is full-featured and well supported=
 by the protocol, rather than as an application as the OGP documents curren=
tly describe it.=A0 Full applications usually have a rather ill-defined fea=
ture set, whereas APIs can be tightly defined and checked for coverage, whi=
ch translates immediately into a more understandable design and far more te=
stable implementations.<br>
<br>I&#39;d like to see a change of emphasis from &quot;viewer application&=
quot; to &quot;viewer API&quot; for the above reasons, as a generalization =
of the software that hosts the client-side endpoint.=A0 Even more concretel=
y, we should be thinking in terms of <b><i>libraries</i></b> as concrete im=
plementations of VWRAP, in exactly the same way that libomv did when it rev=
erse-engineered the SL legacy protocol.<br>
<br>A self-contained protocol library would be a far cleaner and more maint=
ainable factoring of the software, compared to dispersing the protocol impl=
ementation into the mysterious depths of a very large monolithic viewer tha=
t is widely acknowledged to be poorly structured and too monolithic.=A0 Add=
ing even more code to the main body of the application just compounds the c=
urrent problem.<br>
<br>Unfortunately, &quot;dispersing the protocol implementation into the my=
sterious depths of a very large monolithic viewer&quot; is exactly the rout=
e currently being taken for prototyping the protocol.=A0 I believe that cho=
osing that approach was a mistake on several grounds, not the least of whic=
h is that it provides a very obscure and inflexible platform for testing an=
d modifying our protocols as they evolve.=A0 Protocol development and testi=
ng requires the opposite of these properties.<br>
<br>I recommend that that decision be reconsidered before more time and eff=
ort is spent in a direction that has limited utility for protocol developme=
nt.=A0 A protocol library would be far easier to understand, maintain, and =
develop.=A0 It would not bloat the main body of viewer code further, it wou=
ld be testable with far greater ease by calling it from scripts, and it wou=
ld be open to far more eyeballs than the current viewer which represents a =
substantial challenge to practically all its developers.<br>
<br><br>Morgaine.<br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">On Tue, Nov 10, 2009 a=
t 4:32 AM, Lawson English <span dir=3D"ltr">&lt;<a href=3D"mailto:lenglish5=
@cox.net">lenglish5@cox.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Morgaine has seen=
 me hype this many types, but perhaps Joshua and others have not not:<br>
<br>
<a href=3D"http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discu=
ssion" target=3D"_blank">http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn=
/Plugins_discussion</a> ...<br>
<br>
<br>
There&#39;s many uses for client-side scripting, from custom GUIs to manipu=
lation of elements (avatars, objects, etc) going out to the sim directly, t=
o manipulating objects client-side only say for use in a mechanima play whe=
re only the other characters in the play can see what is going on. Hybrid s=
ituations, as is done with the puppeteering code mentioned at the bottom of=
 the page, could delay updating until everything is resolved client-side. A=
 collection of avatars could be participating in a private play, battle, si=
mulation, whatever, and only use the main simulator to provide a backdrop f=
or whatever it is they are doing with or without eventually updating the si=
mulator as to their position/actions/etc.<br>

<br>
And no doubt there are many other scenarios that we haven&#39;t conceived o=
f yet where &quot;client side scripting&quot; would be useful. And one extr=
eme is the Second Life use-case where the server handles virtually every as=
pect of the avatar except limited user input. At the other end is the Croqu=
et/Cobalt case where clients act as servers for their own private worlds th=
at are, in principle, P2P in nature. While the VWRAP scenario assumes more =
Second Life-ish scenarios, there&#39;s plenty of room for more Croquet-like=
 situations, =A0IMHO. The server(s) need not know what input the client is =
working with. Perhaps there&#39;s enhanced physics being used in a special =
MC Escher style world. or perhaps the client is getting a direct feed of pl=
anetarium data to light up the sky. Both situations exist or are being work=
ed on in a rudimentary way in Second Life itself. There&#39;s no reason to =
assume ANY limitations save those required for security/trust issues, and t=
hose will need to be applied on the server side for any realistically secur=
e scenario (assuming that the client-side plug-ins are trustworthy for the =
end-user&#39;s purposes, of course)<br>

<br>
<br>
Lawson<br>
<br>
<br>
<br>
Morgaine wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class=3D"im"=
>
On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell &lt;<a href=3D"mailto:josh@lin=
denlab.com" target=3D"_blank">josh@lindenlab.com</a> &lt;mailto:<a href=3D"=
mailto:josh@lindenlab.com" target=3D"_blank">josh@lindenlab.com</a>&gt;&gt;=
 wrote:<br>

<br>
<br>
 =A0 =A0* Your (3) (common scripting environment) is intriguing. Sun&#39;s<=
br>
 =A0 =A0Project Wonderland uses Java (obviously...) as the common format,<b=
r>
 =A0 =A0and (vastly simplifying) all objects in the VW are Java objects.<br=
>
 =A0 =A0I&#39;d love to learn more from them about the challenges and<br>
 =A0 =A0successes. That said, at a protocol level, I don&#39;t think we&#39=
;d ever<br>
 =A0 =A0dictate a common environment, so going down this road might turn<br=
>
 =A0 =A0into a de-facto common case of the content negotiation (just as<br>
 =A0 =A0the Web technically allows for client-side scripting languages<br>
 =A0 =A0other than Javascript, although they are used incredibly<br>
 =A0 =A0infrequently in practice). <br>
 =A0 =A0* Client-side scripts are also intriguing. If I think about what<br=
>
 =A0 =A0this means in practice, it&#39;s that the client is able to manipul=
ate<br>
 =A0 =A0the state of objects in-world. Well, duh - that&#39;s what editing =
and<br>
 =A0 =A0appearance tools do! So... that capability (pun intended!) is a<br>
 =A0 =A0requirement at the protocol level, although I don&#39;t think we&#3=
9;ve<br>
 =A0 =A0even brushed on how to define it yet. It would be intriguing if<br>
 =A0 =A0the protocol were such that the client could expose a DOM-like<br>
 =A0 =A0view of the world to local scripts to observe and mutate.<br>
<br>
<br>
=A0I like both of those ideas. =A0I wonder if we could support them both in=
 principle with minimal effort by providing a generic hook using script met=
adata. =A0Let some attribute select between &quot;region&quot; (for scripts=
 running in the current region as in SL), &quot;avatar&quot; (for HUD scrip=
ts that run in-world but don&#39;t need region events so they can be run in=
 a separate load-balaced server pool), &quot;home&quot; (for scripts that a=
lways run in the agent&#39;s home region), and &quot;client&quot; (for clie=
nt-side scripts or plugins). =A0Further attributes could specify the langua=
ge and maybe a startup argument list too. =A0(These are just random ideas, =
not cohesive.)<br>

<br>
Thinking about the scripting languages themselves, presumably nobody would =
argue in favour of turning LSL into an interop standard given the poverty o=
f its syntax, but even worse is the tortuous and complex semantic of its sy=
stem calls which would be very problematic to standardize, or maybe impossi=
ble. =A0The SL scripting environment has evolved in a way that isn&#39;t co=
nducive to portability, not only because the implementation is closed and q=
uite unique, but also because it&#39;s tied fairly strongly to a proprietar=
y physics engine for events/simulation and to a rather esoteric communicati=
ons model. =A0These things conspire to make standardising around the SL scr=
ipting mechanism very unlikely. =A0This gives us a solution to cross off th=
e list, but unfortunately doesn&#39;t offer us anything in its place.<br>

<br>
Being realistic, forcing language commonality at this early stage is just n=
ot going to happen, so we might as well lubricate the protocol machinery to=
 allow multiple scripting systems to be supported. =A0Eventually a de-facto=
 standard will emerge as happened with Javascript. =A0Let people with more =
spare time than we have sort it out, and may the best idea win. :-)<br>

<br>
As lubrication, I think we should provide at the very least some generic an=
d extensible metadata hooks in the protocol for this, otherwise the spec wi=
ll be modified incompatibly outside of the standard to support the diverse =
scripting requirements of worlds, and then interop suffers.<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br></div><div class=3D"im">
On Tue, Oct 27, 2009 at 4:51 PM, Joshua Bell &lt;<a href=3D"mailto:josh@lin=
denlab.com" target=3D"_blank">josh@lindenlab.com</a> &lt;mailto:<a href=3D"=
mailto:josh@lindenlab.com" target=3D"_blank">josh@lindenlab.com</a>&gt;&gt;=
 wrote:<br>

<br>
 =A0 =A0Good analysis as usual, Morgaine!<br>
<br>
<br>
 =A0 =A0On Mon, Oct 26, 2009 at 10:15 PM, Morgaine<br>
 =A0 =A0&lt;<a href=3D"mailto:morgaine.dinova@googlemail.com" target=3D"_bl=
ank">morgaine.dinova@googlemail.com</a><br></div><div class=3D"im">
 =A0 =A0&lt;mailto:<a href=3D"mailto:morgaine.dinova@googlemail.com" target=
=3D"_blank">morgaine.dinova@googlemail.com</a>&gt;&gt; wrote:<br>
<br>
 =A0 =A0 =A0 =A0Being pragmatic about the situation, if we wish to see inte=
rop<br>
 =A0 =A0 =A0 =A0of scripting in the relatively near future, we need to find=
 an<br>
 =A0 =A0 =A0 =A0approach that is inherently interoperable. =A0Here are some=
<br>
 =A0 =A0 =A0 =A0ideas that might be relevant to this end (these are<br>
 =A0 =A0 =A0 =A0alternatives, they don&#39;t all apply simultaneously):<br>
<br></div>
 =A0 =A0 =A0 =A0 =A0 1. Make script state transfer a deployment option: =A0=
both<div class=3D"im"><br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0source and destination regions have to allow sc=
ript<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0state transfer for it to happen.<br></div>
 =A0 =A0 =A0 =A0 =A0 2. Worlds running different scripting engine<div class=
=3D"im"><br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0implementations do not transfer state and hence=
 scripts<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0are initialized on teleport.<br></div>
 =A0 =A0 =A0 =A0 =A0 3. Define a common scripting language and virtual mach=
ine<div class=3D"im"><br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0environment --- ie. a web-like Javascript appro=
ach but<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0for regions.<br></div>
 =A0 =A0 =A0 =A0 =A0 4. If script state continuity is desired on teleports<=
div><div></div><div class=3D"h5"><br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0between worlds running different script engines=
, let<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0such scripts run client-side.<br>
<br>
<br>
 =A0 =A0A few thoughts on the above:<br>
<br>
 =A0 =A0* Even though the Web appears to have given up on content<br>
 =A0 =A0negotiation over HTTP, I&#39;m still a fan and I think cross-system=
<br>
 =A0 =A0interop like this is a good place for it. During Region-to-Region<b=
r>
 =A0 =A0state transfer, you could imagine the destination region<br>
 =A0 =A0advertising the script state types it accepts<br>
 =A0 =A0(vendor/com.lindenlab.secondlife.lsl2mono,<br>
 =A0 =A0vendor/org.opensim.dotnetengine, ...), and the source region<br>
 =A0 =A0delivering one tagged with appropriate type. I would imagine we&#39=
;ll<br>
 =A0 =A0need similar logic for static content as well - articles of<br>
 =A0 =A0clothing could have have &quot;prim&quot; or &quot;mesh&quot; based=
 versions, and<br>
 =A0 =A0regions may prefer one type to another. (Although it would be more<=
br>
 =A0 =A0likely to have both available on the region, and have content<br>
 =A0 =A0negotiation occur on the region-&gt;viewer resource transfer.)<br>
<br>
 =A0 =A0* Given the desire for &quot;tourist&quot; models (using the term l=
oosely -<br>
 =A0 =A0I &quot;live&quot; on my home grid, but like to visit other grids),=
 it<br>
 =A0 =A0doesn&#39;t seem like there&#39;s a one-size-fits-all approach (sin=
ce<br>
 =A0 =A0region-to-region teleports in my home grid and region-to-region<br>
 =A0 =A0teleports between grids utilize the same protocol). So... this is<b=
r>
 =A0 =A0definitely part of the protocol&#39;s mandate to sort out.<br>
<br>
 =A0 =A0* Combining the above two points, it implies that attachments will<=
br>
 =A0 =A0have to cope with moving from areas where they have scripts<br>
 =A0 =A0running to scripts not running (if the code/state is not<br>
 =A0 =A0compatible with the hosting region). Fortunately, we have<br>
 =A0 =A0precedent for that. :)<br>
<br>
 =A0 =A0* Infinity and I very briefly hand-waved about whether &quot;portab=
le&quot;<br>
 =A0 =A0content (primarily, attachments to avatars) should even be<br>
 =A0 =A0executed within the region domain. Perhaps they should be<br>
 =A0 =A0executing in the agent domain? That&#39;s a radical departure from =
how<br>
 =A0 =A0SL or OpenSim work today. (If you squint your eyes and partition<br=
>
 =A0 =A0the current services, at least.) - at any rate, today there is no<b=
r>
 =A0 =A0script execution outside of a region. It&#39;s an intriguing idea, =
but<br>
 =A0 =A0by no means complete - how such fine grained state might be<br>
 =A0 =A0updated between domains, for example. Vehicles come to mind as<br>
 =A0 =A0another case, and those have no clear &quot;home base&quot; for scr=
ipt<br>
 =A0 =A0execution. I suspect this is not tractable for the first iteration<=
br>
 =A0 =A0of VWRAP, but I don&#39;t want to dismiss it.<br>
<br>
 =A0 =A0* Your (3) (common scripting environment) is intriguing. Sun&#39;s<=
br>
 =A0 =A0Project Wonderland uses Java (obviously...) as the common format,<b=
r>
 =A0 =A0and (vastly simplifying) all objects in the VW are Java objects.<br=
>
 =A0 =A0I&#39;d love to learn more from them about the challenges and<br>
 =A0 =A0successes. That said, at a protocol level, I don&#39;t think we&#39=
;d ever<br>
 =A0 =A0dictate a common environment, so going down this road might turn<br=
>
 =A0 =A0into a de-facto common case of the content negotiation (just as<br>
 =A0 =A0the Web technically allows for client-side scripting languages<br>
 =A0 =A0other than Javascript, although they are used incredibly<br>
 =A0 =A0infrequently in practice). <br>
 =A0 =A0* Client-side scripts are also intriguing. If I think about what<br=
>
 =A0 =A0this means in practice, it&#39;s that the client is able to manipul=
ate<br>
 =A0 =A0the state of objects in-world. Well, duh - that&#39;s what editing =
and<br>
 =A0 =A0appearance tools do! So... that capability (pun intended!) is a<br>
 =A0 =A0requirement at the protocol level, although I don&#39;t think we&#3=
9;ve<br>
 =A0 =A0even brushed on how to define it yet. It would be intriguing if<br>
 =A0 =A0the protocol were such that the client could expose a DOM-like<br>
 =A0 =A0view of the world to local scripts to observe and mutate.<br>
<br>
<br>
 =A0 =A0_______________________________________________<br>
 =A0 =A0ogpx mailing list<br></div></div>
 =A0 =A0<a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a=
> &lt;mailto:<a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.o=
rg</a>&gt;<div class=3D"im"><br>
 =A0 =A0<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
<br>
<br></div>
------------------------------------------------------------------------<di=
v class=3D"im"><br>
<br>
_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
 =A0<br>
</div></blockquote>
<br>
</blockquote></div><br>

--0016e6db2dcbe6480004780bf195--

From carlo@alinoe.com  Wed Nov 11 02:13:12 2009
Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C474B3A6A80 for <ogpx@core3.amsl.com>; Wed, 11 Nov 2009 02:13:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.765
X-Spam-Level: 
X-Spam-Status: No, score=0.765 tagged_above=-999 required=5 tests=[AWL=-0.219,  BAYES_40=-0.185, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 BTeL6k0jjkCb for <ogpx@core3.amsl.com>; Wed, 11 Nov 2009 02:13:09 -0800 (PST)
Received: from viefep15-int.chello.at (viefep15-int.chello.at [62.179.121.35]) by core3.amsl.com (Postfix) with ESMTP id 020453A6A69 for <ogpx@ietf.org>; Wed, 11 Nov 2009 02:13:08 -0800 (PST)
Received: from edge04.upc.biz ([192.168.13.239]) by viefep15-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20091111101334.FVKL8249.viefep15-int.chello.at@edge04.upc.biz> for <ogpx@ietf.org>; Wed, 11 Nov 2009 11:13:34 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge04.upc.biz with edge id 3mDW1d0140FlQed04mDXdn; Wed, 11 Nov 2009 11:13:34 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1N8ABU-00018L-Un for ogpx@ietf.org; Wed, 11 Nov 2009 11:12:17 +0100
Date: Wed, 11 Nov 2009 11:12:16 +0100
From: Carlo Wood <carlo@alinoe.com>
To: ogpx@ietf.org
Message-ID: <20091111101216.GB5757@alinoe.com>
References: <e0b04bba0910262215td0cf125lb3129947e8f81891@mail.gmail.com> <f72742de0910270951x6b4536d8wef165e850ba16ef8@mail.gmail.com> <e0b04bba0911091956j5edc4840pd5a32d98eff3776e@mail.gmail.com> <4AF8ECDE.2010900@cox.net> <f72742de0911100919r76c337b6i980736db91f7f53c@mail.gmail.com> <20091110201157.GA10861@alinoe.com> <20091110204155.GA5757@alinoe.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091110204155.GA5757@alinoe.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [ogpx] Synchronization of gestures (was: Limits to interoperability of scripted objects)
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2009 10:13:13 -0000

My previous post was a brainstorm, and I made a view mistakes in it.
Let me try again.

Looking just at animations and sounds, we can observe that it
is impossible to deny playing a sound, and it is only possible
to deny playing an animation for ones own avatar. Nevertheless,
more in general one could think of world-manipulations, visible
to others, and requested by others, that require permissions,
the whole set of permissions can than be seen as a bit mask,
but is at the moment of no further interest. Hence, lets
concentrate for the sake of simplicity on animations.

The simplest case would be a scene with three avatars (agents,
whatever) A, B and C, where A proposes to animate B (to B)
and C is just an observer.

In the ideal situation without much lag, the protocol should
look something like this (were B/xyz and C could be a list of
agents/animations):

[A preloads animations (etc)]
A --request animation xyz of B--> simulator
simulator --A requests animation xyz --> B
[B starts preloading animations (etc)]
simulator --A requests animation xyz of B --> C
[C starts preloading animations (etc)]
B --OK--> simulator
simulator --Ready?--> A,B,C
A --Ready--> simulator
B --Ready--> simulator
C --Ready--> simulator
simulator --GO--> A,B,C
[all viewers play the animations for all avatars]


HOWEVER...

It seems better to seperate this "voting / handshaking" from whatever
is the action. If we assume an API, as morgaine proposed, that gives
us complete control over the world, then a logical step would be
to have a viewer-local scripting language that manipulates this
world (albeit locally, in this case). A given script provided by
another agent would fail if it would attempt to do something for
which it had no permission; so it should be known what permissions
a script needs before running it.

The above then can be done by replacing "animation(s)" with "running
a script". In the above case, the script would only need the
permission "animate your avatar for animation xyz".

The above then turns into:

[A preloads animation (etc)]
A         --requests to run script on B,
            needing permission "animate B with xyz"-->  simulator
simulator --A requests to run script,
            needing permissions "animate B with xyz"--> B
[B starts preloading animation (etc)]
simulator --preload animation xyz-->                    C
[C starts preloading animation (etc)]
B         --OK-->                                       simulator
simulator --script-->                                   B
simulator --Ready?-->                                   A,B,C
A         --Ready-->                                    simulator
B         --Ready-->                                    simulator
C         --Ready-->                                    simulator
simulator --GO-->                                       A,B,C
[all viewers run the script]


Now, although EVERYTHING can be implemented from here on with
"running client-side scripts" (possibly predefined, permanently
cached scripts), I'd personally add one more step to seperate
the 'voting' mechanism from 'running a script'.

I think the most general support would be to first define
that some handle means "play script needing those permissions",
and then run the voting protocol, including it's timeout
and permission-denied policies, using that handle; in that
case the voting would look like:


* Define what we vote on, and what are the timeout/permission-denied
  policies, and obtain voting-handle

* Handle preloading (tell everyone that they might need these assets).

* Ask for permissions
* Wait for permissions and/or timeouts

* Inform viewers of result about voting-handle

* Wait for preload-ready signals
* Inform viewers that everyone is ready and we have a 'go'.

* All viewers do as agreed, resulting a mutally synchronized
  experience.

On Tue, Nov 10, 2009 at 09:41:55PM +0100, Carlo Wood wrote:
> * Viewer A (or object) initiates Multi-gesture Request
>   to N (other) viewers, this involves a list of the
>   animations (UUID) to play for each of the avatars
>   involved, and sounds to play etc, and the starting
>   position in the world of each avatar.
> * Each viewer reacts with: Ok, will try; or Nope, I won't.
>   If any viewer denies the request (or times out?)
>   then the server informs all viewers that the multi-
>   animation was aborted (and why). [ An optional flag
>   could be to continue anyway, but without the avatar(s)
>   that don't want to. ]
> * Once all avatars that want to play the multi-animation
>   are known, the server sends them a message: "We have a go!"
> * All viewers that have all the needed information to
>   continue (downloaded and cached the animations, sounds etc)
>   send a message to the server: "ready!"
> * As soon as all viewers are ready (optionally, a parameter
>   of the original request includes a timeout after which
>   the delayed avatar is considered to have said "no"),
>   the server informs all viewers to start playing the
>   multi-gesture.
> 
> And YAY! finally a completely synchronized couple (and
> multi) animation, even synced with sound!
> 
> Options in case of delays (timeouts) should be:
> - Play as soon data available locally,
> - Wait till at least N, or at least those, avatars
>   are ready.
> - Abort completely if any can't play in time.
> - If someone is delayed and the rest already plays
>   the animation, then the viewer can decide to abort
>   or play the animations locally anyway, as soon as
>   they become avaiable, etc etc... All those possibilities
>   are mere bits in already existing messages, so why not.
> 
> As a side effect of this it should be possible to
> play a gesture involving animation and sound by ONE
> avatar (as are the gestures in SL now) but *synchronized*:
> everyone sees it at the same time, and the animations ARE
> synced with the sound once the start to play (unlike now,
> where the animation is played and 30 seconds later you
> hear the sound).

-- 
Carlo Wood <carlo@alinoe.com>

From vaughn.deluca@gmail.com  Sun Nov 29 05:42:53 2009
Return-Path: <vaughn.deluca@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4BEC3A672F for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 05:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 LU3r1LpWDWsw for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 05:42:53 -0800 (PST)
Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by core3.amsl.com (Postfix) with ESMTP id C6F953A66B4 for <ogpx@ietf.org>; Sun, 29 Nov 2009 05:42:52 -0800 (PST)
Received: by bwz23 with SMTP id 23so2030862bwz.29 for <ogpx@ietf.org>; Sun, 29 Nov 2009 05:42:41 -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=xSfF8j9Gc1qzLn2KyKrhnuV4b599X5VmzKu/G1ND6yo=; b=iSp8IbZQy5GkxSMJjILUY+r8r+llNnoDn5TYRL3bSaoKv0TBOejKuflm6j8a9aQUPU ni1aILHp/Vy/CBWF3Qd8+jpxspHBojK7g1QZnmpPAUHZzniq+uslnBALiZB9Pe2MLUdJ tRBxGUDKoaAodfK9EuuORzoE06cWGsFd+LSsc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=X+QcfjRCw3PfErm0CLbFzEEMPO4vpLXgL6jJkkKeRAmaltL0w0sktQcjm6ZRlJULo8 ZLdm1oWRSK70qZJG8vU+zNx+aPgu5rUV4p1Ro3/ihXvAWsYpPcmAZbXqC5C+wy8E9b8G lJ4ylLLGt7AC9bj/r4XLqLsmHdUUn3MD6fVH0=
MIME-Version: 1.0
Received: by 10.204.29.15 with SMTP id o15mr3244268bkc.145.1259502161260; Sun,  29 Nov 2009 05:42:41 -0800 (PST)
Date: Sun, 29 Nov 2009 14:42:41 +0100
Message-ID: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com>
From: Vaughn Deluca <vaughn.deluca@gmail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0003255553aeea70fc047982b2b5
Subject: [ogpx]  VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 13:42:53 -0000

--0003255553aeea70fc047982b2b5
Content-Type: text/plain; charset=ISO-8859-1

It has gotten terribly silent on the list, and its not hard to see why;
without updates of the drafts the discussion floats free and people are
bound to loose interest.

I  do understand that drafting these types of documents takes time, and too
much discussion in an early stage sometimes only complicates matters, yet, a
quick status update and maybe even a working version of the drafts in their
current form would be nice to keep everybody synchronised...

-Vaughn

--0003255553aeea70fc047982b2b5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It has gotten terribly silent on the list, and its not hard to see why; wit=
hout updates of the drafts the discussion floats free and people are bound =
to loose interest.=A0<div><br></div><div>I =A0do understand that drafting t=
hese types of documents takes time, and too much discussion in an early sta=
ge sometimes only complicates matters, yet, a quick status update and maybe=
 even a working version of the drafts in their current form would be nice t=
o keep everybody synchronised...</div>
<div><div><br></div><div>-Vaughn</div></div>

--0003255553aeea70fc047982b2b5--

From meadhbh.siobhan@gmail.com  Sun Nov 29 06:32:01 2009
Return-Path: <meadhbh.siobhan@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6184B3A68C5 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 06:32:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Tqb20uJrmHHU for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 06:32:00 -0800 (PST)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id 697643A67B8 for <ogpx@ietf.org>; Sun, 29 Nov 2009 06:32:00 -0800 (PST)
Received: by pwi6 with SMTP id 6so1784797pwi.29 for <ogpx@ietf.org>; Sun, 29 Nov 2009 06:31:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4LmZC0bilYr0xyo4Gg1L4snW4+AHOow8BkcrSHgDffw=; b=AlFXHzMiAfoG8QFTYXNzTUdpz+GAJXiElTL2R8yLL2tTw8mkuKAVNpHrZXhcx45xN0 cqmUBuA4rGH3qjXQVdrjOHUOBSRLRf0fF8bR/cp9EgAwWWdbZemvCsNOnXXVdJGYzuSC zUQ2/7sAoGpMNK3U0gMWYjWTW6HLq/rPbn/VE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GG9q+vCMkBo2RiJ4D6Yha1SkTMA9MtA+aJT7+SX4KMGV9N0Z3rNzWnP2jvmzg+PrYS I0wLhdyAq+qg7vMZrEiO9JpUGPSUuykXSmkRGIOPGTC3P379FNhUD1YCVhOa3sI9CKDU 6fMCZjNoYWzyO7wdIvcE2To/nklRr5F31HBeg=
MIME-Version: 1.0
Received: by 10.114.8.5 with SMTP id 5mr4910788wah.117.1259505110227; Sun, 29  Nov 2009 06:31:50 -0800 (PST)
In-Reply-To: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com>
Date: Sun, 29 Nov 2009 06:31:50 -0800
Message-ID: <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>
From: Meadhbh Hamrick <meadhbh.siobhan@gmail.com>
To: Vaughn Deluca <vaughn.deluca@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 14:32:01 -0000

yes, VWRAP _is_ still alive.

we're currently working on three documents: LLSD / LLIDL, Intro and
Requirements, and Assets

* LLSD / LLIDL

LLIDL was in the middle of getting a well deserved face lift when
multiple, conflicting changes forced us to return to agreeing on the
problem definition instead of pushing out a draft. LLIDL / LLSD draft
development has been being informed by several pairwise / intense
descussions involving investigation of specific use cases. i hope to
get a wiki page up describing proposed changes at the end of this
week.

but essentially what we're looking at is thus:

- peeps didn't grok why LLSD has the "you get the default value when
you read a map key that's not there" semantics, so i'm integrating the
"structure and interpretation of LLSD messages" email into the draft
as motivation for why LLSD is needed. (
http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )

- peeps thought the LLIDL syntax was odd, that it didn't look "Cish
enough." i'm developing a proposal for making LLIDL look more like an
ALGOL derived language so C/C++/C#/Java programmers can look at it and
have a more immediate understanding of what it's doing.

- we want to be able to support GETs as well as POSTs when LLSD is
carried over HTTP(S). this is so we an make use of intermediaries like
caching squid servers. so we're working on a way to map a resource
definition to a GET instead of a POST. i know there are some people
who want to carry LLSD over XMPP, so we're interested in avoiding
simply saying... "oh... just make this kind of message a GET" since
that's more of a HTTP(S) specific construction.

- related to the item above, we're looking at ways to encode a request
as a query string. the idea here being that since some caching
intermediaries can cache two GET requests with the same URL, including
the query string, we want to be able to encode the request in the
query string to take advantage of the caching behavior.

- some people thought that the variant syntax was confusing.
specifically, the relationship  between a variant record and the
selector. (the selector is the element _in_ the variant map
declaration that has a literal value.) in other words, the way the
LLIDL parser knows that a particular variant is "valid" is that one of
the members of the map has a specific value. the relationship to the
variant and the selector was considered "haphazard" by some reviewers.

- explaining the use of "late keys." i.e. - the '$' in some LLIDL
definitions. the use of the dollar sign ('$') in LLIDL as the key of a
map declaration indicates that there'll be a number of keys, the
symbol for each is determined at message send time, not at resource
definition time.

- fixing things like broken XML DTDs.

- changing the comment character from a semi-colon (';') to a hash mark ('#=
')

* Intro and Goals

There was a lot of commentary on the original "intro and requirements"
doc in Stockholm, and a trickle of interest since then. There are a
few minor changes to the draft, and the inclusion of a much better
glossary. David is writing a section on deployment patterns, and we
plan to integrate our changes "any day now."

* Assets

The Assets draft is in a much more "complicated" state. We're
coordinating our efforts with John Hurliman who's the lead developer
on the Cable Beach project. We hope that what will emerge will be a
unified protocol for accessing second life resources as cable beach
resources.

-cheers
-meadhbh

On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.com> wr=
ote:
> It has gotten terribly silent on the list, and its not hard to see why;
> without updates of the drafts the discussion floats free and people are
> bound to loose interest.
> I =A0do understand that drafting these types of documents takes time, and=
 too
> much discussion in an early stage sometimes only complicates matters, yet=
, a
> quick status update and maybe even a working version of the drafts in the=
ir
> current form would be nice to keep everybody synchronised...
> -Vaughn
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>

From morgaine.dinova@googlemail.com  Sun Nov 29 08:30:16 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69C293A681B for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 08:30:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 iEwZFvI0hK3L for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 08:30:15 -0800 (PST)
Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com [209.85.219.215]) by core3.amsl.com (Postfix) with ESMTP id 686BA3A6946 for <ogpx@ietf.org>; Sun, 29 Nov 2009 08:30:14 -0800 (PST)
Received: by ewy7 with SMTP id 7so3554389ewy.28 for <ogpx@ietf.org>; Sun, 29 Nov 2009 08:30:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=K9emx6IdBkU/9rd8cLPSUISoQwojiE6GBDwYz+vbTeY=; b=VGQw7ccJ+al0OFHfhQMxt9zSPar9C40NW8CA2EGOGp9A72skq84WuyIPPxN5Y0TW+D 7qMH7GPrFKK1GXXFDjT7742K9Xe9Y+hscvFugU1VTxi2mdu5OprJ/VrqNdLNxhLBFdkC Yze4lluiHczsD9lNfAICtx5lbz+nyK6rbBpoQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Y6SYzZbqGYn0MqXFDA4jgOg6UBq/oYacI5KJdC2bg5k5Jaozfozq+xaCnRUzvFi4OB FeqhwYPXK5oQ4RRG8c/rj2wLKP02WjknvWycFp4kMNY7KRN2cvyUBWc+c8HeWkRijeFw bEV8zymOAmQwUGnFIkOC7leyieG+6TqZ5u6Yo=
MIME-Version: 1.0
Received: by 10.216.93.2 with SMTP id k2mr1108467wef.210.1259512203539; Sun,  29 Nov 2009 08:30:03 -0800 (PST)
In-Reply-To: <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>
Date: Sun, 29 Nov 2009 16:30:03 +0000
Message-ID: <e0b04bba0911290830m16afb4e3r6f386c8d02f089f0@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: Meadhbh Hamrick <meadhbh.siobhan@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6d7e3257b74d504798509a8
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 16:30:16 -0000

--0016e6d7e3257b74d504798509a8
Content-Type: text/plain; charset=ISO-8859-1

Might I suggest that, instead of working on several documents behind closed
doors, that instead those documents be worked on *one at a time* right here
*in the VWRAP list* where that effort belongs?

That was how we managed to arrive at a group charter in a timely fashion, by
focusing on one thing at a time so that the whole group could contribute
meaningfully to a linear discussion.  The documents are not independent of
each other, so writing a pile of them simultaneously just creates inertia in
the process of change and promotes a desire for rubber-stamping, which isn't
going to happen.

The Intro document req



On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick
<meadhbh.siobhan@gmail.com>wrote:

> yes, VWRAP _is_ still alive.
>
> we're currently working on three documents: LLSD / LLIDL, Intro and
> Requirements, and Assets
>
> * LLSD / LLIDL
>
> LLIDL was in the middle of getting a well deserved face lift when
> multiple, conflicting changes forced us to return to agreeing on the
> problem definition instead of pushing out a draft. LLIDL / LLSD draft
> development has been being informed by several pairwise / intense
> descussions involving investigation of specific use cases. i hope to
> get a wiki page up describing proposed changes at the end of this
> week.
>
> but essentially what we're looking at is thus:
>
> - peeps didn't grok why LLSD has the "you get the default value when
> you read a map key that's not there" semantics, so i'm integrating the
> "structure and interpretation of LLSD messages" email into the draft
> as motivation for why LLSD is needed. (
> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
>
> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
> enough." i'm developing a proposal for making LLIDL look more like an
> ALGOL derived language so C/C++/C#/Java programmers can look at it and
> have a more immediate understanding of what it's doing.
>
> - we want to be able to support GETs as well as POSTs when LLSD is
> carried over HTTP(S). this is so we an make use of intermediaries like
> caching squid servers. so we're working on a way to map a resource
> definition to a GET instead of a POST. i know there are some people
> who want to carry LLSD over XMPP, so we're interested in avoiding
> simply saying... "oh... just make this kind of message a GET" since
> that's more of a HTTP(S) specific construction.
>
> - related to the item above, we're looking at ways to encode a request
> as a query string. the idea here being that since some caching
> intermediaries can cache two GET requests with the same URL, including
> the query string, we want to be able to encode the request in the
> query string to take advantage of the caching behavior.
>
> - some people thought that the variant syntax was confusing.
> specifically, the relationship  between a variant record and the
> selector. (the selector is the element _in_ the variant map
> declaration that has a literal value.) in other words, the way the
> LLIDL parser knows that a particular variant is "valid" is that one of
> the members of the map has a specific value. the relationship to the
> variant and the selector was considered "haphazard" by some reviewers.
>
> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
> map declaration indicates that there'll be a number of keys, the
> symbol for each is determined at message send time, not at resource
> definition time.
>
> - fixing things like broken XML DTDs.
>
> - changing the comment character from a semi-colon (';') to a hash mark
> ('#')
>
> * Intro and Goals
>
> There was a lot of commentary on the original "intro and requirements"
> doc in Stockholm, and a trickle of interest since then. There are a
> few minor changes to the draft, and the inclusion of a much better
> glossary. David is writing a section on deployment patterns, and we
> plan to integrate our changes "any day now."
>
> * Assets
>
> The Assets draft is in a much more "complicated" state. We're
> coordinating our efforts with John Hurliman who's the lead developer
> on the Cable Beach project. We hope that what will emerge will be a
> unified protocol for accessing second life resources as cable beach
> resources.
>
> -cheers
> -meadhbh
>
> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.com>
> wrote:
> > It has gotten terribly silent on the list, and its not hard to see why;
> > without updates of the drafts the discussion floats free and people are
> > bound to loose interest.
> > I  do understand that drafting these types of documents takes time, and
> too
> > much discussion in an early stage sometimes only complicates matters,
> yet, a
> > quick status update and maybe even a working version of the drafts in
> their
> > current form would be nice to keep everybody synchronised...
> > -Vaughn
> > _______________________________________________
> > ogpx mailing list
> > ogpx@ietf.org
> > https://www.ietf.org/mailman/listinfo/ogpx
> >
> >
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>

--0016e6d7e3257b74d504798509a8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Might I suggest that, instead of working on several documents behind closed=
 doors, that instead those documents be worked on <i><b>one at a time</b></=
i> right here <i><b>in the VWRAP list</b></i> where that effort belongs?<br=
>
<br>That was how we managed to arrive at a group charter in a timely fashio=
n, by focusing on one thing at a time so that the whole group could contrib=
ute meaningfully to a linear discussion.=A0 The documents are not independe=
nt of each other, so writing a pile of them simultaneously just creates ine=
rtia in the process of change and promotes a desire for rubber-stamping, wh=
ich isn&#39;t going to happen.<br>
<br>The Intro document req<br><br><br><br><div class=3D"gmail_quote">On Sun=
, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <span dir=3D"ltr">&lt;<a href=3D=
"mailto:meadhbh.siobhan@gmail.com">meadhbh.siobhan@gmail.com</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">yes, VWRAP _is_ s=
till alive.<br>
<br>
we&#39;re currently working on three documents: LLSD / LLIDL, Intro and<br>
Requirements, and Assets<br>
<br>
* LLSD / LLIDL<br>
<br>
LLIDL was in the middle of getting a well deserved face lift when<br>
multiple, conflicting changes forced us to return to agreeing on the<br>
problem definition instead of pushing out a draft. LLIDL / LLSD draft<br>
development has been being informed by several pairwise / intense<br>
descussions involving investigation of specific use cases. i hope to<br>
get a wiki page up describing proposed changes at the end of this<br>
week.<br>
<br>
but essentially what we&#39;re looking at is thus:<br>
<br>
- peeps didn&#39;t grok why LLSD has the &quot;you get the default value wh=
en<br>
you read a map key that&#39;s not there&quot; semantics, so i&#39;m integra=
ting the<br>
&quot;structure and interpretation of LLSD messages&quot; email into the dr=
aft<br>
as motivation for why LLSD is needed. (<br>
<a href=3D"http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html"=
 target=3D"_blank">http://www.ietf.org/mail-archive/web/mmox/current/msg006=
79.html</a> )<br>
<br>
- peeps thought the LLIDL syntax was odd, that it didn&#39;t look &quot;Cis=
h<br>
enough.&quot; i&#39;m developing a proposal for making LLIDL look more like=
 an<br>
ALGOL derived language so C/C++/C#/Java programmers can look at it and<br>
have a more immediate understanding of what it&#39;s doing.<br>
<br>
- we want to be able to support GETs as well as POSTs when LLSD is<br>
carried over HTTP(S). this is so we an make use of intermediaries like<br>
caching squid servers. so we&#39;re working on a way to map a resource<br>
definition to a GET instead of a POST. i know there are some people<br>
who want to carry LLSD over XMPP, so we&#39;re interested in avoiding<br>
simply saying... &quot;oh... just make this kind of message a GET&quot; sin=
ce<br>
that&#39;s more of a HTTP(S) specific construction.<br>
<br>
- related to the item above, we&#39;re looking at ways to encode a request<=
br>
as a query string. the idea here being that since some caching<br>
intermediaries can cache two GET requests with the same URL, including<br>
the query string, we want to be able to encode the request in the<br>
query string to take advantage of the caching behavior.<br>
<br>
- some people thought that the variant syntax was confusing.<br>
specifically, the relationship =A0between a variant record and the<br>
selector. (the selector is the element _in_ the variant map<br>
declaration that has a literal value.) in other words, the way the<br>
LLIDL parser knows that a particular variant is &quot;valid&quot; is that o=
ne of<br>
the members of the map has a specific value. the relationship to the<br>
variant and the selector was considered &quot;haphazard&quot; by some revie=
wers.<br>
<br>
- explaining the use of &quot;late keys.&quot; i.e. - the &#39;$&#39; in so=
me LLIDL<br>
definitions. the use of the dollar sign (&#39;$&#39;) in LLIDL as the key o=
f a<br>
map declaration indicates that there&#39;ll be a number of keys, the<br>
symbol for each is determined at message send time, not at resource<br>
definition time.<br>
<br>
- fixing things like broken XML DTDs.<br>
<br>
- changing the comment character from a semi-colon (&#39;;&#39;) to a hash =
mark (&#39;#&#39;)<br>
<br>
* Intro and Goals<br>
<br>
There was a lot of commentary on the original &quot;intro and requirements&=
quot;<br>
doc in Stockholm, and a trickle of interest since then. There are a<br>
few minor changes to the draft, and the inclusion of a much better<br>
glossary. David is writing a section on deployment patterns, and we<br>
plan to integrate our changes &quot;any day now.&quot;<br>
<br>
* Assets<br>
<br>
The Assets draft is in a much more &quot;complicated&quot; state. We&#39;re=
<br>
coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.<br>
<br>
-cheers<br>
-meadhbh<br>
<div><div></div><div class=3D"h5"><br>
On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca &lt;<a href=3D"mailto:vaughn=
.deluca@gmail.com">vaughn.deluca@gmail.com</a>&gt; wrote:<br>
&gt; It has gotten terribly silent on the list, and its not hard to see why=
;<br>
&gt; without updates of the drafts the discussion floats free and people ar=
e<br>
&gt; bound to loose interest.<br>
&gt; I =A0do understand that drafting these types of documents takes time, =
and too<br>
&gt; much discussion in an early stage sometimes only complicates matters, =
yet, a<br>
&gt; quick status update and maybe even a working version of the drafts in =
their<br>
&gt; current form would be nice to keep everybody synchronised...<br>
&gt; -Vaughn<br>
</div></div>&gt; _______________________________________________<br>
&gt; ogpx mailing list<br>
&gt; <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
</blockquote></div><br>

--0016e6d7e3257b74d504798509a8--

From morgaine.dinova@googlemail.com  Sun Nov 29 09:06:30 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2CFD3A6946 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 09:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 PPpkn0R7aUlP for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 09:06:29 -0800 (PST)
Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com [209.85.219.215]) by core3.amsl.com (Postfix) with ESMTP id CA77F3A67FD for <ogpx@ietf.org>; Sun, 29 Nov 2009 09:06:28 -0800 (PST)
Received: by ewy7 with SMTP id 7so3581755ewy.28 for <ogpx@ietf.org>; Sun, 29 Nov 2009 09:06:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=HUtQcAU48HIP6GHaoKFxWHaw8TsjSH2i5GXcXCv7ltc=; b=VA4+ugMsyOpC8xMovfY40TKoyhBMl9uUc9mfqofMdcRL5ov2+jvcfls5hmXJU0nESf 5M8gJdJhGGt8tDZKdoGlQ+yLKsq1iB9exBO2l9vzt+grf2dfdzlL2uXkJjQheDb6YflV IYXwQSU/EjgGqUaWIk8vFap8beC5/T8KAPvfw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=TEBYDq/Qq9OGTYWQ37szuSvG7b0Ojmj/9FW5wXXexUYWO2CKpsBdusO4CGrCL6Jx2U OQEJ6RPopHb4AwlEkNDGsk96UmIZAFdGDaM4Zfuah2AItjv9DM5C/5Pdc9oigujMyQTf gJ5ZVbfWTveP3lfLhnG2sXeZaDiRBV3zJBg+w=
MIME-Version: 1.0
Received: by 10.216.88.138 with SMTP id a10mr1080847wef.163.1259514376751;  Sun, 29 Nov 2009 09:06:16 -0800 (PST)
In-Reply-To: <e0b04bba0911290830m16afb4e3r6f386c8d02f089f0@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com> <e0b04bba0911290830m16afb4e3r6f386c8d02f089f0@mail.gmail.com>
Date: Sun, 29 Nov 2009 17:06:16 +0000
Message-ID: <e0b04bba0911290906s7ec3cbe1pecfeacb81acae1fa@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d77e7a0409a80479858b1b
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 17:06:31 -0000

--0016e6d77e7a0409a80479858b1b
Content-Type: text/plain; charset=ISO-8859-1

The preceding reply escaped from Gmail while only half done, please ignore
or delete.  The intended reply will follow.

Morgaine.



====================================

On Sun, Nov 29, 2009 at 4:30 PM, Morgaine <morgaine.dinova@googlemail.com>wrote:

> Might I suggest that, instead of working on several documents behind closed
> doors, that instead those documents be worked on *one at a time* right
> here *in the VWRAP list* where that effort belongs?
>
> That was how we managed to arrive at a group charter in a timely fashion,
> by focusing on one thing at a time so that the whole group could contribute
> meaningfully to a linear discussion.  The documents are not independent of
> each other, so writing a pile of them simultaneously just creates inertia in
> the process of change and promotes a desire for rubber-stamping, which isn't
> going to happen.
>
> The Intro document req
>
>
>
>
> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <
> meadhbh.siobhan@gmail.com> wrote:
>
>> yes, VWRAP _is_ still alive.
>>
>> we're currently working on three documents: LLSD / LLIDL, Intro and
>> Requirements, and Assets
>>
>> * LLSD / LLIDL
>>
>> LLIDL was in the middle of getting a well deserved face lift when
>> multiple, conflicting changes forced us to return to agreeing on the
>> problem definition instead of pushing out a draft. LLIDL / LLSD draft
>> development has been being informed by several pairwise / intense
>> descussions involving investigation of specific use cases. i hope to
>> get a wiki page up describing proposed changes at the end of this
>> week.
>>
>> but essentially what we're looking at is thus:
>>
>> - peeps didn't grok why LLSD has the "you get the default value when
>> you read a map key that's not there" semantics, so i'm integrating the
>> "structure and interpretation of LLSD messages" email into the draft
>> as motivation for why LLSD is needed. (
>> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
>>
>> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
>> enough." i'm developing a proposal for making LLIDL look more like an
>> ALGOL derived language so C/C++/C#/Java programmers can look at it and
>> have a more immediate understanding of what it's doing.
>>
>> - we want to be able to support GETs as well as POSTs when LLSD is
>> carried over HTTP(S). this is so we an make use of intermediaries like
>> caching squid servers. so we're working on a way to map a resource
>> definition to a GET instead of a POST. i know there are some people
>> who want to carry LLSD over XMPP, so we're interested in avoiding
>> simply saying... "oh... just make this kind of message a GET" since
>> that's more of a HTTP(S) specific construction.
>>
>> - related to the item above, we're looking at ways to encode a request
>> as a query string. the idea here being that since some caching
>> intermediaries can cache two GET requests with the same URL, including
>> the query string, we want to be able to encode the request in the
>> query string to take advantage of the caching behavior.
>>
>> - some people thought that the variant syntax was confusing.
>> specifically, the relationship  between a variant record and the
>> selector. (the selector is the element _in_ the variant map
>> declaration that has a literal value.) in other words, the way the
>> LLIDL parser knows that a particular variant is "valid" is that one of
>> the members of the map has a specific value. the relationship to the
>> variant and the selector was considered "haphazard" by some reviewers.
>>
>> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
>> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
>> map declaration indicates that there'll be a number of keys, the
>> symbol for each is determined at message send time, not at resource
>> definition time.
>>
>> - fixing things like broken XML DTDs.
>>
>> - changing the comment character from a semi-colon (';') to a hash mark
>> ('#')
>>
>> * Intro and Goals
>>
>> There was a lot of commentary on the original "intro and requirements"
>> doc in Stockholm, and a trickle of interest since then. There are a
>> few minor changes to the draft, and the inclusion of a much better
>> glossary. David is writing a section on deployment patterns, and we
>> plan to integrate our changes "any day now."
>>
>> * Assets
>>
>> The Assets draft is in a much more "complicated" state. We're
>> coordinating our efforts with John Hurliman who's the lead developer
>> on the Cable Beach project. We hope that what will emerge will be a
>> unified protocol for accessing second life resources as cable beach
>> resources.
>>
>> -cheers
>> -meadhbh
>>
>> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.com>
>> wrote:
>> > It has gotten terribly silent on the list, and its not hard to see why;
>> > without updates of the drafts the discussion floats free and people are
>> > bound to loose interest.
>> > I  do understand that drafting these types of documents takes time, and
>> too
>> > much discussion in an early stage sometimes only complicates matters,
>> yet, a
>> > quick status update and maybe even a working version of the drafts in
>> their
>> > current form would be nice to keep everybody synchronised...
>> > -Vaughn
>> > _______________________________________________
>> > ogpx mailing list
>> > ogpx@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ogpx
>> >
>> >
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>>
>
>

--0016e6d77e7a0409a80479858b1b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The preceding reply escaped from Gmail while only half done, please ignore =
or delete.=A0 The intended reply will follow.<br><br>Morgaine.<br><br><br><=
br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">On S=
un, Nov 29, 2009 at 4:30 PM, Morgaine <span dir=3D"ltr">&lt;<a href=3D"mail=
to:morgaine.dinova@googlemail.com">morgaine.dinova@googlemail.com</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Might I suggest t=
hat, instead of working on several documents behind closed doors, that inst=
ead those documents be worked on <i><b>one at a time</b></i> right here <i>=
<b>in the VWRAP list</b></i> where that effort belongs?<br>

<br>That was how we managed to arrive at a group charter in a timely fashio=
n, by focusing on one thing at a time so that the whole group could contrib=
ute meaningfully to a linear discussion.=A0 The documents are not independe=
nt of each other, so writing a pile of them simultaneously just creates ine=
rtia in the process of change and promotes a desire for rubber-stamping, wh=
ich isn&#39;t going to happen.<br>

<br>The Intro document req<div><div></div><div class=3D"h5"><br><br><br><br=
><div class=3D"gmail_quote">On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamric=
k <span dir=3D"ltr">&lt;<a href=3D"mailto:meadhbh.siobhan@gmail.com" target=
=3D"_blank">meadhbh.siobhan@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">yes, VWRAP _is_ s=
till alive.<br>
<br>
we&#39;re currently working on three documents: LLSD / LLIDL, Intro and<br>
Requirements, and Assets<br>
<br>
* LLSD / LLIDL<br>
<br>
LLIDL was in the middle of getting a well deserved face lift when<br>
multiple, conflicting changes forced us to return to agreeing on the<br>
problem definition instead of pushing out a draft. LLIDL / LLSD draft<br>
development has been being informed by several pairwise / intense<br>
descussions involving investigation of specific use cases. i hope to<br>
get a wiki page up describing proposed changes at the end of this<br>
week.<br>
<br>
but essentially what we&#39;re looking at is thus:<br>
<br>
- peeps didn&#39;t grok why LLSD has the &quot;you get the default value wh=
en<br>
you read a map key that&#39;s not there&quot; semantics, so i&#39;m integra=
ting the<br>
&quot;structure and interpretation of LLSD messages&quot; email into the dr=
aft<br>
as motivation for why LLSD is needed. (<br>
<a href=3D"http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html"=
 target=3D"_blank">http://www.ietf.org/mail-archive/web/mmox/current/msg006=
79.html</a> )<br>
<br>
- peeps thought the LLIDL syntax was odd, that it didn&#39;t look &quot;Cis=
h<br>
enough.&quot; i&#39;m developing a proposal for making LLIDL look more like=
 an<br>
ALGOL derived language so C/C++/C#/Java programmers can look at it and<br>
have a more immediate understanding of what it&#39;s doing.<br>
<br>
- we want to be able to support GETs as well as POSTs when LLSD is<br>
carried over HTTP(S). this is so we an make use of intermediaries like<br>
caching squid servers. so we&#39;re working on a way to map a resource<br>
definition to a GET instead of a POST. i know there are some people<br>
who want to carry LLSD over XMPP, so we&#39;re interested in avoiding<br>
simply saying... &quot;oh... just make this kind of message a GET&quot; sin=
ce<br>
that&#39;s more of a HTTP(S) specific construction.<br>
<br>
- related to the item above, we&#39;re looking at ways to encode a request<=
br>
as a query string. the idea here being that since some caching<br>
intermediaries can cache two GET requests with the same URL, including<br>
the query string, we want to be able to encode the request in the<br>
query string to take advantage of the caching behavior.<br>
<br>
- some people thought that the variant syntax was confusing.<br>
specifically, the relationship =A0between a variant record and the<br>
selector. (the selector is the element _in_ the variant map<br>
declaration that has a literal value.) in other words, the way the<br>
LLIDL parser knows that a particular variant is &quot;valid&quot; is that o=
ne of<br>
the members of the map has a specific value. the relationship to the<br>
variant and the selector was considered &quot;haphazard&quot; by some revie=
wers.<br>
<br>
- explaining the use of &quot;late keys.&quot; i.e. - the &#39;$&#39; in so=
me LLIDL<br>
definitions. the use of the dollar sign (&#39;$&#39;) in LLIDL as the key o=
f a<br>
map declaration indicates that there&#39;ll be a number of keys, the<br>
symbol for each is determined at message send time, not at resource<br>
definition time.<br>
<br>
- fixing things like broken XML DTDs.<br>
<br>
- changing the comment character from a semi-colon (&#39;;&#39;) to a hash =
mark (&#39;#&#39;)<br>
<br>
* Intro and Goals<br>
<br>
There was a lot of commentary on the original &quot;intro and requirements&=
quot;<br>
doc in Stockholm, and a trickle of interest since then. There are a<br>
few minor changes to the draft, and the inclusion of a much better<br>
glossary. David is writing a section on deployment patterns, and we<br>
plan to integrate our changes &quot;any day now.&quot;<br>
<br>
* Assets<br>
<br>
The Assets draft is in a much more &quot;complicated&quot; state. We&#39;re=
<br>
coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.<br>
<br>
-cheers<br>
-meadhbh<br>
<div><div></div><div><br>
On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca &lt;<a href=3D"mailto:vaughn=
.deluca@gmail.com" target=3D"_blank">vaughn.deluca@gmail.com</a>&gt; wrote:=
<br>
&gt; It has gotten terribly silent on the list, and its not hard to see why=
;<br>
&gt; without updates of the drafts the discussion floats free and people ar=
e<br>
&gt; bound to loose interest.<br>
&gt; I =A0do understand that drafting these types of documents takes time, =
and too<br>
&gt; much discussion in an early stage sometimes only complicates matters, =
yet, a<br>
&gt; quick status update and maybe even a working version of the drafts in =
their<br>
&gt; current form would be nice to keep everybody synchronised...<br>
&gt; -Vaughn<br>
</div></div>&gt; _______________________________________________<br>
&gt; ogpx mailing list<br>
&gt; <a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
</blockquote></div><br>
</div></div></blockquote></div><br>

--0016e6d77e7a0409a80479858b1b--

From morgaine.dinova@googlemail.com  Sun Nov 29 09:13:20 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4C243A67F1 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 09:13:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 4eghF+KI1345 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 09:13:14 -0800 (PST)
Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com [209.85.219.215]) by core3.amsl.com (Postfix) with ESMTP id 280E33A68BC for <ogpx@ietf.org>; Sun, 29 Nov 2009 09:13:11 -0800 (PST)
Received: by ewy7 with SMTP id 7so3586832ewy.28 for <ogpx@ietf.org>; Sun, 29 Nov 2009 09:13:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=zwsqhL1gaX9FpjH8UgahmhC84szsXfi2WRGZwhykSJA=; b=C+9DjNknl4yxKYS7g45ftl45Tj5BG284wrEekxDkX78s/WCYcwr0mRgTmulVskCMMK GC5MFcyNHRzHpQ0Er18c8lqFDFFfU4dqx+15h3ZclWzyWMZPwPfqBP32YIO+eizzpcwN q7LPrPVFfkAY2vwWouRkdTXEiF9KAXpp0V4lM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=WysyLPDde2gvMeTEQgP6IK2jebnieQMW2bkiQWz6YRgN8odDPoZaydHkrI6BXu/A2r t9+vraHwcdEeI0FJrOWIsc7zKL/6m3r/Pgb99Hui2whHR6nmcRs9B114gbywidzJbk1r FEBodSVYw1XYQbmvTEZsikXxDYcW9NZ1zx29I=
MIME-Version: 1.0
Received: by 10.216.87.12 with SMTP id x12mr1178063wee.48.1259514781579; Sun,  29 Nov 2009 09:13:01 -0800 (PST)
In-Reply-To: <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>
Date: Sun, 29 Nov 2009 17:13:01 +0000
Message-ID: <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d7e0a92538c1047985a354
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 17:13:20 -0000

--0016e6d7e0a92538c1047985a354
Content-Type: text/plain; charset=ISO-8859-1

Might I suggest that, instead of working on several documents behind closed
doors, that those documents be worked on *one at a time* right here *in the
VWRAP list* where that effort belongs?

That was how we managed to arrive at a group charter in a timely fashion, by
focusing on one thing at a time so that the whole group could contribute
meaningfully in a linear discussion.  The documents are not independent of
each other, so writing a number of them simultaneously just creates inertia
in the process of change and promotes a desire for rubber-stamping, which
isn't going to happen.

The Intro document requires a very large number of changes as a result of
our removal of "one world" wording from the charter, for consistency and
clarity and to avoid the question of "Which world?" at any given time.

Our protocol is very different now from the early days of OGP.  In effect,
it treats every region domain (and potentially every region) as a separate
world, since they can each have local policies, separate asset services, and
so on --- in other words, there is no longer any single world, which is why
we found an easy basis for agreement in the charter.  The documents need to
reflect that, starting from the Intro.

On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick
<meadhbh.siobhan@gmail.com>wrote:

The Assets draft is in a much more "complicated" state. We're
coordinating our efforts with John Hurliman who's the lead developer
on the Cable Beach project. We hope that what will emerge will be a
unified protocol for accessing second life resources as cable beach
resources.


The right place for coordinating this is VWRAP, so that decisions made in
the name of "coordination" obtain early input from the VWRAP contributors.
That's what we're here for.

In particular, we have already been discussing the operation of multiple
asset services right here with Joshua, so how this might work in conjunction
with Cable Beach is a matter of much interest to us.  There are bound to be
numerous alternative approaches, so I recommend that they be discussed
openly here with a lot of eyeballs on the problem, while ideas are still
fluid.


Morgaine.


==========================================

On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick
<meadhbh.siobhan@gmail.com>wrote:

> yes, VWRAP _is_ still alive.
>
> we're currently working on three documents: LLSD / LLIDL, Intro and
> Requirements, and Assets
>
> * LLSD / LLIDL
>
> LLIDL was in the middle of getting a well deserved face lift when
> multiple, conflicting changes forced us to return to agreeing on the
> problem definition instead of pushing out a draft. LLIDL / LLSD draft
> development has been being informed by several pairwise / intense
> descussions involving investigation of specific use cases. i hope to
> get a wiki page up describing proposed changes at the end of this
> week.
>
> but essentially what we're looking at is thus:
>
> - peeps didn't grok why LLSD has the "you get the default value when
> you read a map key that's not there" semantics, so i'm integrating the
> "structure and interpretation of LLSD messages" email into the draft
> as motivation for why LLSD is needed. (
> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
>
> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
> enough." i'm developing a proposal for making LLIDL look more like an
> ALGOL derived language so C/C++/C#/Java programmers can look at it and
> have a more immediate understanding of what it's doing.
>
> - we want to be able to support GETs as well as POSTs when LLSD is
> carried over HTTP(S). this is so we an make use of intermediaries like
> caching squid servers. so we're working on a way to map a resource
> definition to a GET instead of a POST. i know there are some people
> who want to carry LLSD over XMPP, so we're interested in avoiding
> simply saying... "oh... just make this kind of message a GET" since
> that's more of a HTTP(S) specific construction.
>
> - related to the item above, we're looking at ways to encode a request
> as a query string. the idea here being that since some caching
> intermediaries can cache two GET requests with the same URL, including
> the query string, we want to be able to encode the request in the
> query string to take advantage of the caching behavior.
>
> - some people thought that the variant syntax was confusing.
> specifically, the relationship  between a variant record and the
> selector. (the selector is the element _in_ the variant map
> declaration that has a literal value.) in other words, the way the
> LLIDL parser knows that a particular variant is "valid" is that one of
> the members of the map has a specific value. the relationship to the
> variant and the selector was considered "haphazard" by some reviewers.
>
> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
> map declaration indicates that there'll be a number of keys, the
> symbol for each is determined at message send time, not at resource
> definition time.
>
> - fixing things like broken XML DTDs.
>
> - changing the comment character from a semi-colon (';') to a hash mark
> ('#')
>
> * Intro and Goals
>
> There was a lot of commentary on the original "intro and requirements"
> doc in Stockholm, and a trickle of interest since then. There are a
> few minor changes to the draft, and the inclusion of a much better
> glossary. David is writing a section on deployment patterns, and we
> plan to integrate our changes "any day now."
>
> * Assets
>
> The Assets draft is in a much more "complicated" state. We're
> coordinating our efforts with John Hurliman who's the lead developer
> on the Cable Beach project. We hope that what will emerge will be a
> unified protocol for accessing second life resources as cable beach
> resources.
>
> -cheers
> -meadhbh
>
> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.com>
> wrote:
> > It has gotten terribly silent on the list, and its not hard to see why;
> > without updates of the drafts the discussion floats free and people are
> > bound to loose interest.
> > I  do understand that drafting these types of documents takes time, and
> too
> > much discussion in an early stage sometimes only complicates matters,
> yet, a
> > quick status update and maybe even a working version of the drafts in
> their
> > current form would be nice to keep everybody synchronised...
> > -Vaughn
> > _______________________________________________
> > ogpx mailing list
> > ogpx@ietf.org
> > https://www.ietf.org/mailman/listinfo/ogpx
> >
> >
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>

--0016e6d7e0a92538c1047985a354
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Might I suggest that, instead of working on several documents behind closed=
 doors, that those documents be worked on <i><b>one at a time</b></i> right=
 here <i><b>in the VWRAP list</b></i> where that effort belongs?<br>
<br>That was how we managed to arrive at a group charter in a timely
fashion, by focusing on one thing at a time so that the whole group
could contribute meaningfully in a linear discussion.=A0 The documents
are not independent of each other, so writing a number of them
simultaneously just creates inertia in the process of change and
promotes a desire for rubber-stamping, which isn&#39;t going to happen.<br>
<br>The Intro document requires a very large number of changes as a result =
of our removal of &quot;one world&quot; wording from the charter, for consi=
stency and clarity and to avoid the question of &quot;Which world?&quot; at=
 any given time.<br>
<br>Our protocol is very different now from the early days of OGP.=A0 In ef=
fect, it treats every region domain (and potentially every region) as a sep=
arate world, since they can each have local policies, separate asset servic=
es, and so on --- in other words, there is no longer any single world, whic=
h is why we found an easy basis for agreement in the charter.=A0 The docume=
nts need to reflect that, starting from the Intro.<br>
<br>On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <span dir=3D"ltr">&lt;=
<a href=3D"mailto:meadhbh.siobhan@gmail.com">meadhbh.siobhan@gmail.com</a>&=
gt;</span> wrote:<br><br><div style=3D"margin-left: 40px;">The Assets draft=
 is in a much more &quot;complicated&quot; state. We&#39;re<br>

coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.</div><br><br>The right place for coordinating this is VWRAP, so =
that decisions made in the name of &quot;coordination&quot; obtain early in=
put from the VWRAP contributors.=A0 That&#39;s what we&#39;re here for.<br>
<br>In particular, we have already been discussing the operation of multipl=
e asset services right here with Joshua, so how this might work in conjunct=
ion with Cable Beach is a matter of much interest to us.=A0 There are bound=
 to be numerous alternative approaches, so I recommend that they be discuss=
ed openly here with a lot of eyeballs on the problem, while ideas are still=
 fluid.<br>
<br><br>Morgaine.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<br><br><div class=3D"gmail_quote">On Sun, Nov 29, 2009 at 2:31 PM, M=
eadhbh Hamrick <span dir=3D"ltr">&lt;<a href=3D"mailto:meadhbh.siobhan@gmai=
l.com">meadhbh.siobhan@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">yes, VWRAP _is_ s=
till alive.<br>
<br>
we&#39;re currently working on three documents: LLSD / LLIDL, Intro and<br>
Requirements, and Assets<br>
<br>
* LLSD / LLIDL<br>
<br>
LLIDL was in the middle of getting a well deserved face lift when<br>
multiple, conflicting changes forced us to return to agreeing on the<br>
problem definition instead of pushing out a draft. LLIDL / LLSD draft<br>
development has been being informed by several pairwise / intense<br>
descussions involving investigation of specific use cases. i hope to<br>
get a wiki page up describing proposed changes at the end of this<br>
week.<br>
<br>
but essentially what we&#39;re looking at is thus:<br>
<br>
- peeps didn&#39;t grok why LLSD has the &quot;you get the default value wh=
en<br>
you read a map key that&#39;s not there&quot; semantics, so i&#39;m integra=
ting the<br>
&quot;structure and interpretation of LLSD messages&quot; email into the dr=
aft<br>
as motivation for why LLSD is needed. (<br>
<a href=3D"http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html"=
 target=3D"_blank">http://www.ietf.org/mail-archive/web/mmox/current/msg006=
79.html</a> )<br>
<br>
- peeps thought the LLIDL syntax was odd, that it didn&#39;t look &quot;Cis=
h<br>
enough.&quot; i&#39;m developing a proposal for making LLIDL look more like=
 an<br>
ALGOL derived language so C/C++/C#/Java programmers can look at it and<br>
have a more immediate understanding of what it&#39;s doing.<br>
<br>
- we want to be able to support GETs as well as POSTs when LLSD is<br>
carried over HTTP(S). this is so we an make use of intermediaries like<br>
caching squid servers. so we&#39;re working on a way to map a resource<br>
definition to a GET instead of a POST. i know there are some people<br>
who want to carry LLSD over XMPP, so we&#39;re interested in avoiding<br>
simply saying... &quot;oh... just make this kind of message a GET&quot; sin=
ce<br>
that&#39;s more of a HTTP(S) specific construction.<br>
<br>
- related to the item above, we&#39;re looking at ways to encode a request<=
br>
as a query string. the idea here being that since some caching<br>
intermediaries can cache two GET requests with the same URL, including<br>
the query string, we want to be able to encode the request in the<br>
query string to take advantage of the caching behavior.<br>
<br>
- some people thought that the variant syntax was confusing.<br>
specifically, the relationship =A0between a variant record and the<br>
selector. (the selector is the element _in_ the variant map<br>
declaration that has a literal value.) in other words, the way the<br>
LLIDL parser knows that a particular variant is &quot;valid&quot; is that o=
ne of<br>
the members of the map has a specific value. the relationship to the<br>
variant and the selector was considered &quot;haphazard&quot; by some revie=
wers.<br>
<br>
- explaining the use of &quot;late keys.&quot; i.e. - the &#39;$&#39; in so=
me LLIDL<br>
definitions. the use of the dollar sign (&#39;$&#39;) in LLIDL as the key o=
f a<br>
map declaration indicates that there&#39;ll be a number of keys, the<br>
symbol for each is determined at message send time, not at resource<br>
definition time.<br>
<br>
- fixing things like broken XML DTDs.<br>
<br>
- changing the comment character from a semi-colon (&#39;;&#39;) to a hash =
mark (&#39;#&#39;)<br>
<br>
* Intro and Goals<br>
<br>
There was a lot of commentary on the original &quot;intro and requirements&=
quot;<br>
doc in Stockholm, and a trickle of interest since then. There are a<br>
few minor changes to the draft, and the inclusion of a much better<br>
glossary. David is writing a section on deployment patterns, and we<br>
plan to integrate our changes &quot;any day now.&quot;<br>
<br>
* Assets<br>
<br>
The Assets draft is in a much more &quot;complicated&quot; state. We&#39;re=
<br>
coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.<br>
<br>
-cheers<br>
-meadhbh<br>
<div><div></div><div class=3D"h5"><br>
On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca &lt;<a href=3D"mailto:vaughn=
.deluca@gmail.com">vaughn.deluca@gmail.com</a>&gt; wrote:<br>
&gt; It has gotten terribly silent on the list, and its not hard to see why=
;<br>
&gt; without updates of the drafts the discussion floats free and people ar=
e<br>
&gt; bound to loose interest.<br>
&gt; I =A0do understand that drafting these types of documents takes time, =
and too<br>
&gt; much discussion in an early stage sometimes only complicates matters, =
yet, a<br>
&gt; quick status update and maybe even a working version of the drafts in =
their<br>
&gt; current form would be nice to keep everybody synchronised...<br>
&gt; -Vaughn<br>
</div></div>&gt; _______________________________________________<br>
&gt; ogpx mailing list<br>
&gt; <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
</blockquote></div><br>

--0016e6d7e0a92538c1047985a354--

From meadhbh.siobhan@gmail.com  Sun Nov 29 09:39:59 2009
Return-Path: <meadhbh.siobhan@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC0203A6982 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 09:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 huMdp7244lpX for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 09:39:58 -0800 (PST)
Received: from mail-pz0-f176.google.com (mail-pz0-f176.google.com [209.85.222.176]) by core3.amsl.com (Postfix) with ESMTP id 6F2AB3A6981 for <ogpx@ietf.org>; Sun, 29 Nov 2009 09:39:58 -0800 (PST)
Received: by pzk6 with SMTP id 6so1918883pzk.29 for <ogpx@ietf.org>; Sun, 29 Nov 2009 09:39:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VSWhB9MOLtZ8IBUpWup5qjaTOxKwfVIXAcEsj5Vpg8w=; b=myOW5TVTMhcB/i0yHJEEufhMREY4muKggZXc7WRRXVwCCPCObxSqBiVS7K3VEVOSxE YsNis3dKylNIut5v3QksCcA86rm3BU195tMMakmlr9Fb660OxEe/A4rcMBnOo9QmsBf3 3NLRo8DFVm7Moa9b3+u5ihcZJRyqkUobGtyyM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TMMI5YVxh2xTh7OpKH4R4B7EIkvOZo8ftzWHhvwXmfmuX01mocZdlriUMIej2vzbNt OugYXQu8qR1UOG+7MZ82WGdUq4fN94ozTd/brM1fE1McssaZPrO/A4ArI29mVZi4fqZl DoES89dBNgqF4R7JjCOsyjLJrp1rFubT/i1jc=
MIME-Version: 1.0
Received: by 10.115.100.30 with SMTP id c30mr5138176wam.211.1259516389399;  Sun, 29 Nov 2009 09:39:49 -0800 (PST)
In-Reply-To: <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com> <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com>
Date: Sun, 29 Nov 2009 09:39:49 -0800
Message-ID: <b8ef0a220911290939x7619873dyff07976c0b301cbf@mail.gmail.com>
From: Meadhbh Hamrick <meadhbh.siobhan@gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 17:39:59 -0000

okay. you go first.

On Sun, Nov 29, 2009 at 9:13 AM, Morgaine
<morgaine.dinova@googlemail.com> wrote:
> Might I suggest that, instead of working on several documents behind clos=
ed
> doors, that those documents be worked on one at a time right here in the
> VWRAP list where that effort belongs?
>
> That was how we managed to arrive at a group charter in a timely fashion,=
 by
> focusing on one thing at a time so that the whole group could contribute
> meaningfully in a linear discussion.=A0 The documents are not independent=
 of
> each other, so writing a number of them simultaneously just creates inert=
ia
> in the process of change and promotes a desire for rubber-stamping, which
> isn't going to happen.
>
> The Intro document requires a very large number of changes as a result of
> our removal of "one world" wording from the charter, for consistency and
> clarity and to avoid the question of "Which world?" at any given time.
>
> Our protocol is very different now from the early days of OGP.=A0 In effe=
ct,
> it treats every region domain (and potentially every region) as a separat=
e
> world, since they can each have local policies, separate asset services, =
and
> so on --- in other words, there is no longer any single world, which is w=
hy
> we found an easy basis for agreement in the charter.=A0 The documents nee=
d to
> reflect that, starting from the Intro.
>
> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <meadhbh.siobhan@gmail.c=
om>
> wrote:
>
> The Assets draft is in a much more "complicated" state. We're
> coordinating our efforts with John Hurliman who's the lead developer
> on the Cable Beach project. We hope that what will emerge will be a
> unified protocol for accessing second life resources as cable beach
> resources.
>
> The right place for coordinating this is VWRAP, so that decisions made in
> the name of "coordination" obtain early input from the VWRAP contributors=
.
> That's what we're here for.
>
> In particular, we have already been discussing the operation of multiple
> asset services right here with Joshua, so how this might work in conjunct=
ion
> with Cable Beach is a matter of much interest to us.=A0 There are bound t=
o be
> numerous alternative approaches, so I recommend that they be discussed
> openly here with a lot of eyeballs on the problem, while ideas are still
> fluid.
>
>
> Morgaine.
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <meadhbh.siobhan@gmail.c=
om>
> wrote:
>>
>> yes, VWRAP _is_ still alive.
>>
>> we're currently working on three documents: LLSD / LLIDL, Intro and
>> Requirements, and Assets
>>
>> * LLSD / LLIDL
>>
>> LLIDL was in the middle of getting a well deserved face lift when
>> multiple, conflicting changes forced us to return to agreeing on the
>> problem definition instead of pushing out a draft. LLIDL / LLSD draft
>> development has been being informed by several pairwise / intense
>> descussions involving investigation of specific use cases. i hope to
>> get a wiki page up describing proposed changes at the end of this
>> week.
>>
>> but essentially what we're looking at is thus:
>>
>> - peeps didn't grok why LLSD has the "you get the default value when
>> you read a map key that's not there" semantics, so i'm integrating the
>> "structure and interpretation of LLSD messages" email into the draft
>> as motivation for why LLSD is needed. (
>> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
>>
>> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
>> enough." i'm developing a proposal for making LLIDL look more like an
>> ALGOL derived language so C/C++/C#/Java programmers can look at it and
>> have a more immediate understanding of what it's doing.
>>
>> - we want to be able to support GETs as well as POSTs when LLSD is
>> carried over HTTP(S). this is so we an make use of intermediaries like
>> caching squid servers. so we're working on a way to map a resource
>> definition to a GET instead of a POST. i know there are some people
>> who want to carry LLSD over XMPP, so we're interested in avoiding
>> simply saying... "oh... just make this kind of message a GET" since
>> that's more of a HTTP(S) specific construction.
>>
>> - related to the item above, we're looking at ways to encode a request
>> as a query string. the idea here being that since some caching
>> intermediaries can cache two GET requests with the same URL, including
>> the query string, we want to be able to encode the request in the
>> query string to take advantage of the caching behavior.
>>
>> - some people thought that the variant syntax was confusing.
>> specifically, the relationship =A0between a variant record and the
>> selector. (the selector is the element _in_ the variant map
>> declaration that has a literal value.) in other words, the way the
>> LLIDL parser knows that a particular variant is "valid" is that one of
>> the members of the map has a specific value. the relationship to the
>> variant and the selector was considered "haphazard" by some reviewers.
>>
>> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
>> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
>> map declaration indicates that there'll be a number of keys, the
>> symbol for each is determined at message send time, not at resource
>> definition time.
>>
>> - fixing things like broken XML DTDs.
>>
>> - changing the comment character from a semi-colon (';') to a hash mark
>> ('#')
>>
>> * Intro and Goals
>>
>> There was a lot of commentary on the original "intro and requirements"
>> doc in Stockholm, and a trickle of interest since then. There are a
>> few minor changes to the draft, and the inclusion of a much better
>> glossary. David is writing a section on deployment patterns, and we
>> plan to integrate our changes "any day now."
>>
>> * Assets
>>
>> The Assets draft is in a much more "complicated" state. We're
>> coordinating our efforts with John Hurliman who's the lead developer
>> on the Cable Beach project. We hope that what will emerge will be a
>> unified protocol for accessing second life resources as cable beach
>> resources.
>>
>> -cheers
>> -meadhbh
>>
>> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.com>
>> wrote:
>> > It has gotten terribly silent on the list, and its not hard to see why=
;
>> > without updates of the drafts the discussion floats free and people ar=
e
>> > bound to loose interest.
>> > I =A0do understand that drafting these types of documents takes time, =
and
>> > too
>> > much discussion in an early stage sometimes only complicates matters,
>> > yet, a
>> > quick status update and maybe even a working version of the drafts in
>> > their
>> > current form would be nice to keep everybody synchronised...
>> > -Vaughn
>> > _______________________________________________
>> > ogpx mailing list
>> > ogpx@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ogpx
>> >
>> >
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>

From infinity@lindenlab.com  Sun Nov 29 10:11:37 2009
Return-Path: <infinity@lindenlab.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06D583A684C for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 10:11:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 rD3tLFGj6LgE for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 10:11:35 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id 777253A6822 for <ogpx@ietf.org>; Sun, 29 Nov 2009 10:11:34 -0800 (PST)
Received: by fxm5 with SMTP id 5so3006761fxm.28 for <ogpx@ietf.org>; Sun, 29 Nov 2009 10:11:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.239.179.101 with SMTP id c37mr351262hbg.4.1259518284298; Sun,  29 Nov 2009 10:11:24 -0800 (PST)
In-Reply-To: <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com>  <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>  <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com>
From: "Infinity Linden (Meadhbh Hamrick)" <infinity@lindenlab.com>
Date: Sun, 29 Nov 2009 10:11:04 -0800
Message-ID: <3a880e2c0911291011k3abcdff6webdf3c842a880100@mail.gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: multipart/alternative; boundary=001485f7d6e8ec7b5a0479867341
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 18:11:37 -0000

--001485f7d6e8ec7b5a0479867341
Content-Type: text/plain; charset=ISO-8859-1

what issues do you wish to discuss, specifically, morgaine?

--
  infinity linden (aka meadhbh hamrick)  *  it's pronounced "maeve"
        http://wiki.secondlife.com/wiki/User:Infinity_Linden


On Sun, Nov 29, 2009 at 09:13, Morgaine <morgaine.dinova@googlemail.com>wrote:

> Might I suggest that, instead of working on several documents behind closed
> doors, that those documents be worked on *one at a time* right here *in
> the VWRAP list* where that effort belongs?
>
> That was how we managed to arrive at a group charter in a timely fashion,
> by focusing on one thing at a time so that the whole group could contribute
> meaningfully in a linear discussion.  The documents are not independent of
> each other, so writing a number of them simultaneously just creates inertia
> in the process of change and promotes a desire for rubber-stamping, which
> isn't going to happen.
>
> The Intro document requires a very large number of changes as a result of
> our removal of "one world" wording from the charter, for consistency and
> clarity and to avoid the question of "Which world?" at any given time.
>
> Our protocol is very different now from the early days of OGP.  In effect,
> it treats every region domain (and potentially every region) as a separate
> world, since they can each have local policies, separate asset services, and
> so on --- in other words, there is no longer any single world, which is why
> we found an easy basis for agreement in the charter.  The documents need to
> reflect that, starting from the Intro.
>
>
> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <
> meadhbh.siobhan@gmail.com> wrote:
>
> The Assets draft is in a much more "complicated" state. We're
> coordinating our efforts with John Hurliman who's the lead developer
> on the Cable Beach project. We hope that what will emerge will be a
> unified protocol for accessing second life resources as cable beach
> resources.
>
>
> The right place for coordinating this is VWRAP, so that decisions made in
> the name of "coordination" obtain early input from the VWRAP contributors.
> That's what we're here for.
>
> In particular, we have already been discussing the operation of multiple
> asset services right here with Joshua, so how this might work in conjunction
> with Cable Beach is a matter of much interest to us.  There are bound to be
> numerous alternative approaches, so I recommend that they be discussed
> openly here with a lot of eyeballs on the problem, while ideas are still
> fluid.
>
>
> Morgaine.
>
>
> ==========================================
>
> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <
> meadhbh.siobhan@gmail.com> wrote:
>
>> yes, VWRAP _is_ still alive.
>>
>> we're currently working on three documents: LLSD / LLIDL, Intro and
>> Requirements, and Assets
>>
>> * LLSD / LLIDL
>>
>> LLIDL was in the middle of getting a well deserved face lift when
>> multiple, conflicting changes forced us to return to agreeing on the
>> problem definition instead of pushing out a draft. LLIDL / LLSD draft
>> development has been being informed by several pairwise / intense
>> descussions involving investigation of specific use cases. i hope to
>> get a wiki page up describing proposed changes at the end of this
>> week.
>>
>> but essentially what we're looking at is thus:
>>
>> - peeps didn't grok why LLSD has the "you get the default value when
>> you read a map key that's not there" semantics, so i'm integrating the
>> "structure and interpretation of LLSD messages" email into the draft
>> as motivation for why LLSD is needed. (
>> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
>>
>> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
>> enough." i'm developing a proposal for making LLIDL look more like an
>> ALGOL derived language so C/C++/C#/Java programmers can look at it and
>> have a more immediate understanding of what it's doing.
>>
>> - we want to be able to support GETs as well as POSTs when LLSD is
>> carried over HTTP(S). this is so we an make use of intermediaries like
>> caching squid servers. so we're working on a way to map a resource
>> definition to a GET instead of a POST. i know there are some people
>> who want to carry LLSD over XMPP, so we're interested in avoiding
>> simply saying... "oh... just make this kind of message a GET" since
>> that's more of a HTTP(S) specific construction.
>>
>> - related to the item above, we're looking at ways to encode a request
>> as a query string. the idea here being that since some caching
>> intermediaries can cache two GET requests with the same URL, including
>> the query string, we want to be able to encode the request in the
>> query string to take advantage of the caching behavior.
>>
>> - some people thought that the variant syntax was confusing.
>> specifically, the relationship  between a variant record and the
>> selector. (the selector is the element _in_ the variant map
>> declaration that has a literal value.) in other words, the way the
>> LLIDL parser knows that a particular variant is "valid" is that one of
>> the members of the map has a specific value. the relationship to the
>> variant and the selector was considered "haphazard" by some reviewers.
>>
>> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
>> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
>> map declaration indicates that there'll be a number of keys, the
>> symbol for each is determined at message send time, not at resource
>> definition time.
>>
>> - fixing things like broken XML DTDs.
>>
>> - changing the comment character from a semi-colon (';') to a hash mark
>> ('#')
>>
>> * Intro and Goals
>>
>> There was a lot of commentary on the original "intro and requirements"
>> doc in Stockholm, and a trickle of interest since then. There are a
>> few minor changes to the draft, and the inclusion of a much better
>> glossary. David is writing a section on deployment patterns, and we
>> plan to integrate our changes "any day now."
>>
>> * Assets
>>
>> The Assets draft is in a much more "complicated" state. We're
>> coordinating our efforts with John Hurliman who's the lead developer
>> on the Cable Beach project. We hope that what will emerge will be a
>> unified protocol for accessing second life resources as cable beach
>> resources.
>>
>> -cheers
>> -meadhbh
>>
>> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.com>
>> wrote:
>> > It has gotten terribly silent on the list, and its not hard to see why;
>> > without updates of the drafts the discussion floats free and people are
>> > bound to loose interest.
>> > I  do understand that drafting these types of documents takes time, and
>> too
>> > much discussion in an early stage sometimes only complicates matters,
>> yet, a
>> > quick status update and maybe even a working version of the drafts in
>> their
>> > current form would be nice to keep everybody synchronised...
>> > -Vaughn
>> > _______________________________________________
>> > ogpx mailing list
>> > ogpx@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ogpx
>> >
>> >
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>>
>
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>

--001485f7d6e8ec7b5a0479867341
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

what issues do you wish to discuss, specifically, morgaine?<div><br></div><=
div>--<br> =A0 infinity linden (aka meadhbh hamrick) =A0* =A0it&#39;s prono=
unced &quot;maeve&quot;<br> =A0 =A0 =A0 =A0 <a href=3D"http://wiki.secondli=
fe.com/wiki/User:Infinity_Linden">http://wiki.secondlife.com/wiki/User:Infi=
nity_Linden</a><br>


<br><br><div class=3D"gmail_quote">On Sun, Nov 29, 2009 at 09:13, Morgaine =
<span dir=3D"ltr">&lt;<a href=3D"mailto:morgaine.dinova@googlemail.com">mor=
gaine.dinova@googlemail.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex;">

Might I suggest that, instead of working on several documents behind closed=
 doors, that those documents be worked on <i><b>one at a time</b></i> right=
 here <i><b>in the VWRAP list</b></i> where that effort belongs?<br>
<br>That was how we managed to arrive at a group charter in a timely
fashion, by focusing on one thing at a time so that the whole group
could contribute meaningfully in a linear discussion.=A0 The documents
are not independent of each other, so writing a number of them
simultaneously just creates inertia in the process of change and
promotes a desire for rubber-stamping, which isn&#39;t going to happen.<br>
<br>The Intro document requires a very large number of changes as a result =
of our removal of &quot;one world&quot; wording from the charter, for consi=
stency and clarity and to avoid the question of &quot;Which world?&quot; at=
 any given time.<br>


<br>Our protocol is very different now from the early days of OGP.=A0 In ef=
fect, it treats every region domain (and potentially every region) as a sep=
arate world, since they can each have local policies, separate asset servic=
es, and so on --- in other words, there is no longer any single world, whic=
h is why we found an easy basis for agreement in the charter.=A0 The docume=
nts need to reflect that, starting from the Intro.<div class=3D"im">

<br>
<br>On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <span dir=3D"ltr">&lt;=
<a href=3D"mailto:meadhbh.siobhan@gmail.com" target=3D"_blank">meadhbh.siob=
han@gmail.com</a>&gt;</span> wrote:<br><br></div><div class=3D"im"><div sty=
le=3D"margin-left:40px">

The Assets draft is in a much more &quot;complicated&quot; state. We&#39;re=
<br>

coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.</div><br><br></div>The right place for coordinating this is VWRA=
P, so that decisions made in the name of &quot;coordination&quot; obtain ea=
rly input from the VWRAP contributors.=A0 That&#39;s what we&#39;re here fo=
r.<br>


<br>In particular, we have already been discussing the operation of multipl=
e asset services right here with Joshua, so how this might work in conjunct=
ion with Cable Beach is a matter of much interest to us.=A0 There are bound=
 to be numerous alternative approaches, so I recommend that they be discuss=
ed openly here with a lot of eyeballs on the problem, while ideas are still=
 fluid.<br>

<font color=3D"#888888">
<br><br>Morgaine.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<br><br></font><div class=3D"gmail_quote"><div class=3D"im">On Sun, N=
ov 29, 2009 at 2:31 PM, Meadhbh Hamrick <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:meadhbh.siobhan@gmail.com" target=3D"_blank">meadhbh.siobhan@gmail.com=
</a>&gt;</span> wrote:<br>


</div><div><div></div><div class=3D"h5"><blockquote class=3D"gmail_quote" s=
tyle=3D"border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;p=
adding-left:1ex">yes, VWRAP _is_ still alive.<br>
<br>
we&#39;re currently working on three documents: LLSD / LLIDL, Intro and<br>
Requirements, and Assets<br>
<br>
* LLSD / LLIDL<br>
<br>
LLIDL was in the middle of getting a well deserved face lift when<br>
multiple, conflicting changes forced us to return to agreeing on the<br>
problem definition instead of pushing out a draft. LLIDL / LLSD draft<br>
development has been being informed by several pairwise / intense<br>
descussions involving investigation of specific use cases. i hope to<br>
get a wiki page up describing proposed changes at the end of this<br>
week.<br>
<br>
but essentially what we&#39;re looking at is thus:<br>
<br>
- peeps didn&#39;t grok why LLSD has the &quot;you get the default value wh=
en<br>
you read a map key that&#39;s not there&quot; semantics, so i&#39;m integra=
ting the<br>
&quot;structure and interpretation of LLSD messages&quot; email into the dr=
aft<br>
as motivation for why LLSD is needed. (<br>
<a href=3D"http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html"=
 target=3D"_blank">http://www.ietf.org/mail-archive/web/mmox/current/msg006=
79.html</a> )<br>
<br>
- peeps thought the LLIDL syntax was odd, that it didn&#39;t look &quot;Cis=
h<br>
enough.&quot; i&#39;m developing a proposal for making LLIDL look more like=
 an<br>
ALGOL derived language so C/C++/C#/Java programmers can look at it and<br>
have a more immediate understanding of what it&#39;s doing.<br>
<br>
- we want to be able to support GETs as well as POSTs when LLSD is<br>
carried over HTTP(S). this is so we an make use of intermediaries like<br>
caching squid servers. so we&#39;re working on a way to map a resource<br>
definition to a GET instead of a POST. i know there are some people<br>
who want to carry LLSD over XMPP, so we&#39;re interested in avoiding<br>
simply saying... &quot;oh... just make this kind of message a GET&quot; sin=
ce<br>
that&#39;s more of a HTTP(S) specific construction.<br>
<br>
- related to the item above, we&#39;re looking at ways to encode a request<=
br>
as a query string. the idea here being that since some caching<br>
intermediaries can cache two GET requests with the same URL, including<br>
the query string, we want to be able to encode the request in the<br>
query string to take advantage of the caching behavior.<br>
<br>
- some people thought that the variant syntax was confusing.<br>
specifically, the relationship =A0between a variant record and the<br>
selector. (the selector is the element _in_ the variant map<br>
declaration that has a literal value.) in other words, the way the<br>
LLIDL parser knows that a particular variant is &quot;valid&quot; is that o=
ne of<br>
the members of the map has a specific value. the relationship to the<br>
variant and the selector was considered &quot;haphazard&quot; by some revie=
wers.<br>
<br>
- explaining the use of &quot;late keys.&quot; i.e. - the &#39;$&#39; in so=
me LLIDL<br>
definitions. the use of the dollar sign (&#39;$&#39;) in LLIDL as the key o=
f a<br>
map declaration indicates that there&#39;ll be a number of keys, the<br>
symbol for each is determined at message send time, not at resource<br>
definition time.<br>
<br>
- fixing things like broken XML DTDs.<br>
<br>
- changing the comment character from a semi-colon (&#39;;&#39;) to a hash =
mark (&#39;#&#39;)<br>
<br>
* Intro and Goals<br>
<br>
There was a lot of commentary on the original &quot;intro and requirements&=
quot;<br>
doc in Stockholm, and a trickle of interest since then. There are a<br>
few minor changes to the draft, and the inclusion of a much better<br>
glossary. David is writing a section on deployment patterns, and we<br>
plan to integrate our changes &quot;any day now.&quot;<br>
<br>
* Assets<br>
<br>
The Assets draft is in a much more &quot;complicated&quot; state. We&#39;re=
<br>
coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.<br>
<br>
-cheers<br>
-meadhbh<br>
<div><div></div><div><br>
On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca &lt;<a href=3D"mailto:vaughn=
.deluca@gmail.com" target=3D"_blank">vaughn.deluca@gmail.com</a>&gt; wrote:=
<br>
&gt; It has gotten terribly silent on the list, and its not hard to see why=
;<br>
&gt; without updates of the drafts the discussion floats free and people ar=
e<br>
&gt; bound to loose interest.<br>
&gt; I =A0do understand that drafting these types of documents takes time, =
and too<br>
&gt; much discussion in an early stage sometimes only complicates matters, =
yet, a<br>
&gt; quick status update and maybe even a working version of the drafts in =
their<br>
&gt; current form would be nice to keep everybody synchronised...<br>
&gt; -Vaughn<br>
</div></div>&gt; _______________________________________________<br>
&gt; ogpx mailing list<br>
&gt; <a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
</blockquote></div></div></div><br>
<br>_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
<br></blockquote></div><br></div>

--001485f7d6e8ec7b5a0479867341--

From carlo@alinoe.com  Sun Nov 29 12:37:16 2009
Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 217D23A69C0 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 12:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level: 
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 2MH6c21crTEP for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 12:37:15 -0800 (PST)
Received: from viefep20-int.chello.at (viefep20-int.chello.at [62.179.121.40]) by core3.amsl.com (Postfix) with ESMTP id EE5123A689E for <ogpx@ietf.org>; Sun, 29 Nov 2009 12:37:14 -0800 (PST)
Received: from edge03.upc.biz ([192.168.13.238]) by viefep20-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20091129203706.PLEV23910.viefep20-int.chello.at@edge03.upc.biz>; Sun, 29 Nov 2009 21:37:06 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge03.upc.biz with edge id B8d31d04m0FlQed038d4Tl; Sun, 29 Nov 2009 21:37:06 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.69) (envelope-from <carlo@alinoe.com>) id 1NEqTa-0000NR-JL; Sun, 29 Nov 2009 21:34:34 +0100
Date: Sun, 29 Nov 2009 21:34:34 +0100
From: Carlo Wood <carlo@alinoe.com>
To: Meadhbh Hamrick <meadhbh.siobhan@gmail.com>
Message-ID: <20091129203434.GA1006@alinoe.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 20:37:16 -0000

On Sun, Nov 29, 2009 at 06:31:50AM -0800, Meadhbh Hamrick wrote:
> yes, VWRAP _is_ still alive.
> 
> we're currently working on three documents: LLSD / LLIDL, Intro and
> Requirements, and Assets

Hmm, surprisingly so! Who is "we"?

Although I admire the working spirit and the fact that someone is
actually DOING something(!), in general it seems a bad idea to do
all that work on your own without any feedback / discussion on this
list, since it's the people on this list that will have to agree
with every detail, in fact - even come up with those details in
the first place. This approach might turn out to be very inefficent.

There is a not so small chance that you'd be working out details
of an otherwise flawed design (or at least, where the majority
of team would choose a different/better approach) and you'd just
be wasting time, since it will have to be redone once it's made
public to this list.

Imho, the correct way is to have all ideas posted here on this
list, a little at a time (or per thread; many threads can run
in parallel), so that the people on the team who have to agree
with whatever will be proposed to the IEEE can discuss it.
And only work on details once there is a general consensus on
the road being taken.

-- 
Carlo Wood <carlo@alinoe.com>

From morgaine.dinova@googlemail.com  Sun Nov 29 14:19:14 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 907873A69ED for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 14:19:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.143
X-Spam-Level: 
X-Spam-Status: No, score=-1.143 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SARE_HTML_USL_OBFU=1.666]
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 fxzHnFPBhNde for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 14:19:12 -0800 (PST)
Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com [209.85.219.215]) by core3.amsl.com (Postfix) with ESMTP id C29743A69EC for <ogpx@ietf.org>; Sun, 29 Nov 2009 14:19:11 -0800 (PST)
Received: by ewy7 with SMTP id 7so3818040ewy.28 for <ogpx@ietf.org>; Sun, 29 Nov 2009 14:19:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=/4iQHMsSGIrcLpgQp7uEtoKVubWR3pv6KDfkbnTtUlI=; b=nZlhUXEKfJh9HzAv1w/kWh3lZpuupB2jCetho9/UODMwdzlmDVaPDdIVp43jm+H//R 3dDKMxB9kevUXzATsjNzafnns6DdjGpszcaqZ82oDxQoKA6NknY0YoEnGyE+UWeRmMTA DZckRUsn54wzFm/JTHwtWYo5Y8GIUGBIYq3rk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=dEFon6KT9Sln7gUcuPChlGHUNKiA4cqKa52gAPcuFZXXnUROv4rwbwyK9ajeOvSbHS zhClMdXKJqm/LiqQwckYrrteVEyucj+jjja7+aaL99VxAJGxoJ7fgfrpuJjtH/ui4dtm UaYCpTRWXlLV9VrclRKa/avCg277mUb7cslfw=
MIME-Version: 1.0
Received: by 10.216.87.143 with SMTP id y15mr1183154wee.39.1259533142011; Sun,  29 Nov 2009 14:19:02 -0800 (PST)
In-Reply-To: <3a880e2c0911291011k3abcdff6webdf3c842a880100@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com> <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com> <3a880e2c0911291011k3abcdff6webdf3c842a880100@mail.gmail.com>
Date: Sun, 29 Nov 2009 22:19:01 +0000
Message-ID: <e0b04bba0911291419p7aadc9cfw752c52e939cc73c7@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d77e32832edb047989e992
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 22:19:14 -0000

--0016e6d77e32832edb047989e992
Content-Type: text/plain; charset=ISO-8859-1

On the Intro, a good place to start would be to take the document apart
top-down, get agreement on its scope and on what is NOT to be included
because it belongs in more detailed documents, agree on appropriate
sections, and fill them in --- largely from the old OGP material modified as
appropriate, I hope.  (This is how we made good progress on the charter
too.)   Another possibility is to leave the Intro until last, once we know
all the material that it's meant to introduce in overview --- it may be far
too early now because so much is changing.

On the "coordination with Cable Beach", really that should start with John
giving us some idea here of how he sees Cable Beach and VWRAP dovetailing.
Cable Beach was announced  on the MMOX
list<http://www.ietf.org/mail-archive/web/mmox/current/msg01378.html>,
yet we have been told on many occasions that the material on MMOX is
(by
definition) out of scope of OGPX/VWRAP, so there would seem to be some
confusion about MMOX vs OGPX scopes here if we're "coordinating with CB".

Cable Beach was developed independently by John's team at Intel.  An early
version was incorporated into Opensim, and most recently the realXtend
mailing list has mentioned that Cable Beach is evolving to integrate into
realXtend's new system design with its WebDAV-powered inventories, as
I  reported
here earlier<http://www.ietf.org/mail-archive/web/ogpx/current/msg00391.html>.
 This is all extremely interesting and even
*exciting* in the rapid progress it shows, but it does beg the question of
how progress in VWRAP fits in with everyone else's ongoing evolution.  CB is
not any kind of standard after all, it's Work In Progress, and at a rather
early stage of its design, so dependence on it needs to be explained.

Back in September, John
said<http://www.ietf.org/mail-archive/web/ogpx/current/msg00338.html>"
*I can't personally commit any development effort to VWRAP work at this
time, but I will continue to periodically sync Intel's Cable Beach work with
the VWRAP work and aim for a merging of features in the future*".  That
seemed to suggest that CB would follow VWRAP, but it left a lot unsaid.  We
had not even considered multiple asset services and policy-determining
regions back then.  Is it still on track to follow us?  What exactly is the
dependency between our two projects?

Personally I am very happy to see OGP take on in VWRAP a more embracing
concept of interop than its original narrow one, but this does need a lot of
clarification so that we know exactly what we're doing and why, since our
charter was made a narrow one on purpose.  I welcome the new breadth, but we
need to state what we're doing clearly and openly, and explain our new scope
and dependencies.


Morgaine.




=============================

On Sun, Nov 29, 2009 at 6:11 PM, Infinity Linden (Meadhbh Hamrick) <
infinity@lindenlab.com> wrote:

> what issues do you wish to discuss, specifically, morgaine?
>
> --
>   infinity linden (aka meadhbh hamrick)  *  it's pronounced "maeve"
>         http://wiki.secondlife.com/wiki/User:Infinity_Linden
>
>
> On Sun, Nov 29, 2009 at 09:13, Morgaine <morgaine.dinova@googlemail.com>wrote:
>
>> Might I suggest that, instead of working on several documents behind
>> closed doors, that those documents be worked on *one at a time* right
>> here *in the VWRAP list* where that effort belongs?
>>
>> That was how we managed to arrive at a group charter in a timely fashion,
>> by focusing on one thing at a time so that the whole group could contribute
>> meaningfully in a linear discussion.  The documents are not independent of
>> each other, so writing a number of them simultaneously just creates inertia
>> in the process of change and promotes a desire for rubber-stamping, which
>> isn't going to happen.
>>
>> The Intro document requires a very large number of changes as a result of
>> our removal of "one world" wording from the charter, for consistency and
>> clarity and to avoid the question of "Which world?" at any given time.
>>
>> Our protocol is very different now from the early days of OGP.  In effect,
>> it treats every region domain (and potentially every region) as a separate
>> world, since they can each have local policies, separate asset services, and
>> so on --- in other words, there is no longer any single world, which is why
>> we found an easy basis for agreement in the charter.  The documents need to
>> reflect that, starting from the Intro.
>>
>>
>> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <
>> meadhbh.siobhan@gmail.com> wrote:
>>
>> The Assets draft is in a much more "complicated" state. We're
>> coordinating our efforts with John Hurliman who's the lead developer
>> on the Cable Beach project. We hope that what will emerge will be a
>> unified protocol for accessing second life resources as cable beach
>> resources.
>>
>>
>> The right place for coordinating this is VWRAP, so that decisions made in
>> the name of "coordination" obtain early input from the VWRAP contributors.
>> That's what we're here for.
>>
>> In particular, we have already been discussing the operation of multiple
>> asset services right here with Joshua, so how this might work in conjunction
>> with Cable Beach is a matter of much interest to us.  There are bound to be
>> numerous alternative approaches, so I recommend that they be discussed
>> openly here with a lot of eyeballs on the problem, while ideas are still
>> fluid.
>>
>>
>> Morgaine.
>>
>>
>> ==========================================
>>
>> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <
>> meadhbh.siobhan@gmail.com> wrote:
>>
>>> yes, VWRAP _is_ still alive.
>>>
>>> we're currently working on three documents: LLSD / LLIDL, Intro and
>>> Requirements, and Assets
>>>
>>> * LLSD / LLIDL
>>>
>>> LLIDL was in the middle of getting a well deserved face lift when
>>> multiple, conflicting changes forced us to return to agreeing on the
>>> problem definition instead of pushing out a draft. LLIDL / LLSD draft
>>> development has been being informed by several pairwise / intense
>>> descussions involving investigation of specific use cases. i hope to
>>> get a wiki page up describing proposed changes at the end of this
>>> week.
>>>
>>> but essentially what we're looking at is thus:
>>>
>>> - peeps didn't grok why LLSD has the "you get the default value when
>>> you read a map key that's not there" semantics, so i'm integrating the
>>> "structure and interpretation of LLSD messages" email into the draft
>>> as motivation for why LLSD is needed. (
>>> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
>>>
>>> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
>>> enough." i'm developing a proposal for making LLIDL look more like an
>>> ALGOL derived language so C/C++/C#/Java programmers can look at it and
>>> have a more immediate understanding of what it's doing.
>>>
>>> - we want to be able to support GETs as well as POSTs when LLSD is
>>> carried over HTTP(S). this is so we an make use of intermediaries like
>>> caching squid servers. so we're working on a way to map a resource
>>> definition to a GET instead of a POST. i know there are some people
>>> who want to carry LLSD over XMPP, so we're interested in avoiding
>>> simply saying... "oh... just make this kind of message a GET" since
>>> that's more of a HTTP(S) specific construction.
>>>
>>> - related to the item above, we're looking at ways to encode a request
>>> as a query string. the idea here being that since some caching
>>> intermediaries can cache two GET requests with the same URL, including
>>> the query string, we want to be able to encode the request in the
>>> query string to take advantage of the caching behavior.
>>>
>>> - some people thought that the variant syntax was confusing.
>>> specifically, the relationship  between a variant record and the
>>> selector. (the selector is the element _in_ the variant map
>>> declaration that has a literal value.) in other words, the way the
>>> LLIDL parser knows that a particular variant is "valid" is that one of
>>> the members of the map has a specific value. the relationship to the
>>> variant and the selector was considered "haphazard" by some reviewers.
>>>
>>> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
>>> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
>>> map declaration indicates that there'll be a number of keys, the
>>> symbol for each is determined at message send time, not at resource
>>> definition time.
>>>
>>> - fixing things like broken XML DTDs.
>>>
>>> - changing the comment character from a semi-colon (';') to a hash mark
>>> ('#')
>>>
>>> * Intro and Goals
>>>
>>> There was a lot of commentary on the original "intro and requirements"
>>> doc in Stockholm, and a trickle of interest since then. There are a
>>> few minor changes to the draft, and the inclusion of a much better
>>> glossary. David is writing a section on deployment patterns, and we
>>> plan to integrate our changes "any day now."
>>>
>>> * Assets
>>>
>>> The Assets draft is in a much more "complicated" state. We're
>>> coordinating our efforts with John Hurliman who's the lead developer
>>> on the Cable Beach project. We hope that what will emerge will be a
>>> unified protocol for accessing second life resources as cable beach
>>> resources.
>>>
>>> -cheers
>>> -meadhbh
>>>
>>> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.com>
>>> wrote:
>>> > It has gotten terribly silent on the list, and its not hard to see why;
>>> > without updates of the drafts the discussion floats free and people are
>>> > bound to loose interest.
>>> > I  do understand that drafting these types of documents takes time, and
>>> too
>>> > much discussion in an early stage sometimes only complicates matters,
>>> yet, a
>>> > quick status update and maybe even a working version of the drafts in
>>> their
>>> > current form would be nice to keep everybody synchronised...
>>> > -Vaughn
>>> > _______________________________________________
>>> > ogpx mailing list
>>> > ogpx@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/ogpx
>>> >
>>> >
>>> _______________________________________________
>>> ogpx mailing list
>>> ogpx@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ogpx
>>>
>>
>>
>> _______________________________________________
>> ogpx mailing list
>> ogpx@ietf.org
>> https://www.ietf.org/mailman/listinfo/ogpx
>>
>>
>

--0016e6d77e32832edb047989e992
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On the Intro, a good place to start would be to take the document apart top=
-down, get agreement on its scope and on what is NOT to be included because=
 it belongs in more detailed documents, agree on appropriate sections, and =
fill them in --- largely from the old OGP material modified as appropriate,=
 I hope.=A0 (This is how we made good progress on the charter too.) =A0 Ano=
ther possibility is to leave the Intro until last, once we know all the mat=
erial that it&#39;s meant to introduce in overview --- it may be far too ea=
rly now because so much is changing.<br>
<br>On the &quot;coordination with Cable Beach&quot;, really that should st=
art with John giving us some idea here of how he sees Cable Beach and VWRAP=
 dovetailing.=A0 Cable Beach was announced=A0 <a href=3D"http://www.ietf.or=
g/mail-archive/web/mmox/current/msg01378.html">on the MMOX list</a> , yet w=
e have been told on many occasions that the material on MMOX is (by definit=
ion) out of scope of OGPX/VWRAP, so there would seem to be some confusion a=
bout MMOX vs OGPX scopes here if we&#39;re &quot;coordinating with CB&quot;=
.<br>
<br>Cable Beach was developed independently by John&#39;s team at Intel.=A0=
 An
early version was incorporated into Opensim, and most recently the
realXtend mailing list has mentioned that Cable Beach is evolving
to integrate into realXtend&#39;s new system design with its WebDAV-powered
inventories, as I=A0 <a href=3D"http://www.ietf.org/mail-archive/web/ogpx/c=
urrent/msg00391.html">reported here earlier</a> .=A0 This is all extremely =
interesting and even <i>exciting</i> in
the rapid progress it shows, but it does beg the question of how progress i=
n VWRAP
fits in with everyone else&#39;s ongoing evolution.=A0 CB is not any kind o=
f standard after all, it&#39;s Work In Progress, and at a rather early stag=
e of its design, so dependence on it needs to be explained.<br><br>Back in =
September, <a href=3D"http://www.ietf.org/mail-archive/web/ogpx/current/msg=
00338.html">John said</a> &quot;<i>I can&#39;t personally commit any develo=
pment effort to VWRAP work at this time, but I will c<span style=3D"font-si=
ze: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: r=
gb(31, 73, 125);"></span>ontinue to periodically sync Intel&#39;s Cable Bea=
ch work with the VWRAP work and aim for a merging of features in the future=
</i>&quot;.=A0 That seemed to suggest that CB would follow VWRAP, but it le=
ft a lot unsaid.=A0 We had not even considered multiple asset services and =
policy-determining regions back then.=A0 Is it still on track to follow us?=
=A0 What exactly is the dependency between our two projects?<br>
<br>Personally I am very happy to see OGP take on in VWRAP a more embracing=
 concept of interop than its original narrow one, but this does need a lot =
of clarification so that we know exactly what we&#39;re doing and why, sinc=
e our charter was made a narrow one on purpose.=A0 I welcome the new breadt=
h, but we need to state what we&#39;re doing clearly and openly, and explai=
n our new scope and dependencies.<br>
<br><br>Morgaine.<br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gm=
ail_quote">On Sun, Nov 29, 2009 at 6:11 PM, Infinity Linden (Meadhbh Hamric=
k) <span dir=3D"ltr">&lt;<a href=3D"mailto:infinity@lindenlab.com">infinity=
@lindenlab.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">what issues do yo=
u wish to discuss, specifically, morgaine?<div><br></div><div><div class=3D=
"im">
--<br> =A0 infinity linden (aka meadhbh hamrick) =A0* =A0it&#39;s pronounce=
d &quot;maeve&quot;<br> =A0 =A0 =A0 =A0 <a href=3D"http://wiki.secondlife.c=
om/wiki/User:Infinity_Linden" target=3D"_blank">http://wiki.secondlife.com/=
wiki/User:Infinity_Linden</a><br>



<br><br></div><div><div></div><div class=3D"h5"><div class=3D"gmail_quote">=
On Sun, Nov 29, 2009 at 09:13, Morgaine <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:morgaine.dinova@googlemail.com" target=3D"_blank">morgaine.dinova@goog=
lemail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

Might I suggest that, instead of working on several documents behind closed=
 doors, that those documents be worked on <i><b>one at a time</b></i> right=
 here <i><b>in the VWRAP list</b></i> where that effort belongs?<br>
<br>That was how we managed to arrive at a group charter in a timely
fashion, by focusing on one thing at a time so that the whole group
could contribute meaningfully in a linear discussion.=A0 The documents
are not independent of each other, so writing a number of them
simultaneously just creates inertia in the process of change and
promotes a desire for rubber-stamping, which isn&#39;t going to happen.<br>
<br>The Intro document requires a very large number of changes as a result =
of our removal of &quot;one world&quot; wording from the charter, for consi=
stency and clarity and to avoid the question of &quot;Which world?&quot; at=
 any given time.<br>



<br>Our protocol is very different now from the early days of OGP.=A0 In ef=
fect, it treats every region domain (and potentially every region) as a sep=
arate world, since they can each have local policies, separate asset servic=
es, and so on --- in other words, there is no longer any single world, whic=
h is why we found an easy basis for agreement in the charter.=A0 The docume=
nts need to reflect that, starting from the Intro.<div>


<br>
<br>On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick <span dir=3D"ltr">&lt;=
<a href=3D"mailto:meadhbh.siobhan@gmail.com" target=3D"_blank">meadhbh.siob=
han@gmail.com</a>&gt;</span> wrote:<br><br></div><div><div style=3D"margin-=
left: 40px;">


The Assets draft is in a much more &quot;complicated&quot; state. We&#39;re=
<br>

coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.</div><br><br></div>The right place for coordinating this is VWRA=
P, so that decisions made in the name of &quot;coordination&quot; obtain ea=
rly input from the VWRAP contributors.=A0 That&#39;s what we&#39;re here fo=
r.<br>



<br>In particular, we have already been discussing the operation of multipl=
e asset services right here with Joshua, so how this might work in conjunct=
ion with Cable Beach is a matter of much interest to us.=A0 There are bound=
 to be numerous alternative approaches, so I recommend that they be discuss=
ed openly here with a lot of eyeballs on the problem, while ideas are still=
 fluid.<br>


<font color=3D"#888888">
<br><br>Morgaine.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<br><br></font><div class=3D"gmail_quote"><div>On Sun, Nov 29, 2009 a=
t 2:31 PM, Meadhbh Hamrick <span dir=3D"ltr">&lt;<a href=3D"mailto:meadhbh.=
siobhan@gmail.com" target=3D"_blank">meadhbh.siobhan@gmail.com</a>&gt;</spa=
n> wrote:<br>



</div><div><div></div><div><blockquote class=3D"gmail_quote" style=3D"borde=
r-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-le=
ft: 1ex;">yes, VWRAP _is_ still alive.<br>
<br>
we&#39;re currently working on three documents: LLSD / LLIDL, Intro and<br>
Requirements, and Assets<br>
<br>
* LLSD / LLIDL<br>
<br>
LLIDL was in the middle of getting a well deserved face lift when<br>
multiple, conflicting changes forced us to return to agreeing on the<br>
problem definition instead of pushing out a draft. LLIDL / LLSD draft<br>
development has been being informed by several pairwise / intense<br>
descussions involving investigation of specific use cases. i hope to<br>
get a wiki page up describing proposed changes at the end of this<br>
week.<br>
<br>
but essentially what we&#39;re looking at is thus:<br>
<br>
- peeps didn&#39;t grok why LLSD has the &quot;you get the default value wh=
en<br>
you read a map key that&#39;s not there&quot; semantics, so i&#39;m integra=
ting the<br>
&quot;structure and interpretation of LLSD messages&quot; email into the dr=
aft<br>
as motivation for why LLSD is needed. (<br>
<a href=3D"http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html"=
 target=3D"_blank">http://www.ietf.org/mail-archive/web/mmox/current/msg006=
79.html</a> )<br>
<br>
- peeps thought the LLIDL syntax was odd, that it didn&#39;t look &quot;Cis=
h<br>
enough.&quot; i&#39;m developing a proposal for making LLIDL look more like=
 an<br>
ALGOL derived language so C/C++/C#/Java programmers can look at it and<br>
have a more immediate understanding of what it&#39;s doing.<br>
<br>
- we want to be able to support GETs as well as POSTs when LLSD is<br>
carried over HTTP(S). this is so we an make use of intermediaries like<br>
caching squid servers. so we&#39;re working on a way to map a resource<br>
definition to a GET instead of a POST. i know there are some people<br>
who want to carry LLSD over XMPP, so we&#39;re interested in avoiding<br>
simply saying... &quot;oh... just make this kind of message a GET&quot; sin=
ce<br>
that&#39;s more of a HTTP(S) specific construction.<br>
<br>
- related to the item above, we&#39;re looking at ways to encode a request<=
br>
as a query string. the idea here being that since some caching<br>
intermediaries can cache two GET requests with the same URL, including<br>
the query string, we want to be able to encode the request in the<br>
query string to take advantage of the caching behavior.<br>
<br>
- some people thought that the variant syntax was confusing.<br>
specifically, the relationship =A0between a variant record and the<br>
selector. (the selector is the element _in_ the variant map<br>
declaration that has a literal value.) in other words, the way the<br>
LLIDL parser knows that a particular variant is &quot;valid&quot; is that o=
ne of<br>
the members of the map has a specific value. the relationship to the<br>
variant and the selector was considered &quot;haphazard&quot; by some revie=
wers.<br>
<br>
- explaining the use of &quot;late keys.&quot; i.e. - the &#39;$&#39; in so=
me LLIDL<br>
definitions. the use of the dollar sign (&#39;$&#39;) in LLIDL as the key o=
f a<br>
map declaration indicates that there&#39;ll be a number of keys, the<br>
symbol for each is determined at message send time, not at resource<br>
definition time.<br>
<br>
- fixing things like broken XML DTDs.<br>
<br>
- changing the comment character from a semi-colon (&#39;;&#39;) to a hash =
mark (&#39;#&#39;)<br>
<br>
* Intro and Goals<br>
<br>
There was a lot of commentary on the original &quot;intro and requirements&=
quot;<br>
doc in Stockholm, and a trickle of interest since then. There are a<br>
few minor changes to the draft, and the inclusion of a much better<br>
glossary. David is writing a section on deployment patterns, and we<br>
plan to integrate our changes &quot;any day now.&quot;<br>
<br>
* Assets<br>
<br>
The Assets draft is in a much more &quot;complicated&quot; state. We&#39;re=
<br>
coordinating our efforts with John Hurliman who&#39;s the lead developer<br=
>
on the Cable Beach project. We hope that what will emerge will be a<br>
unified protocol for accessing second life resources as cable beach<br>
resources.<br>
<br>
-cheers<br>
-meadhbh<br>
<div><div></div><div><br>
On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca &lt;<a href=3D"mailto:vaughn=
.deluca@gmail.com" target=3D"_blank">vaughn.deluca@gmail.com</a>&gt; wrote:=
<br>
&gt; It has gotten terribly silent on the list, and its not hard to see why=
;<br>
&gt; without updates of the drafts the discussion floats free and people ar=
e<br>
&gt; bound to loose interest.<br>
&gt; I =A0do understand that drafting these types of documents takes time, =
and too<br>
&gt; much discussion in an early stage sometimes only complicates matters, =
yet, a<br>
&gt; quick status update and maybe even a working version of the drafts in =
their<br>
&gt; current form would be nice to keep everybody synchronised...<br>
&gt; -Vaughn<br>
</div></div>&gt; _______________________________________________<br>
&gt; ogpx mailing list<br>
&gt; <a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
</blockquote></div></div></div><br>
<br>_______________________________________________<br>
ogpx mailing list<br>
<a href=3D"mailto:ogpx@ietf.org" target=3D"_blank">ogpx@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ogpx</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br>

--0016e6d77e32832edb047989e992--

From meadhbh.siobhan@gmail.com  Sun Nov 29 14:38:36 2009
Return-Path: <meadhbh.siobhan@gmail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AB793A69F5 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 14:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 8FKZgIXrBeBu for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 14:38:35 -0800 (PST)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id EDFB33A6814 for <ogpx@ietf.org>; Sun, 29 Nov 2009 14:38:34 -0800 (PST)
Received: by pwi6 with SMTP id 6so1908585pwi.29 for <ogpx@ietf.org>; Sun, 29 Nov 2009 14:38:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=mOJS1XlM1kmTVLt1A8LQRwgKD/YWSbKgz3acU/NIldU=; b=k5SZ59mUjYbtSrAl1cPLSbQWWx+u5i8kCYL2pugTgNp9dE4JwvTow9gPwG7q9l4JiR 2BCkdHpLw6XwmGtDjaT0IKITReXDeMmm6HZjTfWTPOLeCfLRVLZdVs/OTgqd6zlmAIVO MG38ihQV0eW3muuV3A7YC/ed/Mtzwbg9UmlrM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Tc6QQUWBIRBZvDgJyp7cEwLZglzf4bJQcmibqdG06Lh47xQk0DdYNsRyK9FaB0yMsI o8Wkw902u4C8AiP4fqFXmkdB0GO/L6hQlSRsbC13T1Zrq6iks3dH3lsRMpqw8voyWCCI VOdSoERFE2DsVyua72sKys/djdYUmPgpsNpfk=
MIME-Version: 1.0
Received: by 10.115.100.30 with SMTP id c30mr5625183wam.211.1259534305861;  Sun, 29 Nov 2009 14:38:25 -0800 (PST)
In-Reply-To: <e0b04bba0911291419p7aadc9cfw752c52e939cc73c7@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com> <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com> <3a880e2c0911291011k3abcdff6webdf3c842a880100@mail.gmail.com> <e0b04bba0911291419p7aadc9cfw752c52e939cc73c7@mail.gmail.com>
Date: Sun, 29 Nov 2009 14:38:25 -0800
Message-ID: <b8ef0a220911291438u6992ef95p50c34863953e0b49@mail.gmail.com>
From: Meadhbh Hamrick <meadhbh.siobhan@gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ogpx@ietf.org
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Nov 2009 22:38:36 -0000

morgaine.

the scope of this working group is defined in the charter.

if the charter is unclear to you, re-read the discussions on the ogpx
mailing list and the commentary in the stockholm BoF session MP3
archive and the minutes from that meeting.

you do not need my permission (or anyone else's) to take apart the
intro draft point by point. and indeed, this is a place where it is
appropriate to do this. it may be advantageous to you to also take
apart other documents (like david's deployment patterns draft.)

however, i am not waiting for you to take this step. i, and my
co-authors, are working on additional revisions of previous drafts. i,
and my co-authors, have decided that we want to get input from people
who have implemented the LLSD draft and the OGP auth and teleport
drafts before seeking input from people who have not. we feel that
incorporating the experience of people who have implemented previous
revisions of the specifications will lead to a better document.

you may, at any time, comment on your experience implementing and
deploying LLSD related services including the authentication service
and teleport. you may, at any time, without prior approval, comment on
this list your thoughts about the architecture of proposed services
such as the asset service, the trust model, profile services for
avatars, etc. i am interested in your thoughts about deployment
patterns, and they will be reflected in the upcoming intro and goals
draft.

however, in the same way that i do not ask for prior editorial control
of your comments, i ask that you do not ask for editorial control of
my comments and work output. it is a requirement that any document we
produce reflect the consensus of this group. since david and i are the
co-authors of the intro and goals draft, it is our responsibility to
attempt to incorporate everyone's requirements (including yours.)

but i ask that you allow us to produce the document before you criticize it=
.

-sincerely
-meadhbh hamrick (aka infinity linden)

On Sun, Nov 29, 2009 at 2:19 PM, Morgaine
<morgaine.dinova@googlemail.com> wrote:
> On the Intro, a good place to start would be to take the document apart
> top-down, get agreement on its scope and on what is NOT to be included
> because it belongs in more detailed documents, agree on appropriate
> sections, and fill them in --- largely from the old OGP material modified=
 as
> appropriate, I hope.=A0 (This is how we made good progress on the charter
> too.) =A0 Another possibility is to leave the Intro until last, once we k=
now
> all the material that it's meant to introduce in overview --- it may be f=
ar
> too early now because so much is changing.
>
> On the "coordination with Cable Beach", really that should start with Joh=
n
> giving us some idea here of how he sees Cable Beach and VWRAP dovetailing=
.
> Cable Beach was announced=A0 on the MMOX list , yet we have been told on =
many
> occasions that the material on MMOX is (by definition) out of scope of
> OGPX/VWRAP, so there would seem to be some confusion about MMOX vs OGPX
> scopes here if we're "coordinating with CB".
>
> Cable Beach was developed independently by John's team at Intel.=A0 An ea=
rly
> version was incorporated into Opensim, and most recently the realXtend
> mailing list has mentioned that Cable Beach is evolving to integrate into
> realXtend's new system design with its WebDAV-powered inventories, as I
> reported here earlier .=A0 This is all extremely interesting and even exc=
iting
> in the rapid progress it shows, but it does beg the question of how progr=
ess
> in VWRAP fits in with everyone else's ongoing evolution.=A0 CB is not any=
 kind
> of standard after all, it's Work In Progress, and at a rather early stage=
 of
> its design, so dependence on it needs to be explained.
>
> Back in September, John said "I can't personally commit any development
> effort to VWRAP work at this time, but I will continue to periodically sy=
nc
> Intel's Cable Beach work with the VWRAP work and aim for a merging of
> features in the future".=A0 That seemed to suggest that CB would follow V=
WRAP,
> but it left a lot unsaid.=A0 We had not even considered multiple asset
> services and policy-determining regions back then.=A0 Is it still on trac=
k to
> follow us?=A0 What exactly is the dependency between our two projects?
>
> Personally I am very happy to see OGP take on in VWRAP a more embracing
> concept of interop than its original narrow one, but this does need a lot=
 of
> clarification so that we know exactly what we're doing and why, since our
> charter was made a narrow one on purpose.=A0 I welcome the new breadth, b=
ut we
> need to state what we're doing clearly and openly, and explain our new sc=
ope
> and dependencies.
>
>
> Morgaine.
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>
> On Sun, Nov 29, 2009 at 6:11 PM, Infinity Linden (Meadhbh Hamrick)
> <infinity@lindenlab.com> wrote:
>>
>> what issues do you wish to discuss, specifically, morgaine?
>> --
>> =A0 infinity linden (aka meadhbh hamrick) =A0* =A0it's pronounced "maeve=
"
>> =A0 =A0 =A0 =A0 http://wiki.secondlife.com/wiki/User:Infinity_Linden
>>
>>
>> On Sun, Nov 29, 2009 at 09:13, Morgaine <morgaine.dinova@googlemail.com>
>> wrote:
>>>
>>> Might I suggest that, instead of working on several documents behind
>>> closed doors, that those documents be worked on one at a time right her=
e in
>>> the VWRAP list where that effort belongs?
>>>
>>> That was how we managed to arrive at a group charter in a timely fashio=
n,
>>> by focusing on one thing at a time so that the whole group could contri=
bute
>>> meaningfully in a linear discussion.=A0 The documents are not independe=
nt of
>>> each other, so writing a number of them simultaneously just creates ine=
rtia
>>> in the process of change and promotes a desire for rubber-stamping, whi=
ch
>>> isn't going to happen.
>>>
>>> The Intro document requires a very large number of changes as a result =
of
>>> our removal of "one world" wording from the charter, for consistency an=
d
>>> clarity and to avoid the question of "Which world?" at any given time.
>>>
>>> Our protocol is very different now from the early days of OGP.=A0 In
>>> effect, it treats every region domain (and potentially every region) as=
 a
>>> separate world, since they can each have local policies, separate asset
>>> services, and so on --- in other words, there is no longer any single w=
orld,
>>> which is why we found an easy basis for agreement in the charter.=A0 Th=
e
>>> documents need to reflect that, starting from the Intro.
>>>
>>> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick
>>> <meadhbh.siobhan@gmail.com> wrote:
>>>
>>> The Assets draft is in a much more "complicated" state. We're
>>> coordinating our efforts with John Hurliman who's the lead developer
>>> on the Cable Beach project. We hope that what will emerge will be a
>>> unified protocol for accessing second life resources as cable beach
>>> resources.
>>>
>>> The right place for coordinating this is VWRAP, so that decisions made =
in
>>> the name of "coordination" obtain early input from the VWRAP contributo=
rs.
>>> That's what we're here for.
>>>
>>> In particular, we have already been discussing the operation of multipl=
e
>>> asset services right here with Joshua, so how this might work in conjun=
ction
>>> with Cable Beach is a matter of much interest to us.=A0 There are bound=
 to be
>>> numerous alternative approaches, so I recommend that they be discussed
>>> openly here with a lot of eyeballs on the problem, while ideas are stil=
l
>>> fluid.
>>>
>>>
>>> Morgaine.
>>>
>>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick
>>> <meadhbh.siobhan@gmail.com> wrote:
>>>>
>>>> yes, VWRAP _is_ still alive.
>>>>
>>>> we're currently working on three documents: LLSD / LLIDL, Intro and
>>>> Requirements, and Assets
>>>>
>>>> * LLSD / LLIDL
>>>>
>>>> LLIDL was in the middle of getting a well deserved face lift when
>>>> multiple, conflicting changes forced us to return to agreeing on the
>>>> problem definition instead of pushing out a draft. LLIDL / LLSD draft
>>>> development has been being informed by several pairwise / intense
>>>> descussions involving investigation of specific use cases. i hope to
>>>> get a wiki page up describing proposed changes at the end of this
>>>> week.
>>>>
>>>> but essentially what we're looking at is thus:
>>>>
>>>> - peeps didn't grok why LLSD has the "you get the default value when
>>>> you read a map key that's not there" semantics, so i'm integrating the
>>>> "structure and interpretation of LLSD messages" email into the draft
>>>> as motivation for why LLSD is needed. (
>>>> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
>>>>
>>>> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
>>>> enough." i'm developing a proposal for making LLIDL look more like an
>>>> ALGOL derived language so C/C++/C#/Java programmers can look at it and
>>>> have a more immediate understanding of what it's doing.
>>>>
>>>> - we want to be able to support GETs as well as POSTs when LLSD is
>>>> carried over HTTP(S). this is so we an make use of intermediaries like
>>>> caching squid servers. so we're working on a way to map a resource
>>>> definition to a GET instead of a POST. i know there are some people
>>>> who want to carry LLSD over XMPP, so we're interested in avoiding
>>>> simply saying... "oh... just make this kind of message a GET" since
>>>> that's more of a HTTP(S) specific construction.
>>>>
>>>> - related to the item above, we're looking at ways to encode a request
>>>> as a query string. the idea here being that since some caching
>>>> intermediaries can cache two GET requests with the same URL, including
>>>> the query string, we want to be able to encode the request in the
>>>> query string to take advantage of the caching behavior.
>>>>
>>>> - some people thought that the variant syntax was confusing.
>>>> specifically, the relationship =A0between a variant record and the
>>>> selector. (the selector is the element _in_ the variant map
>>>> declaration that has a literal value.) in other words, the way the
>>>> LLIDL parser knows that a particular variant is "valid" is that one of
>>>> the members of the map has a specific value. the relationship to the
>>>> variant and the selector was considered "haphazard" by some reviewers.
>>>>
>>>> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
>>>> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
>>>> map declaration indicates that there'll be a number of keys, the
>>>> symbol for each is determined at message send time, not at resource
>>>> definition time.
>>>>
>>>> - fixing things like broken XML DTDs.
>>>>
>>>> - changing the comment character from a semi-colon (';') to a hash mar=
k
>>>> ('#')
>>>>
>>>> * Intro and Goals
>>>>
>>>> There was a lot of commentary on the original "intro and requirements"
>>>> doc in Stockholm, and a trickle of interest since then. There are a
>>>> few minor changes to the draft, and the inclusion of a much better
>>>> glossary. David is writing a section on deployment patterns, and we
>>>> plan to integrate our changes "any day now."
>>>>
>>>> * Assets
>>>>
>>>> The Assets draft is in a much more "complicated" state. We're
>>>> coordinating our efforts with John Hurliman who's the lead developer
>>>> on the Cable Beach project. We hope that what will emerge will be a
>>>> unified protocol for accessing second life resources as cable beach
>>>> resources.
>>>>
>>>> -cheers
>>>> -meadhbh
>>>>
>>>> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <vaughn.deluca@gmail.co=
m>
>>>> wrote:
>>>> > It has gotten terribly silent on the list, and its not hard to see
>>>> > why;
>>>> > without updates of the drafts the discussion floats free and people
>>>> > are
>>>> > bound to loose interest.
>>>> > I =A0do understand that drafting these types of documents takes time=
,
>>>> > and too
>>>> > much discussion in an early stage sometimes only complicates matters=
,
>>>> > yet, a
>>>> > quick status update and maybe even a working version of the drafts i=
n
>>>> > their
>>>> > current form would be nice to keep everybody synchronised...
>>>> > -Vaughn
>>>> > _______________________________________________
>>>> > ogpx mailing list
>>>> > ogpx@ietf.org
>>>> > https://www.ietf.org/mailman/listinfo/ogpx
>>>> >
>>>> >
>>>> _______________________________________________
>>>> ogpx mailing list
>>>> ogpx@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ogpx
>>>
>>>
>>> _______________________________________________
>>> ogpx mailing list
>>> ogpx@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ogpx
>>>
>>
>
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>

From morgaine.dinova@googlemail.com  Sun Nov 29 19:05:23 2009
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 307F43A67B1 for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 19:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.768
X-Spam-Level: 
X-Spam-Status: No, score=-1.768 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 KAWd4uXVgWIA for <ogpx@core3.amsl.com>; Sun, 29 Nov 2009 19:05:20 -0800 (PST)
Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com [209.85.219.215]) by core3.amsl.com (Postfix) with ESMTP id 9ABB13A67AC for <ogpx@ietf.org>; Sun, 29 Nov 2009 19:05:19 -0800 (PST)
Received: by ewy7 with SMTP id 7so4006765ewy.28 for <ogpx@ietf.org>; Sun, 29 Nov 2009 19:05:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=8eLlg2Lqbg7lFX5sI0dUbXodl7Zt+uB6+a9xnxRlpfs=; b=I7FXZDNTm64GQk8yEPUWHb1clqdIfLmZwARdkfYcolko1oYSL6Km7GO5qT5IkbMLEg qn3OFu4e8phylwwBIRoULHA2ZilvQMUj7nvQ8lhOjzmdBipZy5qfcz+iy7hnX5lJ+yb/ b/LhcSlbVjt4H4DxEKeF1Uk94Yjhs4GcGc25g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=mW9iLUR0AaqGRHry4I0a9XbahJYXNnQ5SbHSZiHffde2ae2FiOqszwLCDM3yWOWAfH xLfoLzkLCbrwH8HE1jdpjB2nX1nrkLmLQ+YoHjd/rBGXeif72/kzSvos0mFnXgE6Bylm N+mEZtna53hDMZ3aCXMmWThzt0DKsmDiUHYOw=
MIME-Version: 1.0
Received: by 10.216.88.138 with SMTP id a10mr1245049wef.163.1259550307565;  Sun, 29 Nov 2009 19:05:07 -0800 (PST)
In-Reply-To: <b8ef0a220911291438u6992ef95p50c34863953e0b49@mail.gmail.com>
References: <9b8a8de40911290542l3f6ff7a4pd00a9d5337a04962@mail.gmail.com> <b8ef0a220911290631n2531ea14y85fc5c1b17944f4d@mail.gmail.com> <e0b04bba0911290913i1770044bs7445e0ed6c09ee53@mail.gmail.com> <3a880e2c0911291011k3abcdff6webdf3c842a880100@mail.gmail.com> <e0b04bba0911291419p7aadc9cfw752c52e939cc73c7@mail.gmail.com> <b8ef0a220911291438u6992ef95p50c34863953e0b49@mail.gmail.com>
Date: Mon, 30 Nov 2009 03:05:07 +0000
Message-ID: <e0b04bba0911291905i66f850eeg1b2a1eedc995f5c3@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d77e7aa8c37304798de812
Subject: Re: [ogpx] VWRAP still alive?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2009 03:05:23 -0000

--0016e6d77e7aa8c37304798de812
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Nov 29, 2009 at 10:38 PM, Meadhbh Hamrick <meadhbh.siobhan@gmail.com
> wrote:

>
> the scope of this working group is defined in the charter.
>
> if the charter is unclear to you, re-read the discussions on the ogpx
> mailing list and the commentary in the stockholm BoF session MP3
> archive and the minutes from that meeting.
>


Is there a need for this kind of response, and a poorly veiled insult about
not understanding the charter that we all put together as a team?

Please refrain from attacking people in this working group, either directly
or indirectly.  It's not professional, it does not advance our work, and we
just don't need it.

Our charter is quite clear, and equally clear is the split that we have
chosen to make between OGPX and MMOX --- indeed, it has been yourself who
has most often used the tactic of dismissing topics as "belonging in MMOX".
The split has been very useful I think, precisely because it narrowed the
scope of OGPX.  When it's broadened again, we need to know why.

The fact that Cable Beach was announced in MMOX and was never a part of OGP
during the two years of our AWG effort makes the question of its place in
VWRAP a real one.  The natural assumption would be that CB is out of scope,
unless stated otherwise.  If it is in scope for VWRAP then let's be clear
about it and describe why this is so.  And let's detail for everyone's
benefit why it is that we are coordinating with a particular group that is
designing a new interop mechanism.  (All kudos to John for doing this, but
CB is being designed in his team and VWRAP participants have no say on its
design, so clearly it's not an integral part of VWRAP and its relationship
to VWRAP is completely unknown.)

My own opinion is that Cable Beach is setting the pace in this area (in
conjunction with realXtend).  In contrast, it is a matter of fact that the
OGP team never publicly released a design for decoupled and distributed
asset sevices of any sort whatsoever.  Therefore I would guess that we are
reaching out to Cable Beach as the only solution on the table at this time.
Is this so?

That's my guess, but other people probably have other guesses.  Well let's
stop guessing and actually state *why* we are coordinating with John's
project, what the dependency with Cable Beach is, and how the VWRAP team is
going to be involved with dovetailing with CB, if that is our future.  The
charter may also have to be amended to reflect this integration with a new
protocol that is not an Internet standard.  In addition, we may also need
new deliverables to describe our interfaces to such external services.


Morgaine.





=====================================

On Sun, Nov 29, 2009 at 10:38 PM, Meadhbh Hamrick <meadhbh.siobhan@gmail.com
> wrote:

> morgaine.
>
> the scope of this working group is defined in the charter.
>
> if the charter is unclear to you, re-read the discussions on the ogpx
> mailing list and the commentary in the stockholm BoF session MP3
> archive and the minutes from that meeting.
>
> you do not need my permission (or anyone else's) to take apart the
> intro draft point by point. and indeed, this is a place where it is
> appropriate to do this. it may be advantageous to you to also take
> apart other documents (like david's deployment patterns draft.)
>
> however, i am not waiting for you to take this step. i, and my
> co-authors, are working on additional revisions of previous drafts. i,
> and my co-authors, have decided that we want to get input from people
> who have implemented the LLSD draft and the OGP auth and teleport
> drafts before seeking input from people who have not. we feel that
> incorporating the experience of people who have implemented previous
> revisions of the specifications will lead to a better document.
>
> you may, at any time, comment on your experience implementing and
> deploying LLSD related services including the authentication service
> and teleport. you may, at any time, without prior approval, comment on
> this list your thoughts about the architecture of proposed services
> such as the asset service, the trust model, profile services for
> avatars, etc. i am interested in your thoughts about deployment
> patterns, and they will be reflected in the upcoming intro and goals
> draft.
>
> however, in the same way that i do not ask for prior editorial control
> of your comments, i ask that you do not ask for editorial control of
> my comments and work output. it is a requirement that any document we
> produce reflect the consensus of this group. since david and i are the
> co-authors of the intro and goals draft, it is our responsibility to
> attempt to incorporate everyone's requirements (including yours.)
>
> but i ask that you allow us to produce the document before you criticize
> it.
>
> -sincerely
> -meadhbh hamrick (aka infinity linden)
>
> On Sun, Nov 29, 2009 at 2:19 PM, Morgaine
> <morgaine.dinova@googlemail.com> wrote:
> > On the Intro, a good place to start would be to take the document apart
> > top-down, get agreement on its scope and on what is NOT to be included
> > because it belongs in more detailed documents, agree on appropriate
> > sections, and fill them in --- largely from the old OGP material modified
> as
> > appropriate, I hope.  (This is how we made good progress on the charter
> > too.)   Another possibility is to leave the Intro until last, once we
> know
> > all the material that it's meant to introduce in overview --- it may be
> far
> > too early now because so much is changing.
> >
> > On the "coordination with Cable Beach", really that should start with
> John
> > giving us some idea here of how he sees Cable Beach and VWRAP
> dovetailing.
> > Cable Beach was announced  on the MMOX list , yet we have been told on
> many
> > occasions that the material on MMOX is (by definition) out of scope of
> > OGPX/VWRAP, so there would seem to be some confusion about MMOX vs OGPX
> > scopes here if we're "coordinating with CB".
> >
> > Cable Beach was developed independently by John's team at Intel.  An
> early
> > version was incorporated into Opensim, and most recently the realXtend
> > mailing list has mentioned that Cable Beach is evolving to integrate into
> > realXtend's new system design with its WebDAV-powered inventories, as I
> > reported here earlier .  This is all extremely interesting and even
> exciting
> > in the rapid progress it shows, but it does beg the question of how
> progress
> > in VWRAP fits in with everyone else's ongoing evolution.  CB is not any
> kind
> > of standard after all, it's Work In Progress, and at a rather early stage
> of
> > its design, so dependence on it needs to be explained.
> >
> > Back in September, John said "I can't personally commit any development
> > effort to VWRAP work at this time, but I will continue to periodically
> sync
> > Intel's Cable Beach work with the VWRAP work and aim for a merging of
> > features in the future".  That seemed to suggest that CB would follow
> VWRAP,
> > but it left a lot unsaid.  We had not even considered multiple asset
> > services and policy-determining regions back then.  Is it still on track
> to
> > follow us?  What exactly is the dependency between our two projects?
> >
> > Personally I am very happy to see OGP take on in VWRAP a more embracing
> > concept of interop than its original narrow one, but this does need a lot
> of
> > clarification so that we know exactly what we're doing and why, since our
> > charter was made a narrow one on purpose.  I welcome the new breadth, but
> we
> > need to state what we're doing clearly and openly, and explain our new
> scope
> > and dependencies.
> >
> >
> > Morgaine.
> >
> >
> >
> >
> > =============================
> >
> > On Sun, Nov 29, 2009 at 6:11 PM, Infinity Linden (Meadhbh Hamrick)
> > <infinity@lindenlab.com> wrote:
> >>
> >> what issues do you wish to discuss, specifically, morgaine?
> >> --
> >>   infinity linden (aka meadhbh hamrick)  *  it's pronounced "maeve"
> >>         http://wiki.secondlife.com/wiki/User:Infinity_Linden
> >>
> >>
> >> On Sun, Nov 29, 2009 at 09:13, Morgaine <morgaine.dinova@googlemail.com
> >
> >> wrote:
> >>>
> >>> Might I suggest that, instead of working on several documents behind
> >>> closed doors, that those documents be worked on one at a time right
> here in
> >>> the VWRAP list where that effort belongs?
> >>>
> >>> That was how we managed to arrive at a group charter in a timely
> fashion,
> >>> by focusing on one thing at a time so that the whole group could
> contribute
> >>> meaningfully in a linear discussion.  The documents are not independent
> of
> >>> each other, so writing a number of them simultaneously just creates
> inertia
> >>> in the process of change and promotes a desire for rubber-stamping,
> which
> >>> isn't going to happen.
> >>>
> >>> The Intro document requires a very large number of changes as a result
> of
> >>> our removal of "one world" wording from the charter, for consistency
> and
> >>> clarity and to avoid the question of "Which world?" at any given time.
> >>>
> >>> Our protocol is very different now from the early days of OGP.  In
> >>> effect, it treats every region domain (and potentially every region) as
> a
> >>> separate world, since they can each have local policies, separate asset
> >>> services, and so on --- in other words, there is no longer any single
> world,
> >>> which is why we found an easy basis for agreement in the charter.  The
> >>> documents need to reflect that, starting from the Intro.
> >>>
> >>> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick
> >>> <meadhbh.siobhan@gmail.com> wrote:
> >>>
> >>> The Assets draft is in a much more "complicated" state. We're
> >>> coordinating our efforts with John Hurliman who's the lead developer
> >>> on the Cable Beach project. We hope that what will emerge will be a
> >>> unified protocol for accessing second life resources as cable beach
> >>> resources.
> >>>
> >>> The right place for coordinating this is VWRAP, so that decisions made
> in
> >>> the name of "coordination" obtain early input from the VWRAP
> contributors.
> >>> That's what we're here for.
> >>>
> >>> In particular, we have already been discussing the operation of
> multiple
> >>> asset services right here with Joshua, so how this might work in
> conjunction
> >>> with Cable Beach is a matter of much interest to us.  There are bound
> to be
> >>> numerous alternative approaches, so I recommend that they be discussed
> >>> openly here with a lot of eyeballs on the problem, while ideas are
> still
> >>> fluid.
> >>>
> >>>
> >>> Morgaine.
> >>>
> >>>
> >>> ==========================================
> >>>
> >>> On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick
> >>> <meadhbh.siobhan@gmail.com> wrote:
> >>>>
> >>>> yes, VWRAP _is_ still alive.
> >>>>
> >>>> we're currently working on three documents: LLSD / LLIDL, Intro and
> >>>> Requirements, and Assets
> >>>>
> >>>> * LLSD / LLIDL
> >>>>
> >>>> LLIDL was in the middle of getting a well deserved face lift when
> >>>> multiple, conflicting changes forced us to return to agreeing on the
> >>>> problem definition instead of pushing out a draft. LLIDL / LLSD draft
> >>>> development has been being informed by several pairwise / intense
> >>>> descussions involving investigation of specific use cases. i hope to
> >>>> get a wiki page up describing proposed changes at the end of this
> >>>> week.
> >>>>
> >>>> but essentially what we're looking at is thus:
> >>>>
> >>>> - peeps didn't grok why LLSD has the "you get the default value when
> >>>> you read a map key that's not there" semantics, so i'm integrating the
> >>>> "structure and interpretation of LLSD messages" email into the draft
> >>>> as motivation for why LLSD is needed. (
> >>>> http://www.ietf.org/mail-archive/web/mmox/current/msg00679.html )
> >>>>
> >>>> - peeps thought the LLIDL syntax was odd, that it didn't look "Cish
> >>>> enough." i'm developing a proposal for making LLIDL look more like an
> >>>> ALGOL derived language so C/C++/C#/Java programmers can look at it and
> >>>> have a more immediate understanding of what it's doing.
> >>>>
> >>>> - we want to be able to support GETs as well as POSTs when LLSD is
> >>>> carried over HTTP(S). this is so we an make use of intermediaries like
> >>>> caching squid servers. so we're working on a way to map a resource
> >>>> definition to a GET instead of a POST. i know there are some people
> >>>> who want to carry LLSD over XMPP, so we're interested in avoiding
> >>>> simply saying... "oh... just make this kind of message a GET" since
> >>>> that's more of a HTTP(S) specific construction.
> >>>>
> >>>> - related to the item above, we're looking at ways to encode a request
> >>>> as a query string. the idea here being that since some caching
> >>>> intermediaries can cache two GET requests with the same URL, including
> >>>> the query string, we want to be able to encode the request in the
> >>>> query string to take advantage of the caching behavior.
> >>>>
> >>>> - some people thought that the variant syntax was confusing.
> >>>> specifically, the relationship  between a variant record and the
> >>>> selector. (the selector is the element _in_ the variant map
> >>>> declaration that has a literal value.) in other words, the way the
> >>>> LLIDL parser knows that a particular variant is "valid" is that one of
> >>>> the members of the map has a specific value. the relationship to the
> >>>> variant and the selector was considered "haphazard" by some reviewers.
> >>>>
> >>>> - explaining the use of "late keys." i.e. - the '$' in some LLIDL
> >>>> definitions. the use of the dollar sign ('$') in LLIDL as the key of a
> >>>> map declaration indicates that there'll be a number of keys, the
> >>>> symbol for each is determined at message send time, not at resource
> >>>> definition time.
> >>>>
> >>>> - fixing things like broken XML DTDs.
> >>>>
> >>>> - changing the comment character from a semi-colon (';') to a hash
> mark
> >>>> ('#')
> >>>>
> >>>> * Intro and Goals
> >>>>
> >>>> There was a lot of commentary on the original "intro and requirements"
> >>>> doc in Stockholm, and a trickle of interest since then. There are a
> >>>> few minor changes to the draft, and the inclusion of a much better
> >>>> glossary. David is writing a section on deployment patterns, and we
> >>>> plan to integrate our changes "any day now."
> >>>>
> >>>> * Assets
> >>>>
> >>>> The Assets draft is in a much more "complicated" state. We're
> >>>> coordinating our efforts with John Hurliman who's the lead developer
> >>>> on the Cable Beach project. We hope that what will emerge will be a
> >>>> unified protocol for accessing second life resources as cable beach
> >>>> resources.
> >>>>
> >>>> -cheers
> >>>> -meadhbh
> >>>>
> >>>> On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca <
> vaughn.deluca@gmail.com>
> >>>> wrote:
> >>>> > It has gotten terribly silent on the list, and its not hard to see
> >>>> > why;
> >>>> > without updates of the drafts the discussion floats free and people
> >>>> > are
> >>>> > bound to loose interest.
> >>>> > I  do understand that drafting these types of documents takes time,
> >>>> > and too
> >>>> > much discussion in an early stage sometimes only complicates
> matters,
> >>>> > yet, a
> >>>> > quick status update and maybe even a working version of the drafts
> in
> >>>> > their
> >>>> > current form would be nice to keep everybody synchronised...
> >>>> > -Vaughn
> >>>> > _______________________________________________
> >>>> > ogpx mailing list
> >>>> > ogpx@ietf.org
> >>>> > https://www.ietf.org/mailman/listinfo/ogpx
> >>>> >
> >>>> >
> >>>> _______________________________________________
> >>>> ogpx mailing list
> >>>> ogpx@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/ogpx
> >>>
> >>>
> >>> _______________________________________________
> >>> ogpx mailing list
> >>> ogpx@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/ogpx
> >>>
> >>
> >
> >
> > _______________________________________________
> > ogpx mailing list
> > ogpx@ietf.org
> > https://www.ietf.org/mailman/listinfo/ogpx
> >
> >
>

--0016e6d77e7aa8c37304798de812
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 29, 2009 at 10:38 PM, Meadhbh Hamrick <span dir=3D"ltr">&lt;<a =
href=3D"mailto:meadhbh.siobhan@gmail.com">meadhbh.siobhan@gmail.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"border-left: 1=
px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"=
>

<br><div style=3D"margin-left: 40px;">
the scope of this working group is defined in the charter.<br><br>
if the charter is unclear to you, re-read the discussions on the ogpx<br>
mailing list and the commentary in the stockholm BoF session MP3<br>
archive and the minutes from that meeting.</div>
</blockquote><br><br>Is there a need for this kind of response, and a poorl=
y veiled insult about not understanding the charter that we all put togethe=
r as a team?<br><br>Please refrain from attacking people in this working gr=
oup, either directly or indirectly.=A0 It&#39;s not professional, it does n=
ot advance our work, and we just don&#39;t need it.<br>
<br>Our charter is quite clear, and equally clear is the split that we have=
 chosen to make between OGPX and MMOX --- indeed, it has been yourself who =
has most often used the tactic of dismissing topics as &quot;belonging in M=
MOX&quot;.=A0 The split has been very useful I think, precisely because it =
narrowed the scope of OGPX.=A0 When it&#39;s broadened again, we need to kn=
ow why.<br>
<br>The fact that Cable Beach was announced in MMOX and was never a part of=
 OGP during the two years of our AWG effort makes the question of its place=
 in VWRAP a real one.=A0 The natural assumption would be that CB is out of =
scope, unless stated otherwise.=A0 If it is in scope for VWRAP then let&#39=
;s be clear about it and describe why this is so.=A0 And let&#39;s detail f=
or everyone&#39;s benefit why it is that we are coordinating with a particu=
lar group that is designing a new interop mechanism.=A0 (All kudos to John =
for doing this, but CB is being designed in his team and VWRAP participants=
 have no say on its design, so clearly it&#39;s not an integral part of VWR=
AP and its relationship to VWRAP is completely unknown.)<br>
<br>My own opinion is that Cable Beach is setting the pace in this area (in=
 conjunction with realXtend).=A0 In contrast, it is a matter of fact that t=
he OGP team never publicly released a design for decoupled and distributed =
asset sevices of any sort whatsoever.=A0 Therefore I would guess that we ar=
e reaching out to Cable Beach as the only solution on the table at this tim=
e.=A0 Is this so?<br>
<br>That&#39;s my guess, but other people probably have other guesses.=A0 W=
ell let&#39;s stop guessing and actually state <i><b>why</b></i> we are coo=
rdinating with John&#39;s project, what the dependency with Cable Beach is,=
 and how the VWRAP team is going to be involved with dovetailing with CB, i=
f that is our future.=A0 The charter may also have to be amended to reflect=
 this integration with a new protocol that is not an Internet standard.=A0 =
In addition, we may also need new deliverables to describe our interfaces t=
o such external services.<br>
<br><br>Morgaine.<br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<br><br><div class=3D"gmail_quote">On Sun, Nov 29, 2009 at 10:38 PM, Mea=
dhbh Hamrick <span dir=3D"ltr">&lt;<a href=3D"mailto:meadhbh.siobhan@gmail.=
com">meadhbh.siobhan@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">morgaine.<br>
<br>
the scope of this working group is defined in the charter.<br>
<br>
if the charter is unclear to you, re-read the discussions on the ogpx<br>
mailing list and the commentary in the stockholm BoF session MP3<br>
archive and the minutes from that meeting.<br>
<br>
you do not need my permission (or anyone else&#39;s) to take apart the<br>
intro draft point by point. and indeed, this is a place where it is<br>
appropriate to do this. it may be advantageous to you to also take<br>
apart other documents (like david&#39;s deployment patterns draft.)<br>
<br>
however, i am not waiting for you to take this step. i, and my<br>
co-authors, are working on additional revisions of previous drafts. i,<br>
and my co-authors, have decided that we want to get input from people<br>
who have implemented the LLSD draft and the OGP auth and teleport<br>
drafts before seeking input from people who have not. we feel that<br>
incorporating the experience of people who have implemented previous<br>
revisions of the specifications will lead to a better document.<br>
<br>
you may, at any time, comment on your experience implementing and<br>
deploying LLSD related services including the authentication service<br>
and teleport. you may, at any time, without prior approval, comment on<br>
this list your thoughts about the architecture of proposed services<br>
such as the asset service, the trust model, profile services for<br>
avatars, etc. i am interested in your thoughts about deployment<br>
patterns, and they will be reflected in the upcoming intro and goals<br>
draft.<br>
<br>
however, in the same way that i do not ask for prior editorial control<br>
of your comments, i ask that you do not ask for editorial control of<br>
my comments and work output. it is a requirement that any document we<br>
produce reflect the consensus of this group. since david and i are the<br>
co-authors of the intro and goals draft, it is our responsibility to<br>
attempt to incorporate everyone&#39;s requirements (including yours.)<br>
<br>
but i ask that you allow us to produce the document before you criticize it=
.<br>
<br>
-sincerely<br>
-meadhbh hamrick (aka infinity linden)<br>
<br>
On Sun, Nov 29, 2009 at 2:19 PM, Morgaine<br>
<div><div></div><div class=3D"h5">&lt;<a href=3D"mailto:morgaine.dinova@goo=
glemail.com">morgaine.dinova@googlemail.com</a>&gt; wrote:<br>
&gt; On the Intro, a good place to start would be to take the document apar=
t<br>
&gt; top-down, get agreement on its scope and on what is NOT to be included=
<br>
&gt; because it belongs in more detailed documents, agree on appropriate<br=
>
&gt; sections, and fill them in --- largely from the old OGP material modif=
ied as<br>
&gt; appropriate, I hope.=A0 (This is how we made good progress on the char=
ter<br>
&gt; too.) =A0 Another possibility is to leave the Intro until last, once w=
e know<br>
&gt; all the material that it&#39;s meant to introduce in overview --- it m=
ay be far<br>
&gt; too early now because so much is changing.<br>
&gt;<br>
&gt; On the &quot;coordination with Cable Beach&quot;, really that should s=
tart with John<br>
&gt; giving us some idea here of how he sees Cable Beach and VWRAP dovetail=
ing.<br>
&gt; Cable Beach was announced=A0 on the MMOX list , yet we have been told =
on many<br>
&gt; occasions that the material on MMOX is (by definition) out of scope of=
<br>
&gt; OGPX/VWRAP, so there would seem to be some confusion about MMOX vs OGP=
X<br>
&gt; scopes here if we&#39;re &quot;coordinating with CB&quot;.<br>
&gt;<br>
&gt; Cable Beach was developed independently by John&#39;s team at Intel.=
=A0 An early<br>
&gt; version was incorporated into Opensim, and most recently the realXtend=
<br>
&gt; mailing list has mentioned that Cable Beach is evolving to integrate i=
nto<br>
&gt; realXtend&#39;s new system design with its WebDAV-powered inventories,=
 as I<br>
&gt; reported here earlier .=A0 This is all extremely interesting and even =
exciting<br>
&gt; in the rapid progress it shows, but it does beg the question of how pr=
ogress<br>
&gt; in VWRAP fits in with everyone else&#39;s ongoing evolution.=A0 CB is =
not any kind<br>
&gt; of standard after all, it&#39;s Work In Progress, and at a rather earl=
y stage of<br>
&gt; its design, so dependence on it needs to be explained.<br>
&gt;<br>
&gt; Back in September, John said &quot;I can&#39;t personally commit any d=
evelopment<br>
&gt; effort to VWRAP work at this time, but I will continue to periodically=
 sync<br>
&gt; Intel&#39;s Cable Beach work with the VWRAP work and aim for a merging=
 of<br>
&gt; features in the future&quot;.=A0 That seemed to suggest that CB would =
follow VWRAP,<br>
&gt; but it left a lot unsaid.=A0 We had not even considered multiple asset=
<br>
&gt; services and policy-determining regions back then.=A0 Is it still on t=
rack to<br>
&gt; follow us?=A0 What exactly is the dependency between our two projects?=
<br>
&gt;<br>
&gt; Personally I am very happy to see OGP take on in VWRAP a more embracin=
g<br>
&gt; concept of interop than its original narrow one, but this does need a =
lot of<br>
&gt; clarification so that we know exactly what we&#39;re doing and why, si=
nce our<br>
&gt; charter was made a narrow one on purpose.=A0 I welcome the new breadth=
, but we<br>
&gt; need to state what we&#39;re doing clearly and openly, and explain our=
 new scope<br>
&gt; and dependencies.<br>
&gt;<br>
&gt;<br>
&gt; Morgaine.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt; On Sun, Nov 29, 2009 at 6:11 PM, Infinity Linden (Meadhbh Hamrick)<br>
&gt; &lt;<a href=3D"mailto:infinity@lindenlab.com">infinity@lindenlab.com</=
a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; what issues do you wish to discuss, specifically, morgaine?<br>
&gt;&gt; --<br>
&gt;&gt; =A0 infinity linden (aka meadhbh hamrick) =A0* =A0it&#39;s pronoun=
ced &quot;maeve&quot;<br>
&gt;&gt; =A0 =A0 =A0 =A0 <a href=3D"http://wiki.secondlife.com/wiki/User:In=
finity_Linden" target=3D"_blank">http://wiki.secondlife.com/wiki/User:Infin=
ity_Linden</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Sun, Nov 29, 2009 at 09:13, Morgaine &lt;<a href=3D"mailto:morg=
aine.dinova@googlemail.com">morgaine.dinova@googlemail.com</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Might I suggest that, instead of working on several documents =
behind<br>
&gt;&gt;&gt; closed doors, that those documents be worked on one at a time =
right here in<br>
&gt;&gt;&gt; the VWRAP list where that effort belongs?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; That was how we managed to arrive at a group charter in a time=
ly fashion,<br>
&gt;&gt;&gt; by focusing on one thing at a time so that the whole group cou=
ld contribute<br>
&gt;&gt;&gt; meaningfully in a linear discussion.=A0 The documents are not =
independent of<br>
&gt;&gt;&gt; each other, so writing a number of them simultaneously just cr=
eates inertia<br>
&gt;&gt;&gt; in the process of change and promotes a desire for rubber-stam=
ping, which<br>
&gt;&gt;&gt; isn&#39;t going to happen.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The Intro document requires a very large number of changes as =
a result of<br>
&gt;&gt;&gt; our removal of &quot;one world&quot; wording from the charter,=
 for consistency and<br>
&gt;&gt;&gt; clarity and to avoid the question of &quot;Which world?&quot; =
at any given time.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Our protocol is very different now from the early days of OGP.=
=A0 In<br>
&gt;&gt;&gt; effect, it treats every region domain (and potentially every r=
egion) as a<br>
&gt;&gt;&gt; separate world, since they can each have local policies, separ=
ate asset<br>
&gt;&gt;&gt; services, and so on --- in other words, there is no longer any=
 single world,<br>
&gt;&gt;&gt; which is why we found an easy basis for agreement in the chart=
er.=A0 The<br>
&gt;&gt;&gt; documents need to reflect that, starting from the Intro.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick<br>
&gt;&gt;&gt; &lt;<a href=3D"mailto:meadhbh.siobhan@gmail.com">meadhbh.siobh=
an@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The Assets draft is in a much more &quot;complicated&quot; sta=
te. We&#39;re<br>
&gt;&gt;&gt; coordinating our efforts with John Hurliman who&#39;s the lead=
 developer<br>
&gt;&gt;&gt; on the Cable Beach project. We hope that what will emerge will=
 be a<br>
&gt;&gt;&gt; unified protocol for accessing second life resources as cable =
beach<br>
&gt;&gt;&gt; resources.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The right place for coordinating this is VWRAP, so that decisi=
ons made in<br>
&gt;&gt;&gt; the name of &quot;coordination&quot; obtain early input from t=
he VWRAP contributors.<br>
&gt;&gt;&gt; That&#39;s what we&#39;re here for.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; In particular, we have already been discussing the operation o=
f multiple<br>
&gt;&gt;&gt; asset services right here with Joshua, so how this might work =
in conjunction<br>
&gt;&gt;&gt; with Cable Beach is a matter of much interest to us.=A0 There =
are bound to be<br>
&gt;&gt;&gt; numerous alternative approaches, so I recommend that they be d=
iscussed<br>
&gt;&gt;&gt; openly here with a lot of eyeballs on the problem, while ideas=
 are still<br>
&gt;&gt;&gt; fluid.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Morgaine.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Sun, Nov 29, 2009 at 2:31 PM, Meadhbh Hamrick<br>
&gt;&gt;&gt; &lt;<a href=3D"mailto:meadhbh.siobhan@gmail.com">meadhbh.siobh=
an@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; yes, VWRAP _is_ still alive.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; we&#39;re currently working on three documents: LLSD / LLI=
DL, Intro and<br>
&gt;&gt;&gt;&gt; Requirements, and Assets<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; * LLSD / LLIDL<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; LLIDL was in the middle of getting a well deserved face li=
ft when<br>
&gt;&gt;&gt;&gt; multiple, conflicting changes forced us to return to agree=
ing on the<br>
&gt;&gt;&gt;&gt; problem definition instead of pushing out a draft. LLIDL /=
 LLSD draft<br>
&gt;&gt;&gt;&gt; development has been being informed by several pairwise / =
intense<br>
&gt;&gt;&gt;&gt; descussions involving investigation of specific use cases.=
 i hope to<br>
&gt;&gt;&gt;&gt; get a wiki page up describing proposed changes at the end =
of this<br>
&gt;&gt;&gt;&gt; week.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; but essentially what we&#39;re looking at is thus:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - peeps didn&#39;t grok why LLSD has the &quot;you get the=
 default value when<br>
&gt;&gt;&gt;&gt; you read a map key that&#39;s not there&quot; semantics, s=
o i&#39;m integrating the<br>
&gt;&gt;&gt;&gt; &quot;structure and interpretation of LLSD messages&quot; =
email into the draft<br>
&gt;&gt;&gt;&gt; as motivation for why LLSD is needed. (<br>
&gt;&gt;&gt;&gt; <a href=3D"http://www.ietf.org/mail-archive/web/mmox/curre=
nt/msg00679.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/mm=
ox/current/msg00679.html</a> )<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - peeps thought the LLIDL syntax was odd, that it didn&#39=
;t look &quot;Cish<br>
&gt;&gt;&gt;&gt; enough.&quot; i&#39;m developing a proposal for making LLI=
DL look more like an<br>
&gt;&gt;&gt;&gt; ALGOL derived language so C/C++/C#/Java programmers can lo=
ok at it and<br>
&gt;&gt;&gt;&gt; have a more immediate understanding of what it&#39;s doing=
.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - we want to be able to support GETs as well as POSTs when=
 LLSD is<br>
&gt;&gt;&gt;&gt; carried over HTTP(S). this is so we an make use of interme=
diaries like<br>
&gt;&gt;&gt;&gt; caching squid servers. so we&#39;re working on a way to ma=
p a resource<br>
&gt;&gt;&gt;&gt; definition to a GET instead of a POST. i know there are so=
me people<br>
&gt;&gt;&gt;&gt; who want to carry LLSD over XMPP, so we&#39;re interested =
in avoiding<br>
&gt;&gt;&gt;&gt; simply saying... &quot;oh... just make this kind of messag=
e a GET&quot; since<br>
&gt;&gt;&gt;&gt; that&#39;s more of a HTTP(S) specific construction.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - related to the item above, we&#39;re looking at ways to =
encode a request<br>
&gt;&gt;&gt;&gt; as a query string. the idea here being that since some cac=
hing<br>
&gt;&gt;&gt;&gt; intermediaries can cache two GET requests with the same UR=
L, including<br>
&gt;&gt;&gt;&gt; the query string, we want to be able to encode the request=
 in the<br>
&gt;&gt;&gt;&gt; query string to take advantage of the caching behavior.<br=
>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - some people thought that the variant syntax was confusin=
g.<br>
&gt;&gt;&gt;&gt; specifically, the relationship =A0between a variant record=
 and the<br>
&gt;&gt;&gt;&gt; selector. (the selector is the element _in_ the variant ma=
p<br>
&gt;&gt;&gt;&gt; declaration that has a literal value.) in other words, the=
 way the<br>
&gt;&gt;&gt;&gt; LLIDL parser knows that a particular variant is &quot;vali=
d&quot; is that one of<br>
&gt;&gt;&gt;&gt; the members of the map has a specific value. the relations=
hip to the<br>
&gt;&gt;&gt;&gt; variant and the selector was considered &quot;haphazard&qu=
ot; by some reviewers.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - explaining the use of &quot;late keys.&quot; i.e. - the =
&#39;$&#39; in some LLIDL<br>
&gt;&gt;&gt;&gt; definitions. the use of the dollar sign (&#39;$&#39;) in L=
LIDL as the key of a<br>
&gt;&gt;&gt;&gt; map declaration indicates that there&#39;ll be a number of=
 keys, the<br>
&gt;&gt;&gt;&gt; symbol for each is determined at message send time, not at=
 resource<br>
&gt;&gt;&gt;&gt; definition time.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - fixing things like broken XML DTDs.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - changing the comment character from a semi-colon (&#39;;=
&#39;) to a hash mark<br>
&gt;&gt;&gt;&gt; (&#39;#&#39;)<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; * Intro and Goals<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; There was a lot of commentary on the original &quot;intro =
and requirements&quot;<br>
&gt;&gt;&gt;&gt; doc in Stockholm, and a trickle of interest since then. Th=
ere are a<br>
&gt;&gt;&gt;&gt; few minor changes to the draft, and the inclusion of a muc=
h better<br>
&gt;&gt;&gt;&gt; glossary. David is writing a section on deployment pattern=
s, and we<br>
&gt;&gt;&gt;&gt; plan to integrate our changes &quot;any day now.&quot;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; * Assets<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The Assets draft is in a much more &quot;complicated&quot;=
 state. We&#39;re<br>
&gt;&gt;&gt;&gt; coordinating our efforts with John Hurliman who&#39;s the =
lead developer<br>
&gt;&gt;&gt;&gt; on the Cable Beach project. We hope that what will emerge =
will be a<br>
&gt;&gt;&gt;&gt; unified protocol for accessing second life resources as ca=
ble beach<br>
&gt;&gt;&gt;&gt; resources.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; -cheers<br>
&gt;&gt;&gt;&gt; -meadhbh<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On Sun, Nov 29, 2009 at 5:42 AM, Vaughn Deluca &lt;<a href=
=3D"mailto:vaughn.deluca@gmail.com">vaughn.deluca@gmail.com</a>&gt;<br>
&gt;&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt; &gt; It has gotten terribly silent on the list, and its no=
t hard to see<br>
&gt;&gt;&gt;&gt; &gt; why;<br>
&gt;&gt;&gt;&gt; &gt; without updates of the drafts the discussion floats f=
ree and people<br>
&gt;&gt;&gt;&gt; &gt; are<br>
&gt;&gt;&gt;&gt; &gt; bound to loose interest.<br>
&gt;&gt;&gt;&gt; &gt; I =A0do understand that drafting these types of docum=
ents takes time,<br>
&gt;&gt;&gt;&gt; &gt; and too<br>
&gt;&gt;&gt;&gt; &gt; much discussion in an early stage sometimes only comp=
licates matters,<br>
&gt;&gt;&gt;&gt; &gt; yet, a<br>
&gt;&gt;&gt;&gt; &gt; quick status update and maybe even a working version =
of the drafts in<br>
&gt;&gt;&gt;&gt; &gt; their<br>
&gt;&gt;&gt;&gt; &gt; current form would be nice to keep everybody synchron=
ised...<br>
&gt;&gt;&gt;&gt; &gt; -Vaughn<br>
&gt;&gt;&gt;&gt; &gt; _______________________________________________<br>
&gt;&gt;&gt;&gt; &gt; ogpx mailing list<br>
&gt;&gt;&gt;&gt; &gt; <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br=
>
&gt;&gt;&gt;&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt; ogpx mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; ogpx mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; ogpx mailing list<br>
&gt; <a href=3D"mailto:ogpx@ietf.org">ogpx@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ogpx" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ogpx</a><br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div><br>

--0016e6d77e7aa8c37304798de812--
