[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 2015-03-27
Following is the agenda for the unofficial telecon of the XDI TC at:
Date: Friday, 27 March 2015 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:
IRC Channel: irc://irc.freenode.net:6667/xdi
On Tuesday Drummond uploaded another draft of the next sections of XDI Core—now finished through the Roots section—that we will review on the call.
You can see where this section fits in the full outline of XDI Core 1.0:
https://wiki.oasis-open.org/xdi/CoreSpecOutline
Joseph has voiced the concern that the current proposed ABNF syntax “overloads” parentheses syntax with several meanings. After the StarShift, which removed nested XDI addresses, the following table summarizes the current uses of parentheses syntax:
Usage | Syntax | Example |
peer root | (_) | (=example) |
URI peer root | (scheme:_) | |
inner root | (_/_) | (=example/#friend) |
URI ID | x(scheme:_) | |
local ID | x(_) | =(foo) |
Joseph has suggested that at least one of these could be replaced by another syntax to reduce the overloading of parentheses. Drummond feels strongly that root syntax should stay consistent, and further that the URI ID syntax is consistent with that. That leaves only local ID as a candidate for using a different syntax.
One option would be to introduce a “local symbol” with usage similar to the immutability symbol “!”, i.e., it would appended after the context symbol (and the optional immutability symbol) to indicate that the identifier scope was local and not global.
Here are examples of the primary options for a local symbol character with examples so you can see how they “read” (the parentheses syntax is included on the last row for comparison):
Local Symbol | = Example | + Example | # Example | * Example |
; | =;foo | +;foo | #;foo | *;foo |
, | =,foo | +,foo | #,foo | *,foo |
^ | =^foo | +^foo | #^foo | *^foo |
. | =.foo | +.foo | #.foo | *.foo |
x( ) | =(foo) | +(foo) | #(foo) | *(foo) |
Immutable + Local Symbol | = Example | + Example | # Example | * Example |
!; | =!;foo | +!;foo | #!;foo | *!;foo |
!, | =!,foo | +!,foo | #!,foo | *!,foo |
!^ | =!^foo | +!^foo | #!^foo | *!^foo |
!. | =!.foo | +!.foo | #!.foo | *!.foo |
x!( ) | =!(foo) | +!(foo) | #!(foo) | *!(foo) |
We will review and make a final decision about local identifier syntax. Note that if you are not able to make tomorrow’s TC call, please indicate your view in a response on the list.
http://xdi.org/xdi-spec-docbook/xdi/xdi-messaging-1.0/xdi-messaging-1.0-wd03.xml
In recent discussions on the XDI2 open source project call, it was suggested that $push might be a better dollar word than $copy for the XDI data synchronization operation.
If there is time, Markus can show a proof-of-concept of a Websocket binding. There are several topics to discuss:
Is there agreement that we should publish a Websocket binding? In which spec?
Will this require defining more about the $copy operation? In which spec?
What will push (pub/sub) connections require in terms of additional link contract semantics?
The next call is next week at the regular time.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]