[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: SKI Presentation in Oslo




>Now I am not saying this is necessarily the best way to solve the problem,
>it could also be done with the help of a qualifier inside the Event property
>or a qualifier for the STATUS property. But we had already made a decision
>that OPENINGTIMES should be a new component and it seemed natural to deal
>with SCHEDULEDTIMES in the same way.


I think you mean "component property", not "component".

Not sure who you refer to in the "...we have already made a decision...". You mean SKiCAL? I can't recall that the IETF calsch WG didn't make such a decision; or that such a proposal was actively discussed. I think we were still waiting to hear what the complete requirements were. The specification you posted is an implementation profile, but doesn't really define the problem domain requirements. Right?

Back to the requirements...For an event, such as a Boston Red Sox baseball game, I can certainly see that it would be beneficial to have an additional property in the VEVENT definition that indicated when the gates opened. Very often, public events have both a

-- Frank