[vwrap] Fwd: one question

yes and no.

VWRAP is set up to develop protocols for service interoperability.

if you choose to deploy these services to render a virtual world, then
the answer is yes. but the protocol specification does not require
endpoints to be user agents.

but you could just as easily use VWRAP to, for instance, control
inworld bots. or you could have a web app that retrieves asset data
directly from an asset service and renders it using WebGL (maybe for
something like xstreetsl.)

but my answers shouldn't be a surprise, since it's clear i like the
term "service level interop."

but the use case you describe: yes. the PROTOCOLs used in the use case
are in scope. other aspects, probably not. we don't want to specify a
single internal virtual world state.

if we build a protocol where the client portion (at least) can't be
rendered with HTML5+WebGL, then i would say we've failed.

also, in the example you give, there's no reason you couldn't have an
app that spoke some VWRAP and spoke some linden legacy protocol and
some <fill in the blank>.

-cheers

--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com

On Wed, Sep 22, 2010 at 6:47 PM, Cristina Videira Lopes
<lopes@ics.uci.edu> wrote:
> Let me summarize my main puzzlement with the drafts, and with some of the
> things stated here, with one very simple yes/no question that, hopefully,
> the group will get to a consensus in no time:
>
> I have a student starting to work on a JavaScript+HTML5 viewer for
> brain-dead-simple, multi-user, OpenSimulator-served scenes. I can do that
> very easily with OpenSim, since the client protocol is a plugin. Is VWRAP
> set up to develop protocols for interoperability between virtual worlds
> that, like these ones, use the web browser as the client?
> a) Yes
> b) No
>
> People's answers?
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>