Hi Nara,<br><br>doing multilateral obligations with /Contract/Party/obligation/to fits for me. It's kinda REST syntax.<br>This solution and the one proposed by Nat are both good if we define wildcards on Nat's, because as Nara said the "any" wildcard would be very useful.<br>
<br>Best regards<br><br>Dave<br><br><div class="gmail_quote">2010/5/11 nara hideki <span dir="ltr"><<a href="mailto:hdknr@ic-tact.co.jp">hdknr@ic-tact.co.jp</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
H, Nat and David.<br>
<br>
I think that /Contract/Party/obligation seems to be better.<br>
<br>
1. easier to grasp stakeholders in a contract<br>
2. each party must sign the contract document and a signature<br>
element must be needed.<br>
3. an obligation could be 1 to N relations. Multiple<br>
/Contract/Party/obligation/to can be used.<br>
4. a party can owe multiple obligation to different parties in a contract.<br>
<br>
One thing we should think of is an obligation to "any party in contract".<br>
Although we can provide every obligation to each party, but a wildcard<br>
is quite useful especially when<br>
the number of parties are big.<br>
<br>
----<br>
hdknr<br>
<br>
2010/5/7 David Garcia <<a href="mailto:david.garcia@tractis.com">david.garcia@tractis.com</a>>:<br>
<div><div></div><div class="h5">> +1 to the second one. I think it's more powerful on multilateral contracts,<br>
> because it allows to define party to party obligations with a fine grain<br>
> detail.<br>
> Best regards<br>
><br>
> David Garcia<br>
> El 07/05/2010, a las 06:36, Nat Sakimura <<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>> escribió:<br>
><br>
> In the current draft, <obiligation> is an child element of <party>. However,<br>
> when we think about the multi-party scenario,<br>
> unless we specify the target that the party is obliged to, it would have no<br>
> meaning.<br>
> Thus, we would have two ways to implement it.<br>
> 1. destination as an attribute.<br>
> <obligation to="partyid"><br>
> 2. Flatten obligations.<br>
> <obligation from="partyaid" to="partybid"><br>
> Which do you think is better?<br>
> From the point of view of writing an application, the second option may be<br>
> easier.<br>
> --<br>
> Nat Sakimura (=nat)<br>
> <a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
> <a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
><br>
> _______________________________________________<br>
> Specs-cx mailing list<br>
> <a href="mailto:Specs-cx@lists.openid.net">Specs-cx@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-cx" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-cx</a><br>
><br>
> _______________________________________________<br>
> Specs-cx mailing list<br>
> <a href="mailto:Specs-cx@lists.openid.net">Specs-cx@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-cx" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-cx</a><br>
><br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>David Garcia<br>CTO<br>Tractis - Online contracts you can enforce<br><a href="http://www.tractis.com">http://www.tractis.com</a><br>--<br>Email: <a href="mailto:david.garcia@tractis.com">david.garcia@tractis.com</a><br>
Skype: deiffbcn<br>Blog: <a href="http://blog.negonation.com">http://blog.negonation.com</a><br>Linkedin: <a href="http://www.linkedin.com/in/davebcn">http://www.linkedin.com/in/davebcn</a><br><br><br>