[OASIS Issue Tracker] (WSCALENDAR-542) Merge Vavailability Package so PIM is a single package

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/WSCALENDAR-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated WSCALENDAR-542:
-----------------------------------

        Summary: Merge Vavailability Package so PIM is a single package  (was: Merge Vavailability Package into PIM package in PIM)
    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.

  was:
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.

On further consideration, 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 simplciity of PSMs in XSD and UML, merge the two packages into one.


> Merge Vavailability Package so PIM is a single package
> ------------------------------------------------------
>
>                 Key: WSCALENDAR-542
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-542
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: PIM
>    Affects Versions: PIM CS01
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: William Cox
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)