gluons, intervals and standards

After a 30 minute conversation I think I understand these better but  need to reexpress it in RFC speak. I also have a question or 2.  I'd like to use project management examples as they resonate more with  others outside...  As I understand it intervals express something to be done (or needed).  An example was catering which might have  Interval1 - travel to - fixed duration Interval2 - setup - fixed Interval3 - the event - variable duration Interval4 - tear-down - fixed Interval5 - travel from - fixed duration  A gluon effectively fixes this in time by giving interval3 a start and  duration.  One question was - why is an interval not just a task (vtodo). I sort of  persuaded myself that the semantics (and some rules) are sufficiently  different that using a vtodo would confuse things.  A question: how do we see this interacting with existing installations?  Once these are fixed in time I guess a product might be a set of vtodos.  What are the rules for converting from interval to vtodo? This would be  important for those who would like to use these constructs/concepts and  want to allow the results to be displayed and handled by existing clients.  Is my summary correct and reasonable?

--
Mike Douglass

Senior Systems Programmer Communication&  Collaboration Technologies
518 276 6780(voice) 2809 (fax)

Rensselaer Polytechnic Institute 110 8th Street,
Troy, NY 12180