[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda: XDI TC Telecon Friday 09:00 - 10:30AM PT 2013-10-18
Following is the agenda for the unofficial telecon of the XDI TC at:
Date: Friday, 18 October 2013 USA
Time: 09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)
THE LINK TO THIS AGENDA AND LIVE MEETING MINUTES IS:
https://docs.google.com/document/d/1t5Mx0ITqJdLwo8wM5GD9lcqehgbgnrhk-k2sERwc7J0/edit
THE WEBEX INSTRUCTIONS FOR THIS MEETING ARE:
1. Go to https://neustar.webex.com/neustar/j.php?ED=203186612&UID=1364257662&PW=NN2Y2NzAxZTVj&RT=MiMxMQ%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: 5474
4. Click "Join".
5. Follow the instructions that appear on your screen.
To view in other time zones or languages, please click the link:
Drummond will report on planned sessions next week at Internet Identity Workshop in Mountain View.
Report on progress on XDI Core and XDI Messaging.
Drummond added the Message Type statement to the XDI message pattern block on:
https://wiki.oasis-open.org/xdi/XdiMessagePatterns
Drummond, Markus, and Animesh will report on a proposal revision to the standard link contract pattern that arose from of their implementation work:
https://wiki.oasis-open.org/xdi/LinkContractPattern
Last week we concluded with this proposed solution to the “unauthorized $ref problem”:
If a message requests a $set operation on an equivalence relation ($is, $ref, or $rep) that crosses XDI authority graphs, the requesting party MUST be authorized by a link contract permitting this operation on the target graph just like any other authorized XDI operation.
We took the general action item to consider precisely how this rule will be implemented and discuss it on this week’s call.
Drummond makes the following proposal:
A link contract with $all permission includes all equivalence relation permissions.
Otherwise, the following permissions must be explicitly declared:
$set{$is}
$set{$ref}
$set{$rep}
Drummond proposes to solve this problem exactly the same way as above except the operation that must be permitted is $set($do}.
After our syntax simplication last spring, all XDI context functions used exclusively bracket syntax EXCEPT dictionary definitions.
(=markus) <== root
[+passport] <== collection
<+tel> <== attribute
{foo} <== variable
$(+passport) <== definition
It would be cleaner and easier if there was also a uniform bracket syntax for definitions. One option would be to use double brackets:
[[+passport]] <== definition
Markus suggested another option of using pipes:
|+passport| <== definition
However Drummond proposes a different solution, which is to solve the problem by defining a single standard dictionary context node identified by the
++passport <== generic entity definition
+<+tel> <== generic attribute definition
+=person <== personal definition namespace (mutable)
+[=]!1234 <== personal definition namespace (immutable)
+@legal <== legal definition namespace (mutable)
+[@]!1234 <== legal definition namespace (immutable)
The decision queue stack is shown on the following three auto-generated Category pages:
https://wiki.oasis-open.org/xdi/CategoryLastCall
https://wiki.oasis-open.org/xdi/CategoryCurrent
https://wiki.oasis-open.org/xdi/CategoryHighPriority
See also this list of proposals that need to be developed:
https://wiki.oasis-open.org/xdi/XdiPendingIssues
The next call is next week at the regular time.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]