XDI TC Agenda

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

Date: Friday, 13 December 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:

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

AGENDA

NEWS & UPDATES

None scheduled.

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.

Static Semantic Rules

Joseph cited the following in an email to the list:

https://mail.mozilla.org/pipermail/es-discuss/2013-December/035126.html

He explains:

This provides the term "static semantic rule" to describe non-ABNF rules such as:

the subject and object of a contextual statement must yield a valid XDI address when concatenated by removing the // between them
a statement whose object is parentheses enclosing a syntactically valid XDI statement, is semantically equivalent to a rearranged statement using inner roots

The first does restrict the set of syntactically valid XDI statements, even though it is called a semantic rule. The second does not reduce the set of all valid XDI statements, or could be viewed as increasing it from a more basic smaller set not allowing triples in parentheses as objects.

The mail gives ignoring insignificant whitespace as another example of a static semantic rule, which could alternatively be implemented using syntax diagrams ("racetrack diagrams", which are equivalent to BNF). In the XDI case we have never attempted to add it to the ABNF, but have always had it as a static semantic rule external to the ABNF.

We will discuss how this applies to XDI Core 1.0.

Merging Graphs and Graph-Relative vs. Authority-Relative Statements

We will contain discussion about whether certain statements in an XDI graph should be “graph-relative” or “root-relative”, e.g.:

<$public><$key>&/&/”...”

or “authority-relative”, e.g.:

=markus<$public><$key>&/&/”...”

“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-->

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

We will return to these and determine next steps.

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