RE: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041127.doc uploaded

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

My comments on the subj:

121-122: [portType element information item] it is either element or EII
but across the document. Pick one. I suggest the "element". The document
jumps from one to the other and that is not appropriate.

255 shold better say [choice of an implementation approach]

288 [resource-specific] was just fine over there, I believe. I do not
understand why is this wording bifurcation happening in that sentence...

301 [allows for a range of coverage]... [gradual coverage]... Just say
[covers equally well starting from the low-end manageability up to the
high-end manageability]...

309 should be [This flexibility]

361 [One such element of metadata on properties] should be [One such
metadata on properties] and similarily [Capability is an element of
metadata that] should be [Capability is metadata that]. This use of
"element" is confusing here with its meaning of an XML element
throughout the document.

420 [permitting virtually free-form expression of events.] This is very
fancy. It is not really free form, is it? There is a form given here and
unless it conforms to it it ain't a WSDM event. So I suggest that this
statement is removed. One may simply state [WSDM event format is
extensible.] Which is already stated somewhat in the sentense above
this.

421 I do not believe that Figute 6 is at all necessaary. We have only
used UML to represent individual capabilities so far. Never any data
models. It is not consistent to represent some data and not the other. I
suggest that we keep using UML for only the capability models
(properties, operations, events.

516 [The manageability capability URI for the Identity capability is]
why not just say [This capability is identified by the following URI]

538-540 That stuff just hangs out there without any obvious attahment.
Why not precede this with [This property has the following metadata:]
and indent the lines.

592 [characteristics of a manageability interface rather than the
resource.] I think not. I think [characteristics of a manageability
endpoint implementation rather than the resource.]

Schema: 

I suggest that we do <xs:group instead of <xs:complexType. I do not
understand how [CorrelatablePropertiesPropertiesType] is useable by
anybody else. I don't know why is it there if it is not useable.


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


-----Original Message-----
From: vbp@hp.com [mailto:vbp@hp.com] 
Sent: Saturday, November 27, 2004 10:56 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Groups - wd-wsdm-muws-part1-1.0-20041127.doc uploaded

The document wd-wsdm-muws-part1-1.0-20041127.doc has been submitted by
William Vambenepe (vbp@hp.com) to the OASIS Web Services Distributed
Management (WSDM) TC document repository.

Document Description:


Download Document:  
http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/10267/wd-
wsdm-muws-part1-1.0-20041127.doc

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document_
id=10267


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.