Extended Relations (revisited)

In respect to the requirement to support Extended Relations [1], the last outcome was to get more Use Cases [2].

I have a real-world use case, but it indicates that we are far from supporting this feature.

Look at this example (music) Subscription Offer [3]. The offer stipulates the Duty to make royalty payments.
If we look at #1 (All-In Royalty) you can see there is an XOR to *either* Pay “A” or “B”. (And in “B” here is also another XOR relationship).
But the XOR relationships are dependent on some other key context (in this case, “which ever is greater/lessor”).

I think for us to successfully support Extended Relations, the current simplistic approach of just XOR/OR of duties and constraints [4] will not meet the these business requirements.


Renato Iannella, Monegraph
Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group

[1] https://www.w3.org/2016/poe/wiki/Requirements#POE.R.DM.10_Extended_Relations <https://www.w3.org/2016/poe/wiki/Requirements#POE.R.DM.10_Extended_Relations>
[2] https://www.w3.org/2016/09/22-poe-minutes.html#item10 <https://www.w3.org/2016/09/22-poe-minutes.html#item10>
[3] https://www.harryfox.com/documents/rate_charts/s_np_so.pdf <https://www.harryfox.com/documents/rate_charts/s_np_so.pdf>
[4] https://github.com/w3c/poe/issues/63 <https://github.com/w3c/poe/issues/63>