W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2002

RE: [RTF] Conceptual Management Model (call for public discussion s)

From: Hao He <Hao.He@thomson.com.au>
Date: Tue, 2 Jul 2002 21:43:28 +1000
Message-ID: <686B9E7C8AA57A45AE8DDCC5A81596AB019ED7B7@sydthqems01.INT.TISA.COM.AU>
To: "'Darran Rolls '" <Darran.Rolls@waveset.com>, "'WSA W3C Public (E-mail) '" <www-ws-arch@w3c.org>
hi, Darran,

I am thinking of a conceptual model similar to or compaitable with the core 
model of CIM so people can build or map more detailed models with CIM.

Hao

-----Original Message-----
From: Darran Rolls
To: Hao He; WSA W3C Public (E-mail)
Sent: 7/2/02 6:38 AM
Subject: RE: [RTF] Conceptual Management Model (call for public discussions)

Hao

Could you please (briefly) explain the nature of the suggested
conceptual models, perhaps in light of something like DMTF CIM/WEBM?

Thanks

--------------------------------------------------------
Darran Rolls                      http://www.waveset.com
Waveset Technologies Inc          drolls@waveset.com 
(512) 657 8360                    
--------------------------------------------------------


> -----Original Message-----
> From: Hao He [mailto:Hao.He@thomson.com.au]
> Sent: Monday, July 01, 2002 12:40 AM
> To: WSA W3C Public (E-mail)
> Subject: [RTF] Conceptual Management Model (call for public
discussions)
> 
> hi,
> 
> The RTF wants people's view on the following issue:
> 
> Do we need a Conceptual Management Model in the requirement document?
> 
> I proposed the following two items[1] to be added to D-AC18 [2]
proposed
> by
> Zula and Heather.
> 
> AR018.1.5 Define a standard (conceptual) management model for
> architectural
> components, their dependencies and their lifecycles.
> 
> AR018.1.5 Define a standard (conceptual) management model for Web
Services
> instances,
> their dependencies and their lifecycles.
> 
> My motivation for suggesting them is that a high-level conceptual
> management
> model can
> 1) help ensure a WS architecture and service manageable;
> 2) be a standard starting point for future work on WS management;
> 3) unify metrics, management operations, and events as outlined in
AR018.1
> and AR018.2[2];
> 4) help the deployment of a WS.
> 
> Any thoughts and comments on this issue would be appreciated.
> 
> Hao
> 
> [1] http://lists.w3.org/Archives/Public/www-ws-arch/2002Jun/0138.html
> [2] http://lists.w3.org/Archives/Public/www-ws-arch/2002Jun/0116.html


Received on Tuesday, 2 July 2002 07:42:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:01 GMT