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] MUWS Comments part 2


William,

My comments on part 2.  Most of them are typos or cosmetic changes.  However, I think state and status capabilities need more work.

3.2.4. I don’t understand what you’re suggesting here?  We have a capability that has no properties in it?  What about the 2 that you just defined – state and statetransition?  I agree that the state values should be defined by the managed resource owner.  But how would the manager know where to go to get the state information if it doesn’t know how to ask for it?

3.3.1. I disagree with the language that the operational status is "independent of the specific state model used".  I think it would be dependent but it is not a direct mapping.

Cheers,
H.
--

Zhili Zhang wrote:
Hi William,
 
Here are my comments on document wd-wsdm-muws-part2-1.0-20041126.doc.
 
(1) In the WSDL, the following resource property documents from namespace "http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" are referenced in various portTypes. However, they are not defined in that namespace.
 
muws-p2-xs:DescriptionProperties
muws-p2-xs:MetricsProperties
muws-p2-xs:RelationshipsProperties
muws-p2-xs:RelationshipResourceProperties
 
(2) QName "xml:lang" is used in schema. Strictly speaking, the XSD should have the following import statement:
 
 
Otherwise, several schema validators will give the following error:
#src-resolve.4 QName reference "xml:lang" can't be resolved as namespace "http://www.w3.org/XML/1998/namespace" wasn't imported. (see http://www.w3.org/TR/xmlschema-1/#src-resolve)
 
Other validators like .NET may work well with it. However, a simple fix like this will make WSDM schemas solid.
 
(3) The namespace table in Introduction section (page 5) lists namespaces for ServiceGroup (wssg), etc. Couple of others are missing from the table, such as wsrf-rp, wstop, wsa.
 
(4) Should we insert OASIS legal disclaimer into normative XSDs, WSDLs, topic instances? Schemas and WSDLs from other groups like WSN, WSRF have it.
 
Thanks
Zhili
 
 
 
-----Original Message-----
From: Heather Kreger [mailto:kreger@us.ibm.com]
Sent: Monday, November 29, 2004 12:24 PM
To: vbp@hp.com
Cc: wsdm@lists.oasis-open.org
Subject: [wsdm] MUWS Comments part 2


Here are my comments on MUWS Part 2.



My biggest issues are:

1. In Platform Properties - addresses addressing more that properties, split out into two sections and make more normative references to resource properties specs.
2. Need Topics in the events section.
3. Configuration is missing half its section
4. Advertising is missing advertisement by registration

Heather Kreger
STSM, Web Services Lead Architect for SWG Emerging Technologies
Author of "Java and JMX: Building Manageable Systems"
kreger@us.ibm.com
919-543-3211 (t/l 441)  cell:919-496-9572

wd-wsdm-muws-part2-1.0-20041126.doc

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]