WBMM> Draft WBMM Schedule schema v0.20 - 30 Sept 2003

WBMM> Draft WBMM Schedule schema v0.20 - 30 Sept 2003

WBMM> Draft WBMM Schedule schema v0.20 - 30 Sept 2003

Wagner,William WWagner at NetSilicon.com
Tue Sep 30 14:43:14 EDT 2003


Just to confirm Ira's  message, there  will  be a WBMM conference call  tomorrow. 

Time:12:00 PM EDT (9:00 AM PDT)  Wednesday  October  1,  2003
Call-in US Toll-free: 1-877-874-5524
Call-in International/Toll: 1-712-455-8420
Participant Identification number: 497478#

We  will  review Harry's minutes  from the last meeting  (ftp://ftp.pwg.org/pub/pwg/wbmm/minutes/wbmm_030910.pdf and  go on to dig  in to  Ira's  Schedule  Schema, which  with  his Use  Models  message  below  reflects  the basic mechanism  we have been defining. I expect there may  be a few questions about  specifics  and the next  step,  which  perhaps is the  representation of  the  direct  operations and their  parameters). 
Other  issues  will  be the objectives of  the  Monday  face  to  face.

I  have been unable  to  get confirmation  from Harry that  he  will  have the  IBM web document  sharing  capability  available, so  I  suggest  that  participants  pull  up  Ira's  Schema and perhaps  the referenced   RFCs.

And  a reminder  that  the WBMM face to face is in NYC on next  Monday, October 6, starting at  9:30  AM. We  will  have phone access:

Time: 9:30AM EDT, Monday October 6, 2003
Dial In: 1-866-365-4406
Toll #: 1-303-248-9655
Passcode: 2635888# 

Bill Wagner/NetSilicon
WBMM Committee Chair

-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Tuesday, September 30, 2003 12:37 PM
To: McDonald, Ira; 'wbmm at pwg.org'
Subject: WBMM> Draft WBMM Schedule schema v0.20 - 30 Sept 2003

Hi folks,                                         Tuesday (30 Sept 2003)

[for review at tomorrow's WBMM telecon and next Monday's face-to-face]

In response to some comments from Pete Zehler, I revised my prototype
Schedule XML Schema, based on the IETF Schedule MIB v2 (RFC 3231).

The Schedule XML Schema v0.20 validates without warnings using XSV 2.5
(the free XML Schema Validator) and is posted at:


Below are: (a) change log; (b) use models; (c) defined operations; and
(d) excerpted definition of 'ScheduleEntry' (row in a schedule).

- Ira McDonald
  High North Inc

[changes from v0.10 to v0.20]

(1) Changed 'xsd:integer' (unbounded) to 'xsd:int' (32-bit) to align
    with Schedule MIB and for efficient XML processing, per Pete Zehler;
(2) Defined new container elements 'Sched...List' for all multi-valued
    elements for efficient XML list processing, per Pete Zehler;
(3) Revised elements to define explicit 'minOccurs' and 'maxOccurs',
    for consistency with PWG Semantic Model and XML best practices;
(4) Revised indentation of elements and comments for clarity;
(5) Revised and expanded element documentation.

[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 operations]

None - no operation
Other - vendor extension with parameter named 'Operation'
Restart - reset to same, previous, or factory configuration
Shutdown - stop instance of service/device entirely
Startup - start new instance of service/device
Subscribe - for notifications
Wakeup - wakeup service/device, which then performs Get-Schedule

[excerpted definition of 'ScheduleEntry' (row in a schedule)]

<xsd:element name="ScheduleEntry">
  <!-- entry for one scheduled management operation -->
  <!-- element names ending in 'List' denote multi-valued lists -->
  <!-- element names ending in 's' denote single-valued counters -->
  <!-- see individual element descriptions for their cardinality -->
  <!-- and REQUIRED versus OPTIONAL presence in a schedule entry -->
  <!-- see schedEntry - section 4 [RFC3231] -->
      <xsd:element ref="SchedIndex"
        minOccurs="1" maxOccurs="1"/>
      <xsd:element ref="SchedDescription"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedState"
        minOccurs="1" maxOccurs="1"/>
      <xsd:element ref="SchedStateReasonList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedStateMessageList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedOperation"
        minOccurs="1" maxOccurs="1"/>
      <xsd:element ref="SchedParameterList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedTargetURIList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedObject"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedElementList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedMode"
        minOccurs="1" maxOccurs="1"/>
      <xsd:element ref="SchedInterval"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedWeekDayList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedMonthList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedDayList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedHourList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedMinuteList"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedTriggers"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedFailures"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedLastError"
        minOccurs="0" maxOccurs="1"/>
      <xsd:element ref="SchedErrorDate"
        minOccurs="0" maxOccurs="1"/>

More information about the Wims mailing list