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.

WS-Calendar is used for more than specifying a schedule; the inheritance rules are used to evolve a schedule from one (say in an Energy Interoperation Tender) where the price, location, and even starting time might not be specified to one (say in an Energy Interoperation) where all that information is bound. Limited examples were in PR01. Class diagrams will be in PR02; an Enterprise Architect Project file including the nearly final PR01 version of UML models from the EMIX schemas, as well as of Energy Interoperation PR01, can be found at http://www.oasis-open.org/committees/document.php?document_id=40529&wg_abbrev=energyinterop As the Gluon is from WS-Calendar, a normative reference in EMIX, we are using that term. The terminology should also describe the functional use (as below, e.g., "A Gluon is a handle to a Sequence". Rewrite and review the ws-calendar narrative for clarity and precision, including Stop sentence after "inherited" and add discussion of inheritance earlier in document. Use WS-Calendar Gluon in first reference in each section. Add conformance section on inheritance to last section. Terminology needs to be consistent; e.g., a Gluon acts as a handle to a Sequence Capitalize Interval, Gluon, Sequence throughout as defined terms.