[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes: XDI TC Telecon Friday 2014-06-06
Following are the minutes of the unofficial telecon of the XDI TC at:
Date: Friday, 6 June 2014 USA
Time: 09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)
Drummond Reed
Les Chasen
Hubert Le Van Gong
Will Martin
Joseph Boyle
Markus Sabadello
Dan Blum
Phil Windley
Eno Jackson
Brian Wu
William Dyson
Matthew Sutton
Peter Davis
None scheduled.
Introductions of William Dyson, Eno Jackson, and Brian Wu
Dan has uploaded version 4 of the XDI policy draft:
https://www.oasis-open.org/committees/document.php?document_id=53237&wg_abbrev=xdi
Dan also posted a list of preparatory questions:
https://lists.oasis-open.org/archives/xdi/201406/msg00001.html
Dan provided some context on the current status of the Policy spec.
Deadlines and Quality Expectations for Working Drafts
We discussed the benefits and tradeoffs of putting out early Working Drafts that are incomplete and contain substantial questions, issues, and open areas.
Editors are encouraged to post works in progress (with health warnings) as working drafts for all version 1 specifications identified on the wiki before June 23, so that XDI can make a good showing when it is widely publicized in the news as expected during the period of the Respect Network launch.
It is ok for these working drafts to be works in progress. Editors should communicate health warnings to reader so that they can assess the maturity of a spec.
Once a Working Draft Spec is available, out of date content in any XDI TC wiki page should be replaced by the editor of the document with a reference to the appropriate sections(s) of the current Working Draft. Where possible, that wiki page should also contain a easily-digestable summary of the topic
Joseph asked about the syntax we are using for variables in specification template code, i.e., for “spec variables” vs. “XDI variables”.
Joseph’s suggestion is to start using ALLCAPS in bold.
Phil suggested using a colon as the prefix character, however a colon is a legal XDI syntax character, so the worry is that it would cause confustion.
Drummond’s suggestion is that we combine these suggestions by using % as the prefix character (since it is not a legal XDI syntax character except for escape encoding, which should not appear in spec templates), plus ALLCAPS in bold, e.g., %FROM. The reason for the prefix character is that it allows multiple variables to appear contiguously (as we do have in some spec templates).
Example of old approach:
<--from-peer-->/$set/<--from-->[$msg]<--msg-id-->
Example of new approach:
%FROM-PEER/$set/%FROM[$msg]%MSG-ID
https://wiki.oasis-open.org/xdi/XdiOneSpecs
https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook
XDI signatures
Continue to discuss Peter’s updated XDI signature proposal:
https://lists.oasis-open.org/archives/xdi/201405/msg00030.html
The next call is next week at the regular time.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]