Bulk Operation

EMIX-280 Ensure that terminology from ws-calendar is similar to or the same as that used in Energy Interoperation

EMIX-280 All - Please use another phrase than gluon. Gluon is being used for product, for extension of elements, etc.... Either use the proper naming or use another "standard" naming.

EMIX-280 All - EMIX is building interactions with WSCalendar. Issues with WSCalendar have not been completely addressed, thus further issues could present themselves with EMIX when the WSCalendar is completed. Further complications may occur with Energy Interop.

EMIX-280 Line 303 - This seems to say that everything is a Gluon rather than using the WS-Calendar standard to for just schedule. An information model (class diagram) would really help.

EMIX-280 Line 297 - Is this a product like Energy or SPIN or something else that includes other info.

EMIX-280 Line 297 - can be inherited from the gluon set - So this is part of the WS-Calendar standard and not EMIX?

EMIX-280 Line 295 - Please see the IRC submitted issues on WS-Calendar the use of generic catch all entities and the inheritance model

EMIX-280 Concerned with the proposal to reliance of WS calendar to the formulations being developed. While there may be opportunities to leverage the use of WS calendar to some of the areas being looked at it may create considerable challenges in the others.

EMIX-280 Line 518 - Using catch-all entities like Gluon make it difficult to determine what the spec is actually talking about.

EMIX-280 Line 496 - Why is vcalendar referenced?

EMIX-280 Line 348 - It is really not clear what a Gluon is meant to represent in this context.

EMIX-280 All - What is Gluon?