XDI TC Agenda

Following is the agenda for the unofficial telecon of the XDI TC at:

Date: Friday, 10 January 2014 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:

https://neustar.webex.com/neustar/j.php?ED=203186612&UID=1364257662&PW=NN2Y2NzAxZTVj&ORT=MiMxMQ%3D%3D

AGENDA

NEWS & UPDATES

XDI Tutorial

Markus has worked on an XDI Tutorial:

http://tutorial.xdi.org/

PRESENTATIONS/DISCUSSIONS

Next Steps on Working Drafts

We will discuss the additions/corrections we want to make to produce XDI Core 1.0 Working Draft 02, including:

MIME types for serialization formats.
Formatting improvements.
Adding missing sections.
Improved Github merging process.

“Membership” Statements

Drummond and Markus have worked more on how to express membership of an individual with an organization, including information such as a membership number, and membership expiration date, and premium memberships:

EXAMPLE:

[@]!:uuid:0000/+member/[=]!:uuid:1111

[=]!:uuid:1111/$is+member/[@]!:uuid:0000

[@]!:uuid:0000/+member/([=]!:uuid:1111<+member>&/&/0)

[@]!:uuid:0000[+member]#0/$is/[=]!:uuid:1111

[@]!:uuid:0000/+member/([=]!:uuid:1111<+expiration><$t>&/&/"2015-01-01T12:00:00Z")

Authority-Relative Link Contracts

We will review updates to the link contract patterns to ensure that link contracts are authority-relative:

https://wiki.oasis-open.org/xdi/LinkContractPattern

The “Unauthorized $ref Problem” and “Unbounded $set Problem”

We will return to these and discuss how the new authority-relative link contract patterns affect these two problems.

“Forwarding” of Messages by a Server

If the target peer root specified by a message does not match the peer root that is authoritative for the graph the message is sent to, the message can be “forwarded” to the authoritative server for the peer root. See the following two lines from the XdiMessagePatterns page:

#1: FROM <--from-peer-->/$set/<--from-->[$msg]<--msg-id-->
#2: TO <--from-->[$msg]<--msg-id-->/$is()/<--to-peer→

DECISION POINTS FOR THIS CALL

None scheduled.

DECISION POINT QUEUE REVIEW

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

NEXT CALL

The next call is next week at the regular time.

xdi message