Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PIM CS01
    • Fix Version/s: PIM WD14
    • Component/s: PIM
    • Labels:
      None
    • Environment:

      Toby Considine

    • Proposal:
      Hide

      Put all classes in the Vavailability package into the encompassing PIM package. Consider name changes (see WSCALENDAR-544 ) in the merge.

      Show
      Put all classes in the Vavailability package into the encompassing PIM package. Consider name changes (see WSCALENDAR-544 ) in the merge.
    • Resolution:
      Hide

      Integrated packages with name changes ( WSCALENDAR-544) as shown in

      PIM Proposed Changes WD13-WD14WIP 20150115.zip at https://www.oasis-open.org/committees/document.php?document_id=54898&wg_abbrev=ws-calendar.

      Names still subject to WSCALENDAR-544.

      Show
      Integrated packages with name changes ( WSCALENDAR-544 ) as shown in PIM Proposed Changes WD13-WD14WIP 20150115.zip at https://www.oasis-open.org/committees/document.php?document_id=54898&wg_abbrev=ws-calendar . Names still subject to WSCALENDAR-544 .

      Description

      Although the IETF standardization of Vavailability is not completed, that work is expected to start in the near future. The justification for a separate package was the the underlying RFC may change during the IETF process.

      An updated PIM with updated Vavailability is not a major problem for users of the model. Also, the Vavailability package references things in the PIM package and vice versa.

      So for simplicity of defining PSMs, merge the two packages into one.

        Attachments

          Activity

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              william.cox William Cox (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: