Bill,
I assume you mean 12PM EST Wednesday November 5, 2003?
Pete
Peter Zehler
XEROX
Xerox Innovation Group
Email: PZehler@crt.xerox.com
Voice: (585) 265-8755
FAX: (585) 422-7961
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
> -----Original Message-----
> From: Wagner,William [mailto:WWagner@NetSilicon.com]
> Sent: Tuesday, November 04, 2003 12:45 PM
> To: wbmm@pwg.org
> Subject: WBMM> Nov 4 WBMM Phone Conference
>
>
>
> Just a reminder, the next WBMM conference call will be on 4 November from
> 12PM to 1PM EST.
>
> Time: 12:00 PM EST (9:00 AM PST) Wednesday November 4, 2003
> Call-in US Toll-free: 1-877-874-5524
> Call-in International/Toll: 1-712-455-8420
> Participant Identification number: 497478#
>
> The agenda is a continuation of last week's, with a more review of Ira's
> Schedule schema
>
> ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/schedule-20031027.xsd
>
> Also to be discussed are the steps necessary for extension of the Semantic
> model to include the device objects schema derived from the MIBs, and the
> schedule schema
>
>
> Bill Wagner
>
>
>
> Ira's notes on the use models are repeated below.
> ------------------------------------------------------------------------
> [use models]
>
> Use Model 1 (Passive - Required):
>
> A WBMM managed device (or service) creates an HTTP connection (OUTBOUND
> across the enterprise network's firewall) to a WBMM management station.
> The WBMM managed device (or service) immediately sends a Get-Schedule
> request (packaged in a SOAP/1.1 envelope). The WBMM management station
> sends a Get-Schedule response containing an XML Schedule object (a list
> of scheduled operations and times/intervals).
>
> Later, as each scheduled operation is performed, the WBMM managed device
> (or service) may create another HTTP connection to the WBMM management
> station and send Send-Report (normal) and/or Send-Alert (exception)
> requests, as needed.
>
>
> Use Model 2 (Active - Optional):
>
> A WBMM management station sends an Execute (or SetSchedule) request
> (containing a Schedule object) directly to a WBMM managed device (or
> service), for example, by sending a SOAP/1.1 request over email (SMTP).
>
> Later, each scheduled operation is performed by the WBMM managed device
> (as described in Use Model 1 above).
>
> ------------------------------------------------------------------------
> [defined actions]
>
> None - no operation
> Other - vendor extension with parameter named 'Action'
> Disable
> Enable
> Pause
> Resume
> PauseAndDisable
> ResumeAndEnable
> PurgeJobs
> Restart - reset to same, previous, or factory configuration
> Shutdown - stop instance of service/device entirely
> Startup - start new instance of service/device
> GetElements
> PurgeElements
> SetElements
> GetResource
> PurgeResources
> SetResource
> Subscribe - for notifications
> Unsubscribe
> Wakeup - wakeup service/device, which then performs Get-Schedule
>
> ------------------------------------------------------------------------
> [excerpted definition of 'Plan' (row in a schedule)]
>
> <xsd:element name="Plan">
> <!-- Plan - one planned action -->
> <!-- see individual element descriptions for their cardinality -->
> <!-- and REQUIRED versus OPTIONAL presence in a plan -->
> <!-- see schedEntry - section 4 [RFC3231] -->
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element ref="PlanStatus"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element ref="PlanDescription"
> minOccurs="0" maxOccurs="1"/>
> <xsd:element ref="PlanAction"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element ref="PlanTimetable"
> minOccurs="1" maxOccurs="1"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
> ------------------------------------------------------------------------
> [excerpted definition of 'Schedule' (top-level object)]
>
> <xsd:element name="Schedule">
> <!-- Schedule - schedule metadata and set of planned actions -->
> <!-- see schedTable - section 4 [RFC3231] -->
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element ref="ScheduleState"
> minOccurs="1" maxOccurs="1"/>
> <xsd:element ref="ScheduleInfo"
> minOccurs="0" maxOccurs="1"/>
> <xsd:element ref="ScheduleSourceURI"
> minOccurs="0" maxOccurs="1"/>
> <xsd:element ref="ScheduleTriggerCount"
> minOccurs="0" maxOccurs="1"/>
> <xsd:element ref="ScheduleFailureCount"
> minOccurs="0" maxOccurs="1"/>
> <xsd:element ref="Plan"
> minOccurs="0" maxOccurs="unbounded"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
This archive was generated by hypermail 2b29 : Tue Nov 04 2003 - 12:58:00 EST