OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-calendar message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Naming of Intervals


There were many many comments on the time segments / intervals section of the working draft. We have also made this more complex. I would like to open a conversation on this.

 

The current WIP has something similar to:

 

Time Segment

Definition

Duration

Well-known element from iCalendar and xCal, Duration is the length of a meeting scheduled using iCalendar or any of its derivatives. Duration is an optional parameter of xCal objects VEVENT and VTODO.

Duration Series

A Duration Set is a series of consecutive Durations, meaning it includes the trivial case of a single duration. An interval is re-locatable, i.e., it does not have a specific date and time.

Interval

An interval is a fully qualified duration set. An interval definition begins with the duration set and adds supporting information to define the service performance. An interval is re-locatable, i.e., it does not have a specific date and time.

Period

A period is an interval that is anchored by a specific date and time, that is, it is an interval with a start date and time. Specific performance of a service contract always occurs in a period.

 

I am not absolutely sure the DurationSet is needed – and it has not been discussed before. It came as I was trying out some language which highlighted a deeper problem.

 

I)                    We have long discussed a series of consecutive durations, perhaps even identical size durations, i.e., all 15 minute intervals. These would be essentially homogenous, i,e, they may have an interval object that says they are all purchases of power, although each interval may have a different quantity, to build a load profile.

 

II)                  As we discussed ways to control order of these consecutive homogenous events, we came up with a structure that also supports, say, two services, A and B, in which B might follow immediately after A completes, or 10 minutes after A completes, or 10 minutes before A completes, or 10 minutes after A starts. This allows for several interesting groups of objects, with more breadth than the simple consecutive series.

 

It also creates two things to be named. (I) which we have been calling an interval and the more complex (II) which is as of yet un-named.

 

Discussions, please…

 

tc

 

 

 


“It is difficult to get a man to understand something, when his salary depends upon his not understanding it” -- Upton Sinclair.


Toby Considine
TC9, Inc

OASIS Technical Advisory Board
TC Chair: oBIX & WS-Calendar

TC Editor: EMIX, EnergyInterop

U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

  

Email: Toby.Considine@gmail.com
Phone: (919)619-2104

http://www.tcnine.com/
blog: www.NewDaedalus.com

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]