[OASIS Issue Tracker] (WSCALENDAR-544) Rationalize Class names in the merged Availability package

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

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

William Cox updated WSCALENDAR-544:
-----------------------------------

    Description: 
The class names in the Availability Package should be reconsidered.

Since another item ( WSCALENDAR-542 ) suggests merging the Availability Package into the PIM UML package, the names should be re-examined.

TimeRangeType should perhaps be "AvailabilityTimeRangeType" 

BusyType is more general in 5545 so should be called AvailabilityBusyType


  was:
The class names in the Availability Package should be reconsidered.

Since another item ( WSCALENDAR-542 ) suggests merging the Availability Package into the PIM UML package, the names should be re-examined.

TimeRangeType should perhaps be "AvailabilityTimeRangeType" or "AvTimeRangeType"; BusyType should perhaps be "AvailabilityBusyType", and so forth.


     Resolution: 
CHANGE TimeRangeType TO AvailabilityTimeRangeType

CHANGE BusyType TO AvailabilityBusyType

> Rationalize Class names in the merged Availability package
> ----------------------------------------------------------
>
>                 Key: WSCALENDAR-544
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-544
>             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
>
> The class names in the Availability Package should be reconsidered.
> Since another item ( WSCALENDAR-542 ) suggests merging the Availability Package into the PIM UML package, the names should be re-examined.
> TimeRangeType should perhaps be "AvailabilityTimeRangeType" 
> BusyType is more general in 5545 so should be called AvailabilityBusyType



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