[OASIS Issue Tracker] (WSCALENDAR-555) Gluon as Handle and Service Entry Point (SEP)

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

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

William Cox updated WSCALENDAR-555:
-----------------------------------

              Summary: Gluon as Handle and Service Entry Point (SEP)  (was: CLONE - Gluon as Handle and Service Entry Point (SEP))
             Assignee: Toby Considine  (was: William Cox)
        Fix Version/s: PIM WD14
    Affects Version/s: PIM CS01
                           (was: PIM WD05)
          Description: 
See WSCALENDAR-506 which applied to earlier PIM WD05. That item has been closed, no action.

This applies to PIM CS01 Section 4.5.2 line 415.


             Proposal: 
Add to 4.5.2 after line 419:

More generally, a Gluon can be thought of  as a pointer into a Sequence, which is a time-related set of intervals. With Gluons and inheritance rules, missing scheduling information can be dynamically included in a Sequence.

If one considers the unscheduled Sequence and referencing Gluons as a subroutine or template, than a Gluon defines an instance or invocation of that template. 

Several Gluons MAY exist (and be advertised) pointing into a given Sequence. When used in this manner, effectively each Gluon acts as a Service Entry Point for interacting with that template

Each Gluon (service entry point) may in turn be associated with additional information: a different price, a different schedule of availability, and so on. Alternately, a Gluon makes the entire instance associated with each entry point actionable by Scheduling that Sequence. (See Table 3-1). 

  was:
Add to 4.6.3:

As above, a Gluon can be thought of  as a pointer into an array of intervals, one able to add missing scheduling information to the array. If one considers the unschedduled array as a subroutine or template, than a Gluon defines an instance or invocation of that template. Several Gluons MAY be advertised pointing into the same Array. When used in this way, each Gluon acts as a Service Entry Point for the interacting with that template. Each service entry point may in turn be accompanied by additional information: a different price, a different schedule of availability, and so on. Alternately, a Gluon that makes the entire instance associated with each entry point actionable. 

           Resolution:   (was: Assigning to Bill for PIM cleanup post CS01.)

> Gluon as Handle and Service Entry Point (SEP)
> ---------------------------------------------
>
>                 Key: WSCALENDAR-555
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-555
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Improvement
>          Components: PIM
>    Affects Versions: PIM CS01
>         Environment: Toby Considine
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>             Fix For: PIM WD14
>
>
> See WSCALENDAR-506 which applied to earlier PIM WD05. That item has been closed, no action.
> This applies to PIM CS01 Section 4.5.2 line 415.



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