attachment-0001

Ira, I've looked these over and they look great. Thank you. I will discuss these, tomorrow, with my extended team. With these, I think we are near the point where prototyping can begin. ---------------------------------------------- Harry Lewis IBM STSM Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- <table width=100%> <tr valign=top> <td width=40%>"McDonald, Ira" <imcdonald@sharplabs.com> Sent by: owner-wbmm@pwg.org 06/22/2004 07:54 PM <td width=59%> <table width=100%> <tr> <td> <div align=right>To</div> <td valign=top>"'wbmm@pwg.org'" <wbmm@pwg.org> <tr> <td> <div align=right>cc</div> <td valign=top> <tr> <td> <div align=right>Subject</div> <td valign=top>WBMM> Five WIMS schema modules (22 June 2004)</table> <table> <tr valign=top> <td> <td></table> </table> <tt>Hi folks,                                         Tuesday (22 June 2004) [A cleanup pass in support of Harry Lewis' prototyping efforts at IBM.] I have just posted the suite of WIMS XML schema, all of which validate without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML Schema Validator) and are posted at:    ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/schedule-20040622.xsd    - Schedule XML Schema v0.60    ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/resource-20040622.xsd    - Resource XML Schema v0.40    ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/alert-20040622.xsd    - Alert XML Schema v0.20    ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/report-20040622.xsd    - Report XML Schema v0.20    ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/events-20040622.xsd    - Events XML Schema v0.50    ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/readme-20040622.txt    - this release note Below are: (a) module dependencies; (b) change logs for all modules. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221  Grand Marais, MI  49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [module dependencies] (1) Schedule - includes Events and Resource (2) Resource - no includes (free-standing) (3) Alert - includes Schedule (4) Report - includes Schedule (5) Events - no includes (free-standing) ------------------------------------------------------------------------ [changes from Schedule v0.50 to v0.60] (1) Minor editorial fixups; (2) Added include of Events schema for 'NotifyEvents' (see below). (3) Deleted 'ActionNotifyEvents' and replaced with enumerated    'NotifyEvents' from the (now included) Events schema. (4) Renamed 'ActionNotifyURIs' to 'ActionNotifyRecipientURI' and changed    to single-valued (like IPP), for consistency with Alert schema. (5) Added 'ActionSubcriptionElements' to 'ActionSubscribeForAlerts',    to allow OPTIONAL support for any other Subscription elements    (e.g., 'NotifyNaturalLanguage' for a human-readable notification). (6) Added include of Resource schema for 'ResourceId' (see below). (7) Revised 'ActionRequestedResources' to sequence of 'ResourceId',    'ResourceName', and any element (filter) from the Resource schema,    to support compact and flexible GetResources actions. (8) Revised 'ActionTargetResources' to sequence of 'ResourceId',    'ResourceName', and any element (filter) from the Resource schema,    to support compact and flexible SetResources actions. (9) Added 'ActionMandatoryElements' and 'ActionTargetElements' to    'ActionSetElements' and 'ActionSetResources' to support fine-grained    fidelity (instead of atomic behaviour of most management protocols),    per May 2004 PWG in Vancouver and our recent email discussions. (10) Added 'Action[Monitoring|Management|Administration]' groups and    revised definition of 'PlanAction' to be a choice of exactly one,    per May 2004 PWG in Vancouver and our recent email discussions. (11) Moved 'ActionVendor' to 'ActionManagement' group, to allow vendor    extensions (without Admin group) and allow base 'ActionMonitoring'    group to have only REQUIRED actions, for interoperability. (12) Renamed 'PlanIndex' to 'PlanId' (integer key),    for consistency with PWG Semantic Model/1.0 and IPP/1.1 naming. (13) Added 'Schedule[Status|Description|Processing]' groups and revised    definition of 'Schedule' to use them. (14) Added 'SchedulePersistence', 'ScheduleCreateDate', and    'ScheduleExpireDate' (i.e., lease) to 'ScheduleStatus' group,    for consistency with Resource, per discussion w/ Harry Lewis. (15) Revised 'ScheduleSourceURI' to be REQUIRED (instead of OPTIONAL),    for consistency with WIMS operations and Alert schema. (16) Added 'ScheduleId' (integer key) to 'ScheduleDescription' group,    to support OPTIONAL multiple concurrent Schedule objects. (17) Renamed 'ActionNameType' to 'WIMSActionType', for clarity. (18) Added 'WIMSOperationsSupported', 'WIMSActionsSupported', and    'WIMSObjectsSupported' elements,    to support revised 'RegisterForManagement' operation. ------------------------------------------------------------------------ [changes from Resource v0.30 to v0.40] (1) Minor editorial fixups; (2) Renamed 'ResourceIndex' to 'ResourceId' (integer key),    for consistency with PWG Semantic Model/1.0 and IPP/1.1 naming. (3) Renamed 'ResourceJobURIs' to 'ResourceJobIds' (URIs --> integers),    to avoid dependency on 'job-uri' (ambiguous semantics in RFC 2911). (4) Renamed 'ResourceOwner' to 'ResourceOwnerURI' (name --> URI)    for consistency with Alert and Schedule schema. (5) Added 'ResourceExpireDate' (i.e., lease) to 'ResourceStatus' group,    per May 2004 PWG in Vancouver and our recent email discussions. ------------------------------------------------------------------------ [changes from Alert v0.10 to v0.20] (1) Minor editorial fixups; (2) Renamed 'NotifySubscriptionIndex' to 'NotifySubscriptionId',    and 'NotifyJobSetIndex' to 'NotifyJobSetId',    and 'NotifyJobIndex' to 'NotifyJobId',    for consistency with PWG Semantic Model/1.0 and IPP/1.1 naming. (3) Added 'Subscription[Status|Description]' groups and revised    definition of 'Subscription' to use them. (4) Added 'NotifySubscriptionState', 'NotifyPersistence',    'NotifyCreateDate', and 'NotifyExpireDate' (i.e., lease) to    'SubscriptionStatus' group,    per May 2004 PWG in Vancouver and our recent email discussions. (5) Added 'NotifyOwnerURI' to 'SubscriptionStatus' group    (IPP uses 'notify-subscriber-user-name' with weak semantics),    for consistency with Resource schema. (6) Added 'NotifyRecipientURI' to 'SubscriptionStatus' group    (IPP uses 'notify-recipient-uri' with the same semantics), to    disambiguate overloading of 'Notify[Source|Target]URI' elements. (7) Added 'NotifySourceDate' to 'AlertSource' group, to timestamp Alert    (IPP uses 'printer-up-time' (ticks) and 'printer-current-time'),    for consistency with 'NotifyCreateDate' in Subscription object    and with future Alert history. (8) Deleted 'NotifyCharset' from 'AlertBasic' group (but _not_ from    'SubscriptionDescription' group), due to redundancy w/ fixed UTF-8,    per May 2004 PWG in Vancouver and our recent email discussions. (9) Added 'AlertSubscription' group (for new Subscription events),    per May 2004 PWG in Vancouver and our recent email discussions. ------------------------------------------------------------------------ [changes from Report v0.10 to v0.20] (1) Minor editorial fixups; (2) Added 'ReportBasic' and 'ReportSource' groups,    for consistency with Alert schema. (3) Deleted 'ReportSubstitutedElements' from 'ReportBasic' group,    per May 2004 PWG in Vancouver and our recent email discussions. (4) Added 'ReportSequenceNumber' to 'ReportBasic' group,    for consistency with Alert schema. (5) Added 'ReportSourceURI' and 'ReportSourceDate',    for consistency with Alert schema and with future Report history. ------------------------------------------------------------------------ [changes from Events v0.40 to v0.50] (1) Minor editorial fixups; (2) Added back Resource events (for WIMS notifications support),    per May 2004 PWG in Vancouver and our recent email discussions. (3) Added new Subscription events (for WIMS notifications support),    per May 2004 PWG in Vancouver and our recent email discussions. ------------------------------------------------------------------------ </tt>