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] Is componentAddress required?


Responses below:

Thomas W. Studwell
Senior Technical Staff Member, Autonomic Computing Architecture
IBM Software Group
C151/Bldg 500
4205 S Miami Blvd, Durham, NC 27703
(919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038
studwell@us.ibm.com

"What marks the mind of the strategist is an intellectual elasticity or flexibility that enables him to come up with realistic responses to changing conditions... In strategic thinking, one first seeks a clear understanding of the particular character of each element of a situation and then makes the fullest possible use of human brainpower to restructure the elements in the most advantageous way." (Keniche Ohmae, The Mind of the Strategist)
Inactive hide details for "Vambenepe, William N" <vbp@hp.com>"Vambenepe, William N" <vbp@hp.com>


          "Vambenepe, William N" <vbp@hp.com>

          11/18/2004 04:08 AM


To

<wsdm@lists.oasis-open.org>

cc


Subject

RE: [wsdm] Is componentAddress required?

 
And yes I noticed that the spec says "This is a REQUIRED property if the
component is addressable" but this really doesn't mean anything.
Anything one can talk about is addressable by some (potentially yet to
be invented) addressing scheme.

<tws>ok, then the element is REQUIRED.  We added this text because someone in the TC claimed there could be resources that are not addressable and therefore this should be optional. So it is OPTIONAL if there is such a device.  You claim that all devices are addressable so that would make this REQUIRED.</tws>

Also, I need an explanation of this:

ManagementEvent/sourceComponentId/componentAddress/{any} - XML open
contents to include any XML representation of the component address. The
commonly used addresses are either basic Web service address,
wsa:EndpointAddress, or the address of a manageable resource,
muws:ManageabilityEndpointReference.

AFAIK (and I should know), there is no ManageabilityEndpointReference in
MUWS.

<tws>Again, this was added at the request of someone (the same person I might add) who claimed there is a muws:ManageabilityEndpointReference.  I am ok to remove the reference to this non-existent type.</tws>

Also, I have a remark about this definition:

ManagementEvent/reporterComponentId - this is the identification of the
component that is the "reporter" of the event or the situation. This is
a REQUIRED property only if the reporting component is different than
the source component. Otherwise, this element is OPTIONAL. This element
is of the same XML Schema complex type as the
ManagementEvent/sourceComponentId element.

Does this mean that if I don't see a reporterComponentId I know that the
reporter is the same as the source? What about the case where the
reporter doesn't want to (or doesn't have a way to) report who it is but
is still different from the source? I don't think we should assume that
no reporter means reporter=source.

<tws>If there exists a Web service that is capable of emitting a ManagementEvent it does know WHO it is and is required to identify itself.  It is ludicrous to think there could be WSDM events reported anonymously.</tws>

BTW I took the liberty to rename sourceComponentId and
reporterComponentId to sourceComponent and reporterComponent because one
common case is when this contains an EPR and, as Francisco Curbera very
pointedly explained on the WS-Addressing mailing list an EPR is not an
Id
(
http://lists.w3.org/Archives/Public/public-ws-addressing/2004Nov/0355.h
tml). Let me know if this is a problem.

<tws>I'm ok with the name change but I'm not sure I agree with the reason.  The EPR is an element within the ComponentIdentification (componentAddress), not the Identification itself.</tws>

William


-----Original Message-----
From: Vambenepe, William N
Sent: Thursday, November 18, 2004 12:22 AM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Is componentAddress required?

The pseudo-schema and the UML show that componentAddress (inside
sourceComponentId or reporterComponentId) is optional (0 to unbounded)
but the current description says it's required. Which one is right.

I think it should be optional. It's ok if I only want to send the
ResourceId.

William

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.


GIF image



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