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

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

- I can go with multiple references per participant as long as we make it crystal clear that these are all references to the same resource (and by grouping them together the producer of this relationship element asserts that these references point to the same resource). 

<IS>Yes. I thought that I had a statement like that. If not then +1 to add it. </IS>

Also, we need to specify that if the producer of this relationship element knows of a manageability representation for participants in the relationship it MUST include the EPR to this manageability representation as one of the references for this participant.

<IS>I'm not sure that this is required. You cannot "MUST" me to tell you Heather's social security number even if I knew it :)... First of all what would make you think I knew it? This is not a verifiable assetion. Why have unverifiable assertions in the spec? You could "MAY" or "SHOULD" this...</IS>

- Having roles described as URIs is fine, but the current mechanism has people create 3 URIs in most cases for each relationship type (one for the type and one for each role in the "common" case of directional binary relationships). And I don't find the <Direction/> element too elegant. How about this alternative:
MUWS pre-defines three roles (and assigns URIs to them): a "source"
role, a "target" role and a "participant" role. When people create new relationship types, if the relationship is binary and directional (e.g.
"DependsOn") they use the MUWS-defined "source" and "target". If the relationship is non-directional and has only one role (e.g. "Neighbor") then they use the MUWS-defined "participant" role. In all other cases they create their own roles (and corresponding URIs) as necessary.
As a result we can drop the <Direction/> element. If the relationship is binary and directional (the case in which <Direction/> would be useful) then people who define the relationship type would use the MUWS-defined "target" and "source" role URIs so the consuming tools would know in which direction to draw the arrow.
With this approach we can support the exceptional case where the source, target and participant roles are not enough without making the common case more complex than needed.

<IS>Possible. However it limits one in being able to define a relationship with a semantically defined "role". That is, for example, there is a value in being able to query all relationships where a given participant is the "http://.../container";. Of course that could also be rephrased to querying for all relationships which type is "http://.../containment"; and a given participant is the "muws:source". But then, who says that there are only containment relationships with container as a role... May be there are many more relationships that have container as a role too.</IS>

- In the description of the "manageable" reference type, we need to make it clear that not only is the content an EPR, it is an EPR that points to a manageability representation of the resource (in the MUWS sense of the term).

<IS>Ok. I'll add that.
That is in the WSDM sense of the term manageable :). Also that is manageabilty endpoint as this is an EndPointReference, not RepresentationReference :).</IS>

- Finally a small thing: I assume that minOccurs for <Participant/> is 2 not 1. I know it's not easy to express this in pseudo-schema, but maybe a more correct way to write it is:
<Participant/>
<Participant/>+
Rather then just
<Participant/>+
But it still looks a bit strange.

<IS>ok</IS>

Regards,

William

-----Original Message-----
From: Igor.Sedukhin@ca.com [mailto:Igor.Sedukhin@ca.com]
Sent: Friday, August 06, 2004 12:29 PM
To: wsdm@lists.oasis-open.org
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 #1 of Manageable Relationships for WSDM .doc.

Document Description:
Assembled taking into account the discussion that we had. This one may make everybody happy...
1) N-ary relationships
2) optional directionality
3) many references
4) controllable relationships
5) manageable relationships

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

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php?document_
id=8515

Revision:
This document is revision #1 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_workgrou
p.php.