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: Company review comments


All,

 

Here is an elaboration of the comments that I will be submitting to the company review for WSDM MUWS 1.1 (and which I presented during the conf. call yesterday).

 

  1. MUWS Part 1, line 127, “car engine” is not an intuitively obvious example of an “IT resource”.

 

  1. The current definition of WSRF Resource, “a resource defined as the actual composition of a resource and a web service from which the resource can be accessed,” is virtually a word-for-word quote of the definition of WS-Resource in WS-Resource specification.  I don’t see why we are introducing a new term for a technical concept in another specification.  This leads to confusions, e.g., in MUWS Part 2, lines 131-133, we have the following passage:

 

A manageable resource is a refinement of a WSRF resource. A WS-Resource is defined as the actual composition of a resource and a web service from which the resource can be accessed. 

 

            There are several problems here for the reader.  Going from “WSRF Resource” to “WS-Resource” in the text sentence is a little rough unless the reader understands the relationship between the two.  And, oh, yes, they happen to be exactly the same thing!!  The definition of WS-Resource is exactly the same as WSRF resource.  So why are there two different terms for same thing?  The term “WSRF Resource” resource should at least be changed to WS-Resource in line 128 of Part 1.

 

            I suspect that what is intended by “WSRF resource” is really what the WS-Resource specification defines as a “resource”.  (The WS-Resource specification defines two terms “resource” and “WS-Resource”.)   A “resource” is defined as:

 

A resource is a logical entity that has the following characteristics:

It MUST be identifiable.

It MUST have a set of zero or more properties, which are expressible in XML infoset.

It MAY have lifecycle.

 

            If a WSRF Resource is what WS-Resource spec defines as a resource, then I would suggest modifying the definition of WS-Resource to read: a resource defined as the actual composition of a WSRF Resource and a web service from which the resource can be accessed, which I believe is the intended interpretation of the WS-Resource specification.

 

            This leaves the question of what is a WSDM resource?  I believe the intention is still is say that it is a WSRF Resource; therefore the definition of WSDM resource and the first sentence in the passage quoted above from Part 2 can remain unchanged.

 

  1. The definition of Manageability capability interface (lines 143-144) should be deleted.  This concept is no longer used in the specification.  The definition of manageability interface should be changed to:

 

A Web service interface that exposes one or more manageability capabilities.

 

            This definition fits all usages of the term throughout the spec.  (“Manageability capability interface” has no further occurrences in the spec.

 

Kirk Wilson
CA Inc.
Architect, Development
Office of the CTO
Tele: + 1 603 823-7146
Fax:   + 1 603 823-7148
<mailto:kirk.wilson@ca.com>

 



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