Web Based Monitoring and Management: RE: WBMM> June 30 WIMS

RE: WBMM> June 30 WIMS Phone Conference Minutes

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Thu Jul 01 2004 - 11:00:46 EDT

  • Next message: Zehler, Peter: "WBMM> automated meter collection in the news"

    Hi Bill,

    I agree with you. The WIMS Objects spec defines the objects
    themselves, including XxxId key elements, but it shouldn't
    (wherever possible) constrain whether a given protocol (WIMS,
    IPP, whatever) allows/requires those objects to be supported
    multi-valued.

    On Schedules, I suggest that WIMS protocol spec requires that
    a single Schedule object (with Id=1) be supported and permits
    support for multiple Schedule objects (with union semantics,
    as though the set of Schedule objects were concatenated).

    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

    -----Original Message-----
    From: Wagner,William [mailto:WWagner@NetSilicon.com]
    Sent: Wednesday, June 30, 2004 6:35 PM
    To: McDonald, Ira; wims@pwg.org
    Cc: wbmm@pwg.org
    Subject: RE: WBMM> June 30 WIMS Phone Conference Minutes

    Ira,

    Thanks. That will help. I do think that the protocol spec should identify,
    in words at least, the concepts and handling of multiple schedules
    and leases although they are defined in the WIMS Objects document.

    Bill Wagner

    -----Original Message-----
    From: McDonald, Ira [mailto:imcdonald@sharplabs.com]
    Sent: Wednesday, June 30, 2004 6:28 PM
    To: Wagner,William; wims@pwg.org
    Cc: wbmm@pwg.org
    Subject: RE: WBMM> June 30 WIMS Phone Conference Minutes

    Hi Bill,

    I'll try to go through all the Operations and Actions
    in the spec for the new/renamed parameters or returns
    and write up a detailed note for schema name changes.

    Note that 'ScheduleDescription' and all the other groups
    do NOT have an impact on the spec. Only leaf elements
    (and not many of those) are ever mentioned. By the
    same token, while protocol spec can mention leases,
    they're now being normatively defined in WIMS Objects.

    Schedule schema does NOT directly reference all the
    detailed elements of a Subscription object. It has
    four SubscribeForAlerts action parameters (like the
    'NotifyEvents' list) and then a generic parameter
    called 'ActionSubscriptionElements' that allows the
    inclusion of ANY other Subscription element (which
    the WIMS Agent may not support, if it's optional).

    The overall impact on the spec should be modest.

    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
     
    -----Original Message-----
    From: owner-wbmm@pwg.org [mailto:owner-wbmm@pwg.org]On Behalf Of
    Wagner,William
    Sent: Wednesday, June 30, 2004 4:37 PM
    To: wims@pwg.org
    Cc: wbmm@pwg.org
    Subject: WBMM> June 30 WIMS Phone Conference Minutes

    June 30 Minutes are posted at:

    ftp://ftp.pwg.org/pub/pwg/wims/minutes/wims_040630.pdf.

    Note that it appears that wims@pwg.org" is not yet active. Please continue
    to use wbmm@pwg.org

    Bill Wagner



    This archive was generated by hypermail 2b29 : Thu Jul 01 2004 - 11:01:12 EDT