Re: [ogpx] Informal draft for discussion -- client side capabilitiesand setup flows

Still digesting, but some quick feedback:

* Re: the eventq(s) schemes - am I correct in my interpretation that 
these URIs would not be exposed outside of a single (agent, region) 
domain? If so, would these be considered a "best 
practice"/"implementation detail" rather than something normative? (The 
document is clearly discussing patterns so it's within scope for the 
document.) If not, then I'm misinterpreting something.

* For *examples* in documents, could we informally standardize on using 
JSON serialization of LLSD rather than the XML serialization? I realize 
that XML is more expressive (e.g. you can distinguish strings vs. UUIDs) 
but JSON is more compact and it avoids having non-LLSD-savvy XML-centric 
users readers from gagging at the seemingly crazy implied schema. 
(Formal interface specifications should use LLIDL.)

David W Levine wrote:
>
> This is an informal draft intended to drive some feedback and 
> discussion. The content follows the discussion a week ago, in SL at 
> the weekly AWGroupies meeting. Feedback is welcome, and encouraged, 
> here, and at next week's AWGroupy meeting. For those who do not follow 
> the weekly discussions, they are held in world, on Second Life Contact 
> Zha Ewry (me) or Saijanai Kuhn in world for an invite. The AWGroupies 
> meet Tuesday mornings at 9:30 AM Pacific time, in second life. For 
> those who do not routinely use second life, a free account is 
> available, details at the Linden Lab web site: 
> _http://secondlife.com/_   I expect the next iteration of the document 
> to be posted as an IETF input for discussion at IETF75 in Stockholm.
>
>
>
>
>
> - David Levine
> ~ Zha Ewry  (In Second Life)
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx