OASIS Web Services Calendar (WS-Calendar) TC

The detailed work of the PIM revealed some flaws in the PSM spec. Notably:   The degenerate bound intervals at the heart of FREEBUSY and AVAILABILITY are never adequately defined in the spec or in the Schemas.   The RRULES used in Availability are not adequately represented in VAVAILABILITY.   If these issues are interesting to you, I urge you to attend the workshop meeting tomorrow to discuss the implications for the PSM.   tc     "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan Toby Considine TC9, Inc OASIS TC Chair: oBIX & WS-Calendar OASIS TC Editor: EMIX, Energy Interoperation SGIP Smart Grid Architecture Committee    Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com blog: http://www.NewDaedalus.com  

The next PIM working draft with fixes for these and other issues (all the Public Review Comments) will be uploaded tonight. Eyes on the issues Toby mentioned would be good, so we can avoid a second public review before Committee Spec. Thanks! bill -- William Cox Email: wtcox@CoxSoftwareArchitects.com Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile +1 908 277 3460 fax On 7/31/14 4:54 PM, Toby Considine wrote: The detailed work of the PIM revealed some flaws in the PSM spec. Notably:   The degenerate bound intervals at the heart of FREEBUSY and AVAILABILITY are never adequately defined in the spec or in the Schemas.   The RRULES used in Availability are not adequately represented in VAVAILABILITY.   If these issues are interesting to you, I urge you to attend the workshop meeting tomorrow to discuss the implications for the PSM.   tc     Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. - Brian W. Kernighan Toby Considine TC9, Inc OASIS TC Chair: oBIX & WS-Calendar OASIS TC Editor: EMIX, Energy Interoperation SGIP Smart Grid Architecture Committee    Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com blog: http://www.NewDaedalus.com  

Not sure this requires action. Since Vavailability is a component it implicitly has the interval, and the rrules (could be wrong here) would similarly have implicit intervals. The PIM has to make it explicit, bringing the implicitly understood context out. BTW I also looked carefully at the Vavailability draft, and dtStart/duration is just fine.  Anything to reduce the multiplicity of interval expressions is a step forward IMO. Thanks! bill On 7/31/14 4:54 PM, Toby Considine wrote: The detailed work of the PIM revealed some flaws in the PSM spec. Notably:   The degenerate bound intervals at the heart of FREEBUSY and AVAILABILITY are never adequately defined in the spec or in the Schemas.   The RRULES used in Availability are not adequately represented in VAVAILABILITY.   If these issues are interesting to you, I urge you to attend the workshop meeting tomorrow to discuss the implications for the PSM.   tc     Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. - Brian W. Kernighan Toby Considine TC9, Inc OASIS TC Chair: oBIX & WS-Calendar OASIS TC Editor: EMIX, Energy Interoperation SGIP Smart Grid Architecture Committee    Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com blog: http://www.NewDaedalus.com  

This opinion was overtaken by events, and required change. See Jira items including https://issues.oasis-open.org/browse/WSCALENDAR-532 with several subtasks.  I don't think that WS-Calendar 1.0 is in error, because the implied intervals are present in the components, but this might be clarified in any update. Note that's a fancy way of saying I was wrong. Thanks! bill On 8/1/14 12:00 PM, William Cox wrote: Not sure this requires action. Since Vavailability is a component it implicitly has the interval, and the rrules (could be wrong here) would similarly have implicit intervals. The PIM has to make it explicit, bringing the implicitly understood context out. BTW I also looked carefully at the Vavailability draft, and dtStart/duration is just fine.  Anything to reduce the multiplicity of interval expressions is a step forward IMO. Thanks! bill On 7/31/14 4:54 PM, Toby Considine wrote: The detailed work of the PIM revealed some flaws in the PSM spec. Notably:   The degenerate bound intervals at the heart of FREEBUSY and AVAILABILITY are never adequately defined in the spec or in the Schemas.   The RRULES used in Availability are not adequately represented in VAVAILABILITY.   If these issues are interesting to you, I urge you to attend the workshop meeting tomorrow to discuss the implications for the PSM.   tc     Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. - Brian W. Kernighan Toby Considine TC9, Inc OASIS TC Chair: oBIX & WS-Calendar OASIS TC Editor: EMIX, Energy Interoperation SGIP Smart Grid Architecture Committee    Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com blog: http://www.NewDaedalus.com