Improve references to WS-Calendar for clarity, terminology, and adaptation of inheritance

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • wd17
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      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.

      Show
      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.

      This is an umbrella issue ("Task") for the terminology and clarity issues related to WS-Calendar in EMIX.

        1.
        		 All - What is Gluon? Sub-task Closed Toby Considine (Inactive)
        2.
        		 Line 496 - Why is vcalendar referenced? Sub-task Closed Toby Considine (Inactive)
        3.
        		 Line 348 - It is really not clear what a Gluon is meant to represent in this context. Sub-task Closed Toby Considine (Inactive)
        4.
        		 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. Sub-task Closed Toby Considine (Inactive)
        5.
        		 Line 295 - Please see the IRC submitted issues on WS-Calendar the use of generic catch all entities and the inheritance model Sub-task Closed Toby Considine (Inactive)
        6.
        		 Line 297 - can be inherited from the gluon set - So this is part of the WS-Calendar standard and not EMIX? Sub-task Closed Toby Considine (Inactive)
        7.
        		 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. Sub-task Closed Toby Considine (Inactive)
        8.
        		 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. Sub-task Closed Toby Considine (Inactive)
        9.
        		 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. Sub-task Closed Toby Considine (Inactive)
        10.
        		 Line 518 - Using catch-all entities like Gluon make it difficult to determine what the spec is actually talking about. Sub-task Closed Toby Considine (Inactive)
        11.
        		 Ensure that terminology from ws-calendar is similar to or the same as that used in Energy Interoperation Sub-task Closed Toby Considine (Inactive)
        12.
        		 Line 297 - Is this a product like Energy or SPIN or something else that includes other info. Sub-task Closed Toby Considine (Inactive)

            Assignee:
            Toby Considine (Inactive)
            Reporter:
            Toby Considine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: