RE: [obix-xml] oBIX Scheduling

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

Do we include points actually in the vCalendar? I can see….

(note: pseudo XML, not  any  actual implementation)

 

Postulate separate objects in the oBIX payload

 

<calendar1>

<calendar2>

<calendar3>

<calendar4>

<contract1>

<contract2>

<contract3>

<contract4>

<contract5>

 

I could imagine (A)

<contract1 schedule=”calendar1”>

<contract2 schedule=”calendar1”>

<contract3 schedule=”calendar1,calendar3”>

 

Alternately, I could imagine (B)

 

<calendar1 invokes=”contract1”>

<calendar2 invokes=”contract1,contract3”>

<calendar3 invokes=”contract4”>

 

This moves invocation of point or  event outside the calendar item and creates a more general purpose calendar item. Personally, I prefer the (a) approach. But not strongly…

 

tc

---

"A man should never be ashamed to own that he has been in the wrong, which is but saying ... that he is wiser today than yesterday." -- Jonathan Swift

---

Toby Considine Chair, OASIS oBIX TC 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

 

 

From: Brian Frank [mailto:bfrank@tridium.com]
Sent: Wednesday, October 22, 2008 11:28 AM
To: obix-xml@lists.oasis-open.org
Subject: RE: [obix-xml] oBIX Scheduling

 

Yes let’s definitely setup a meeting.

 

This is great that we finally have some stuff written down.  Couple comments:

 

- I do not think vcalendar should implement Point – intuitively it doesn’t seem like calendars are hard or logical points

 

- I think it ok that we can’t capture the contract of consistent values;  no type system can perfectly model every contract;  so I don’t think we should complicate things by trying to create specialized bool, real, etc calendars;

 

- I don’t get the priority of 1 or 0 – is that the range?  If so why not use a boolean?

 

- getSchedule doesn’t sound like an operation – it sounds like a JavaBeans getter; I’d vote for something like flatten, periods, toSchedule, scheduleFor

 

- We should translate dashes to camel case for example last-modified should be lastModified

 

- Shouldn’t Vevent and Period have a value slot?

 

- Does it make sense for Period to include end and duration when that can be derived?

 

 

---

From: Aaron Hansen [mailto:a.hansen@controlco.com]
Sent: Monday, October 20, 2008 6:59 PM
To: obix-xml@lists.oasis-open.org
Subject: [obix-xml] oBIX Scheduling

 

Lets schedule a meeting to discuss.

Issues/Todo:

?         Should Vcalendar implement obix:Point.

?         Should we define calendars and events of specific types (bool,real...)?

?         defaultValue object under Vcalendar?

?         How can the getSchedule operation be modified to more closely support free/busy requests?