Create better explanation of different parts of WS-Calendar: Semantic, API (REST), and Message (SOAP) and which parts to use when

XMLWordPrintable

    • Type: Improvement
    • Resolution: Applied
    • Priority: Major
    • wd21
    • Affects Version/s: pr01
    • Component/s: None
    • None
    • Hide

      Develop section in introduction distinguishing the different parts and purposes of the specification

      Show
      Develop section in introduction distinguishing the different parts and purposes of the specification

      Different parts of this specification do quite different things. If the reader sees it as all or nothing, then this is distracting

        1.
        		 Line 1426 - Does this mean that derived standards like EMIX and EnergyInterop will also be Restful? Sub-task Closed Toby Considine (Inactive)
        2.
        		 Line 1440 - This section specifies the use of HTTP RESTfull services, and does not provide language to indicate that there may be any other way to implement this standard. Sub-task Closed Toby Considine (Inactive)
        3.
        		 Line 38 - No problem with WS-Calendar adopting semantics and vocabulary from iCalendar, but it sounds like the standard will only use iCalendar in applicable web service contracts. Sub-task Closed Toby Considine (Inactive)
        4.
        		 Line 859 - There is no way to define an interval and then use it in a schedule without redefining it again? 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: