Re: [ogpx] revised draft charter for OGPX working group

If you look at:
http://www.ietf.org/id/draft-levine-ogp-layering-00.txt 

It begins to address this at the requirements and design pattern level. 
I'd strongly argue, that if its not clear that we want to permit the 
protocols to work properly in *all* of those deployments patterns, we need 
to update the charter to make that clear.

My personal perspective is that the OGPX specifications are going to end 
up defining several hundred "REST" and "RESTish" resources/services, and 
that grouping and we need to describe how to group and deploy them as 
deployers see fit. There re some natural clusterings which will be very 
hard to decouple, but, beyond those, the specifications should strive to 
give deployers and implementers as much flexibility as possible. 

-  David W. Levine
~ Zha Ewry, In Second Life

Kajikawa Jeremy <belxjander@gmail.com> 
Sent by: ogpx-bounces@ietf.org
07/18/2009 05:22 AM

To
ogpx@ietf.org
cc

Subject
Re: [ogpx] revised draft charter for OGPX working group

Well a sketch I recently worked up has
  AgentDomain and RegionDomain

these can be instanced...

  but both need "SI" or Service Interfaces
  basically abstracting U G A I M into classes for re-use
  and standardizing the protocol chatter

On Sat, 2009-07-18 at 11:57 +0100, Alexey Melnikov wrote:
> Hi Dave,
> 
> Dave CROCKER wrote:
> 
> > Also:  A topic that's been discussed frequently is the difference 
> > between having a client able to access multiple servers, versus having 

> > independent servers directly interact.  From the draft charter, I 
> > cannot tell which of these will be covered or how.
> 
> I think this is an important question. There are 3 groups of entities 
> involved in OGP and the charter doesn't make this clear.
> 
> _______________________________________________
> 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