[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Thoughts on Enrollment
I wrote the following this weekend when trying to work through issues in Enrollment. It may be the basis of a subsection, perhaps a level two portion of a re-written Section 3. Section three needs to rely more on the existence of WS-Calendar and EMIX, and less on positing them. Of course, that was not true last December… Note how it tries to pre-figure the conformance / context rules, and thus eliminate the need to express redundant information in the intervals… So, not sure where this fits, but sharing for slings and barbs… Narrative Framework for EI Services (Non-Normative) The summary that follows provides a narrative guide to aid in understanding key potential uses of the services. It does not define a normative market or application framework. Markets and applications may use some or all of the services defined herein. A Party first registers with another party and receives a Party ID. Registration establishes an identity and basic contact information. To act as a VEN, an actor may locate one or more potential VTNs and then poll that potential VTN for the Market Contexts that it offers. Parties in a market MAY issue indications of interest to other registered Parties in the market. A Party may request information from potential VTNs about the Market Contexts that each offers. In response to an indication of interest, one or more parties may offer to serve as a VTN or as a VEN. Some markets MAY have only one potential VTN. Some Parties MAY be constrained to acting solely in the VEN role. Any such market rule and set of roles is outside the scope for this specification. A Party which wishes to act as a VEN enrolls one or more Accounts with a VTN. During enrollment, an Account is associated a particular market context. An Account may be enrolled as a Resource, and exchange detailed capability information, or it may be enrolled solely as a transactive participant. A VEN can choose to enroll a single Account in multiple market contexts, or with multiple VTNs. An Account enrolled in a Market Context accepts the rules of that Market Context, which may include specific Terms including non-performance penalties. Market and Application rules concerning multiple enrollments are out of scope for this specification. A VEN identifies its Accounts by Party ID (its own) and Account Name. It is possible to enroll an Account and associate it with no Market Context. The meaning of such an enrollment is determined by market rules which are outside the scope of this specification. During Enrollment, each Account is associated with one or more schedules. A Market Context may have a schedule for when it is active. An Account may have a schedule when it can respond to requests. A market may offer different terms for day-time and night-time performance. A VEN may require different Terms for work-time and after-hours performance. Enrollment makes no statement about how such Terms are agreed to, but only how the agreement is expressed. A VEN may Opt to change its availability for performance. It can make permanent, i.e., non-expiring changes to its schedule by re-enrollment. It can Opt-In to add a specific availability schedule to the existing schedule for a discrete time. It may Opt-Out, replacing the current schedule with another for a discrete time. “The single biggest problem in communication is the illusion that it has taken place.”
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]