OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

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


Subject: Updates to the link contract spec


On the call today we decided to do some updates to the link contract patterns, and also to perhaps add a few more examples.

Since the additional examples were my suggestion, I've pulled up my notes from reading through the spec the other day for the corner cases that I then thought could use examples:

We need an example where the TA is not the RA or the AA

Explains why: Templates provided by neutral third parties make it much easier for link contracts to be standardized, promoting interoperability of XDI vocabulary and permission

We need an example of when a link contract node is an entity collection rather than a singleton

This link contract template pattern examples leave me confused – why is there no operation after the $do$if?

<--template-authority-->{$from}<--template-authority--><--template-id-->$do$if<--boolean-context-->/<--operator-->/<--condition-->

 

This link contract template pattern examples leave me confused – why is there no operation after the $do$if and why is only one member-id shown?  Is that idea that you would do the operation to multiple <member-id>’s? and what is a member-id?

 

<--template-authority-->{$from}<--template-authority--><--template-id-->[$do]<--member-id-->$if<--boolean-context-->/<--operator-->/<--condition-->


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