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] Groups - Manageable Relationships for WSDM .doc uploaded


Here are some comments on the latest version of the relationships 
document. 

1. Section 2: SourceRole and TargetRole

If these attributes are specifying the type of role, should this be a 
QName instead?  This allows you to define the type names within a specific 
namespace.  This also allows you to define a set of type names using XML 
schema.  Here is an example:

  <!-- Containment role types -->
  <simpleType name="Containment">
    <restriction base="QName">
      <enumeration value="muws-role:Container"/>
      <enumeration value="muws-role:Contained"/>
    </restriction>
  </simpleType>


2.  Section 2: Roles

Since it is possible that different roles may implement different 
interfaces to support the role, how would a participant advertise the 
association between the type of role and the interface that supports it? 
For example, a Container may have an interface that is unique to that 
role. 


3. Section 2: Reference element

I can't help but think that allowing more than one Reference per 
Participant may lead to interoperability problems.  Would it be possible 
to require just one reference that contains the resource ID, an optional 
EPR, and extension elements from any namespace?  The namespace for the 
extension elements could be used to understand the semantics of the 
elements instead of using the Dialect attribute.  By doing this, you allow 
references to resources that don't have an EPR (or resources where you 
don't know their EPR) and resources where you do know their EPR.  You also 
can specify reference information that is unique to the resource.

Here's an example of what I mean:

<Reference>
  <ResourceID>xsd:string</ResourceID>
  <ResourceEPR>wsa:EndpointReferenceType</ResourcepEPR> ?
  <xsd:any/> *
</Reference> 


4. Section 3.2: Events

I may have missed it, but is an implementer of the manageable 
relationships capability required to support these events?  Also, does 
supporting these events imply that you need to support a subscription 
interface?


Regards,
Peter Brittenham
IBM




Igor.Sedukhin@ca.com 
08/11/2004 04:42 PM

To
wsdm@lists.oasis-open.org
cc

Subject
[wsdm] Groups - Manageable Relationships for WSDM .doc uploaded






The document revision Manageable Relationships for WSDM .doc has been 
submitted by Igor Sedukhin (Igor.Sedukhin@ca.com) to the OASIS Web 
Services Distributed Management TC document repository. 
This document is revision #2 of Manageable Relationships for WSDM .doc.

Document Description:
Added issue comments from the discussion. Fixed a few sentences. Added 
definition of the control capability.

Download Document: 
http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php/8673/Manageable%20Relationships%20for%20WSDM%20.doc


View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document_id=8673


Revision:
This document is revision #2 of Manageable Relationships for WSDM .doc. 
The document details page referenced above will show the complete revision 
history


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_workgroup.php
.





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