--- In WS-Home-Building-Workgroup@yahoogroups.com, "Pete Brown"
<peterwbrown@...> wrote:
>
> I've uploaded the Camera WSDL to the files section of this group for
> review and discussion.
>

I had a look at this and find it unwieldy, with all these getters and
setters for each and every camera attribute. I'm not a camera expert,
but I guess it will be very difficult to get this type of fine-grained
interface accepted as a standard by all camera manufacturers. It looks
as though a camera is modeled as a totally unstructured set of attributes.

Furthermore, from a user (application developer) point of view, I
think that, in addition to accessing attributes individually, I'd also
like to be able to get/set a whole bunch of attributes (maybe all of
them) at once. This is what WS-Management allows to do, provided that
an appropriate 'resource model' is defined for the device type at hand
(in this case, a camera).

Indeed, I suggest (for cameras or other devices) to use DPWS for
direct control interactions and WS-Management for all interactions of
a configuration (parameter setting/getting) or supervisory nature
(more precisely: Fault/alarm handling, Configuration, Accounting,
Performance monitoring ans Security management, according to the FCAPS
model). WS-Management was designed for that purpose and is quite
complementary to DPWS. By the way, the different types of interaction
might correspond to different 'user' applications (maybe with
different authorization levels).

Does this make sense to you?

Regards,
Harm Smit.