Allow full Recurrence Function for both Gluon and Availability

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Major
    • PIM WD15
    • Affects Version/s: PIM CS01
    • Component/s: PIM
    • None
    • Environment:

      William Cox based on 20150320 TC Meeting

    • Hide

      Create RecurrenceType (or RecurType) with attributes exdate, rdate, rRule.

      Create recurrence attribute in AvailableType and GluonType cardinality [0..1]

      Delete duplicated attributes in WD14 AvailableType.

      Follow standard NIEM practice isolating the conformed strings within named classes.

      Show
      Create RecurrenceType (or RecurType) with attributes exdate, rdate, rRule. Create recurrence attribute in AvailableType and GluonType cardinality [0..1] Delete duplicated attributes in WD14 AvailableType. Follow standard NIEM practice isolating the conformed strings within named classes.
    • Hide

      Address full recurrence semantics as used in Availability and Gluons

      Show
      Address full recurrence semantics as used in Availability and Gluons

      The Recurrence functionality for Vavailability (in AvailabilityType) should also be available for Gluons.

      A RecurrenceType class containing RRules, Exdate, and Rdate as RFC5545 conformed strings is also needed for reuse - in GluonType and AvailableType.

      Note that WD14 AvailableType does NOT have Rdate.

      Descriptive rules for inheritance of RecurrenceType need to be created. I suggest that RecurrenceType inheritance shall not cross the Gluon-Interval boundary; replacement rather than logical operations seems much simpler to process.

            Assignee:
            Michael Douglass (Inactive)
            Reporter:
            William Cox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: