RE: [obix-xml] Power Systems Group

["Aaron Hansen" <ahansen@tridium.com>]

I like a bunch of domain-specific services.  The security guys want a service for CCTV so they can easily expose pan, tilt and zoom operations.  These don't belong in the current set of specs and read/write won't cut it, especially if complex arguments are needed.

On the other hand, could these be generically handled by an action/command service?

Sorry about all the email today, this is the last one.
Aaron

-----Original Message-----
From: Richards, Dave [mailto:drichards@trane.com]
Sent: Wednesday, December 15, 2004 1:44 PM
To: obix-xml@lists.oasis-open.org
Cc: RichardCHarwell@eaton.com
Subject: RE: [obix-xml] Power Systems Group


This brings up a big question that we haven't really considered yet (to my
knowledge).

Do we want to have a bunch of domain-specific services like this or do we
want to try to include everything in the basic services?  Even if there is a
serparate set of services, the same data would still be accessible through
the basic read.  What is the case for duplication?  Can some sort of
canonical naming scheme for use with the basic read be as effective as
specific services?  Is that even necessary?

Perhaps we need a joint meeting with the Power Systems SC to discuss the
direction we want to go on this?  That way we'll have a policy when the next
domain-specific group starts up.

The operations listed in the referenced doc can for the most part be done
with the basic read operation or the TBD history service.  The possible
exception is the request_peak_energy function.  Request_peak_energy just
isn't clear to me, but there seem to be calculations involved based on the
"timewindow" parameter, so I don't know if it fits the basic model or not.


Dave Richards


> -----Original Message-----
> From: ahansen@tridium.com [mailto:ahansen@tridium.com] 
> Sent: Wednesday, December 15, 2004 11:11 AM
> To: obix-xml@lists.oasis-open.org
> Cc: RichardCHarwell@eaton.com
> Subject: [obix-xml] Power Systems Group
> 
> 
> The power systems group has built a service description for 
> exchanging info with energy mgmt systems.
> 
> They would like us to review and comment on the next steps to 
> implementation in a way consistent with our services.
> 
> At this point, I think they'll be of more use to us than the 
> reverse.  Having their service in mind should help us with 
> issues such as the ext element.  Would it be best for them to 
> build their ideal schema/wsdl and the two of us adapt to each other? 
> 
> Take a look and we'll discuss at the next telecon (which at 
> this point won't be until next year).  If the link doesn't 
> work, their doc is available from the umbrella oBIX TC 
> document section.
> 
http://oasis-open.org/apps/org/workgroup/obix-power/download.php/10200/OBIX%
20Power%20System%20services.doc

On a slightly related note:
Some think of us as the HVAC group and that we should also be developing
higher level functions similiar to these.  My/our plate is full, is anyone
willing to head up an HVAC sig for this purpose?

Best,
Aaron