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: MOWS Document Comments

This feedback is organized similar to the MUWS comments.  Items 1-8 are
issues needing some discussion or at least verification, and items 9 and
10 indicate grammar errors and one minor clarification. 

Feedback on the Management Of Web Services:

1. Since every requirement references "Manageability Representation", it
is really important to define it clearly.  In fact, I believe that it is
the same as the "manageability capabilities" of MUWS, but adds the
abstract semantic definition (information modeling) on top.  Of course,
I may be totally wrong in this and need to be reset.

2. I think that it is problematic to have a central term, "manageability
representation", and headings that use this term, 2.1 Manageability
Representation and 2.1.3 Representation.  The entire document is about
"manageability representation".  We need to rename sections 2.1 and
2.1.3 (perhaps to "Model" and "Capabilities and Perspectives",

2. Page 8, Overall 1 - The requirement distinguishes between "management
and provisioning". It seems that management includes provisioning.
Should provisioning instead be specifically added to the list of
capabilities in Overall 3?

3. Page 5, last paragraph (continuing on page 6) - This text does not
seem to fit in a "glossary" section.  It should be moved/removed.

4. Page 8, Overall 2 - Clarify that a "specific model representation" is
really a specific "data model" representation and the example is "(e.g.,
CIM-XML)" and not CIM directly.  In fact, CIM itself IS expressed as a
UML-based model - since MOF is only a textual rendering of UML.

5. Page 8, Met 1 - Is the MUST requirement that metrics exist but that
they may only be defined in specific data models?  Otherwise, I think
that we have to define some base metrics and their semantics.  It does
not make sense to say that the representation MUST have metrics, but
that none are specified in the UML abstraction.  Since Met 1 is a MUST,
doesn't this mean that there is some minimum set of metrics (defined in
support of Met 6) that MUST be implemented?  If so, we should be
explicit about this in the requirements.

6. Page 9, Mod 6 - Can this be clarified to indicate that we are talking
about information encoding and wire transmission (ie, bindings)?
Perhaps saying "The manageability representation MUST NOT be tied to a
specific XML Schema representation, binding and/or interface"?? 

7. Page 10, Chng 6 - The text "all or nothing" reads to me as
transactions.  This seems to indicate that transactions SHOULD be
discussed in MUWS. If something else was intended, this is not clear.

8. Section 4 should be removed in lieu of explicit references to MUWS.
If we want to further clarify MUWS requirements or make them stronger
(SHOULD to MUST), then we should reference the MUWS requirement
directly.  I don't think that it is acceptable for MOWS to dictate a
MUST or SHOULD that it not at least a SHOULD or MAY in MUWS. 

9. There are some grammar issues:
- Page 4, First paragraph - Should end with ":" since the following 
	sub-headings supply the info indicated in the sentence
- Page 4, under "deliverables" sub-heading - Should be a period after
	Jan 2004, and "this includes ... " should be the start of a new
	sentence (with appropriate capitalization)
- Page 4, second sentence under "Initial Focus" - Is a run-on and
	should be changed to past tense.  The sentence should be
	as "However, it is expected ... will also need to be addressED
	in the tenure of the WSDM TC. These include, but are ..."
- Page 5, second paragraph under "WSDL described web service" -
	in the second sentence should be plural (ie, "A binding, ..., is
	accessible via one or more endpointS ..."
- Page 9, Mod 1 - Remove the "a" before "consumer"
- Page 10, Life 7 - Suggest rewording as follows: "The manageability
	representation SHOULD support a "ping" to a Web service that
	does not change the service's state"

10. One item needs clarification:
- Page 10, Life 8 - Needs to be rewritten as a sentence with a MUST.


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