[Foundation] June 13 Foundation Text Conference Agenda

[Rahul Dave]

 The idea of the JIG's is to focus on explicit issues. What are the first
 issues we need to consider for JAM? An example would be rule based routing
 or filtering, or a naming scheme for arbitrary objects inside nodes, or
 header extensions for transactional guarantees.

 My thought on this is to form these JIGS as we consider the issues involved and
 then use the JAM list, or some other one for JIG discussions. To put it another
 way, I dont think each jig needs its own mailing list, but does a jabber
 conference ( and maybe in the future a group messaging..)

 Rahul
I got this from you:
> 
> I think it's a bit early for a JAM JIG but there's probably enough
> interest in it to justify forming that group. 
> 
> I was just talking with Dizzy and Jack Erwin (a developer at jabber.com)
> and we definitely see a more immediate need for a JIG that will define the
> format for Jabber IDs. Right now the JID format (allowable characters,
> length, etc.) is undefined (or at best a bit loose), and that's a problem.
> 
> A JID-JIG isn't as glamorous as a JAM-JIG, but it's quite necessary. :)
> 
> Peter
> 
> On Tue, 12 Jun 2001, Bill Abbas wrote:
> 
> > 
> > How about a JIG for JAM?  
> > 
> > =Bill
> > _______________________________________________
> > Members mailing list
> > Members at jabber.org
> > http://mailman.jabber.org/listinfo/members
> > 
> 
> _______________________________________________
> Members mailing list
> Members at jabber.org
> http://mailman.jabber.org/listinfo/members
>