events” is not clearly defined in the document.
I assume it refers to events that have
< now) AND ((dtend > now) OR ((dtstart +
duration) > now)).
about events that have neither dtend nor duration? I think
this is the standard in building automation. In our scheduler the
is (disregarding priorities) that event with dtstart < now that has
highest dtstart. Our scheduler has something like dtstop but no
is a separate event in our scheduler. We have no default value.
1. Sorry, priority is 1-9, and 0 means no
is the highest priority. This is an ical construct.
2. No problem on the op name change.
3. Dashes vs camel case - I was trying to preserve the iCal names (obix
ical property name = xcal element name).
4. I was thinking Vevent and Period type match the parent calendar
So if the calendar is a bool, then the events and periods would be
5. Period end vs. duration - just passing along the iCal structure.
Brian Frank wrote:
let’s definitely setup a meeting.
is great that we finally have some stuff written down.
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?
Lets schedule a meeting to discuss.
- Should Vcalendar implement
- 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?