One question I had was whether the server should return an error if the message policy is not met, or simply not execute the message and be silent.
This also takes us to the question of error codes, and I found this page that Mike had created:
https://wiki.oasis-open.org/xdi/MessagingErrorCode
Is this consistent with your thinking, i.e. we would develop a dictionary of such error codes?
Markus
On Sat, Mar 2, 2013 at 1:12 AM, Drummond Reed <> wrote:
Markus, very cool. Quite clean and elegantly done.
=Drummond
On Fri, Mar 1, 2013 at 2:41 PM, Markus Sabadello <> wrote:
I implemented support for message policies in XDI messages.
This means that an XDI client can specify that a message should only be executed if certain conditions are made.
This is the "client-side counterpart" to XDI link contracts.
I.e. instead of the XDI endpoint enforcing a certain policy, the XDI client itself can send a policy along with the message.
See here for Drummond's description of this feature:
https://wiki.oasis-open.org/xdi/XdiMessagePatterns#ConditionalExecutionRules
In the XDI Local Messenger there's an example where you can try this:
http://xdi2.projectdanube.org/XDILocalMessenger?category=5&sample=1
It's a $mod operation that only gets executed if a literal value in the target graph is $greater than 80.
Markus
--
You received this message because you are subscribed to the Google Groups "XDI2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to .
To post to this group, send email to .
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "XDI2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to .
To post to this group, send email to .
For more options, visit https://groups.google.com/groups/opt_out.
