RE: [ws-calendar] gluons, intervals and standards

["Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu>]

(Should have replied to all, not just to Mike)


"It is the theory that decides what can be observed."   - Albert Einstein

Toby Considine
Chair, OASIS oBIX Technical Committee
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee
Facilities Technology Office
University of North Carolina
Chapel Hill, NC
  
Email: Toby.Considine@ unc.edu
Phone: (919)962-9073 
http://www.oasis-open.org 
blog: www.NewDaedalus.com


-----Original Message-----
From: Considine, Toby (Campus Services IT) 
Sent: Wednesday, May 11, 2011 9:28 PM
To: 'Mike Douglass'
Subject: RE: [ws-calendar] gluons, intervals and standards

In the as yet unseen WD20, I refine the discussion of Intervals based on out conversation the other morning

An Interval is a unit of time, and can be bound to service delivery. An Unscheduled Interval has no specified date and time. A Scheduled Interval has a specified start date and time. Intervals can legally contain all elements properties as defined in [RFC5545]. For convenience, the elements essential to coordinating service operations using Intervals are listed in Table 3-1. 

An Interval is part of a Sequence. An entire Sequence can be scheduled by scheduling a single Interval in a Sequence. A single Sequence can be scheduled multiple times through repeated reference by different Gluons. For this reason, of the three primary temporal elements (dtStart, dtEnd, and Duration) in a Component, the Duration has primacy in Intervals. Within a Sequence, a maximum of a single Interval MAY have a dtStart or a dtEnd.

I think that an entirely reasonable application would create vtodos, or perhaps even vevents from each Interval as a Sequence is transacted. Another entirely reasonable Appliaction might just add information in place, or even re-name them with the same GUID. Such activities are interesting, but out of scope of the Spec.

Does that help?

tc

"It is the theory that decides what can be observed."   - Albert Einstein

Toby Considine
Chair, OASIS oBIX Technical Committee
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC
  
Email: Toby.Considine@ unc.edu
Phone: (919)962-9073
http://www.oasis-open.org
blog: www.NewDaedalus.com


-----Original Message-----
From: Mike Douglass [mailto:douglm@rpi.edu]
Sent: Wednesday, May 11, 2011 3:47 PM
To: ws-calendar@lists.oasis-open.org
Subject: [ws-calendar] 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                           douglm@rpi.edu
Senior Systems Programmer
Communication&  Collaboration Technologies      518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php