ws-calendar — archive

[Edward Cazalet]

Ws-Calendar looks to be a terrific advance for the smart grid and providing ways for users to use only what they need without having to understand all of Ws-Calendar. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: WSCALENDAR-224 URL: http://tools.oasis-open.org/issues/browse/WSCALENDAR-224 Project: OASIS Web Services Calendar (WS-Calendar) TC Issue Type: Improvement Reporter: Edward Cazalet Assignee: Toby Considine The capability of WS-calendar to take all of the parameters of an energy product and allocate the parameters to intervals and gluons is extremely useful in EMIX and EI. Carrying a price and/or quantity along with a start time and a pointer to a gluon makes for a simple package. A gluon can point to another gluon which can carry parameters that very less frequently. And the link to conventional calendaring technology is also a big plus for interoperability, especially between the grid and customers. However, there is a lot in ws-calendar that is not currently useful to energy markets. If a way can be found for EMIX and EI to expose only that of WS-Calendar that is needed by energy markets it would open up WS-Calendar, EMIX and EI to more users. And if the XML schemas based on WS-Calander can be simplified, (fewer layers) again that would be helpful. I started out as an advocate for WS-Calendar, then I turned a skeptic when faced with the complexity including strange terms like gluon and a strange use of the term interval. I am now a supporter but simplification would help bring along others more quickly and expand its proper use in energy and the smart grid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira