This is a reference dialect. Just define a new dialect in the spec. No
reason to have an attribute which is always there, but sometimes true sometimes
false.
-----Original Message-----
From: Vambenepe,
William N [mailto:vbp@hp.com]
Sent: Thu 8/12/2004 9:33 PM
To: wsdm@lists.oasis-open.org
Cc:
Subject:
[wsdm] One more idea on relationships
Here is a potential problem:
I have an EPR to a
resource foo. I ask resource foo to send me the
"containment" relationships
it's involved in. It returns one
relationship to me. This relationship
contains an EPR pointing to the
container and an EPR pointing to the
containee. The trouble is, neither
of these EPR matches the EPR I used to
contact foo. Since there could be
more than one EPR per resource, this is
perfectly possible. How do I
know whether foo is the container or the
containee?
Retrieving the ResourceId may help, but even this is not
guaranteed to
succeed. And it might require more round trips.
I
suggest that we create an optional "self" attribute of type boolean
that
can be placed on a participant in a relationship. By placing it on
a
participant, a resource that sends the relationship indicates that it
is
the participant in question. Obviously, if the relationship is
retrieved
from someone who is not a participant in the relationship, the
"self"
attribute would not appear.
Regards,
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_workgroup.php.