OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041118.doc uploaded


Are we talking about the same diagram, Figure 1?

Where does it talk about the MUWS framework (its properties, events, metadata, capabilities) are being used, applied, and extended by specific domains?

All it shows is how a managed resource is represented through a web service manageability end point that is descovered by a manager and is used for interactions with the managed resource.  This in essense is a high level MUWS architecture.

H.
--

Sedukhin, Igor S wrote:
That is what it depicts now: MUWS applied to various domains. That is how that section is and was written. Therefore by your definition it is too WSDM architecture.
 
MUWS defines a number of capabilities that can be used and WSDM architecture says how to apply those capabilities to any manageable resource in any domain.
 

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 

 


From: Homayoun Pourheidari [mailto:homayoun@bea.com]
Sent: Tuesday, November 23, 2004 5:29 PM
To: Sedukhin, Igor S
Cc: Vambenepe, William N; Mark Ellison; Wsdm (E-mail)
Subject: Re: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041118.doc uploaded

I agree with William that this is a "MUWS architecture" that can be applied to different domains -- e.g. MOWS.  In the picture, if you change the "Manageable Resource" to a web service, then it would become a "MOWS architecture". 

I think a "WSDM architecture" should depict a picture where a MUWS framework that is getting applied to various domains.

Cheers,
H.
--

Sedukhin, Igor S wrote:
This [I agree the architecture is not specific to MUWS.] contradicts
[Which is why I think it makes sense to call it the MUWS architecture.]
:)

The change does affect a lot of wording in MOWS concepts section and I
don't want to revisit it at this point.

I believe it is the WSDM architecture and spec partitioning is our own
internal kitchen which must not affect the reason why we have this TC in
the first place!

This may seem to be minor to some, but it is not to me. So I'd like to
insist that we recall that change in MUWS part 1.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 


-----Original Message-----
From: Vambenepe, William N [mailto:vbp@hp.com] 
Sent: Tuesday, November 23, 2004 5:05 PM
To: Sedukhin, Igor S; Mark Ellison
Cc: Wsdm (E-mail)
Subject: RE: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041118.doc
uploaded


I agree the architecture is not specific to MUWS. It applies to MOWS
too. It actually applies to everything that uses MUWS, including MOWS.
Which is why I think it makes sense to call it the MUWS architecture. It
is the architecture introduced by MUWS and used by every spec that is
based on MUWS, including but not limited to MOWS.

Any other opinions? At the end I don't think this materially affects the
spec so it's not a big deal. I'd like to hear what others think and I'll
put in the spec whatever the group likes best.

William 

-----Original Message-----
From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent: Monday, November 22, 2004 7:17 PM
To: Vambenepe, William N; Mark Ellison
Cc: Wsdm (E-mail)
Subject: RE: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041118.doc
uploaded

I do not agree to replace WSDM for MUWS in the concepts an architecture
section. This change has been just introduced and was not in the Mark's
edits. I believe that these concepts apply to all of the work and
specifications produced by WSDM and are not specific to MUWS only. I'd
like to recall this change.


-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 


-----Original Message-----
From: Vambenepe, William N [mailto:vbp@hp.com]
Sent: Monday, November 22, 2004 10:09 PM
To: Sedukhin, Igor S; Mark Ellison
Cc: Wsdm (E-mail)
Subject: RE: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041118.doc
uploaded


In the doc I just posted (minutes before this reply came) I replaces
"manageability representation" with "manageability endpoint". This seems
correct to me (by our definition a manageability endpoint is specific to
one resource) and avoids repeating the more heavy "implementation of a
manageable resource". Let me know if someone thinks this is a problem.

I second Igor's thanks to Mark for the great review. Since I expect as
many corrections to Part 2 I am holding off from further work on Part 2
until I get Mark's review otherwise it will be merge hell.

William

-----Original Message-----
From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent: Monday, November 22, 2004 7:04 PM
To: Mark Ellison; Vambenepe, William N
Cc: Wsdm (E-mail)
Subject: RE: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041118.doc
uploaded

Great comments, Mark. Looks much better now.

[resource-type-specific] I think it was actually better as
[resource-specific]. Avoids introduction of unnecessary concepts early
on.
That is, if printer management is printer-specific or
printer-type-specific, I don't know...

Good that you noticed: in 5.3.1 a [manageability representation]. Where
did that come from? We have never defined one in the architecture or
terminology sections. I agree that this should be implementation of a
manageable resource as your comment says.


-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 


-----Original Message-----
From: Mark Ellison [mailto:ellison@ieee.org]
Sent: Monday, November 22, 2004 9:06 PM
To: vbp@hp.com
Cc: Wsdm (E-mail)
Subject: Re: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041118.doc
uploaded

Hi William,

Here are my editoral comments for MUWS-part1.  Hopefully, I'll work
through part two by this time tomorrow...

Regards,

Mark

vbp@hp.com wrote:

  
The document wd-wsdm-muws-part1-1.0-20041118.doc has been submitted by
    
William Vambenepe (vbp@hp.com) to the OASIS Web Services Distributed
Management (WSDM) TC document repository.
  
Document Description:
Part 1 has a complete draft with no pending AI or TODO. Thanks for
    
reviewing.
  
Download Document:  
http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/10177/wd
-wsdm-muws-part1-1.0-20041118.doc

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document
_id=10177


PLEASE NOTE:  If the above links do not work for you, your email 
application may be breaking the link into two pieces.  You may be able 
to copy and paste the entire link address into the address field of
    
your web browser.
  
To unsubscribe from this mailing list (and be removed from the roster
    
of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou
p.php.
  
 

    


To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou
p.php.



To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.


  
begin:vcard
fn:Homayoun Pourheidari
n:Pourheidari;Homayoun
org:WebLogic Integration
adr;dom:;;2315 North First St.;San Jose;CA;95131
email;internet:homayoun@bea.com
tel;work:+1 408.570.8175
version:2.1
end:vcard



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]