[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XDI TC Unofficial Telecon Agenda: Monday 10:00 - 11:30AM PT 2015-09-21
Following is the agenda for the unofficial telecon of the XDI TC held on:
Date: Monday, 21 September 2015 USA
Time: 10:00AM - 11:30AM Pacific Time (17:00-18:30 UTC)
The TC operates under a standing rule approved 17 July 2008 under which the TC does not hold regular official meetings and conducts all business by electronic ballot only. Unofficial weekly meetings are held to enable discussion among members but no business is conducted nor actions taken.
THE LINK TO THIS AGENDA AND LIVE MEETING NOTES IS:
https://docs.google.com/document/d/1t5Mx0ITqJdLwo8wM5GD9lcqehgbgnrhk-k2sERwc7J0/edit
Link to join from PC, Mac, iOS or Android:
Or join by phone:
+1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 925 461 490
International numbers available:
https://zoom.us/zoomconference?m=9Lut7KQe_7FL6dRPEpvRh6OJU7UFyFPN
IRC Channel: irc://irc.freenode.net:6667/xdi
Drummond has uploaded the latest draft:
https://www.oasis-open.org/committees/document.php?document_id=56520&wg_abbrev=xdi
The new section is the Namespace Architecture section of XDI Addressing.
The main sections remaining for Drummond to draft are:
Internationalization
Canonicalization
IRIs
XDI Schemes
Versioning
In preparing to write the Identifier Canonicalization section of XDI Namespaces, Drummond proposes that the TC adopt the following rules for “extreme canonicalization” XDI identifiers because this will ensure the fewest false positives and false negatives in identifier matching:
Only allow digits, lowercase letters, and three symbol characters (dot, dash, and underscore) in native XDI identifiers in the ASCII range. Uppercase characters MUST be escape encoded (thereby preserving uppercase letter matching for systems that need it).
Characters above the ASCII range MUST apply the most stringent form of Unicode normalization (as specified by Joseph).
IRIs used within XDI addresses (in parentheses) MUST be normalized according to their scheme.
So far, we have been using XDI variables to act as placeholders for (one or more) XDI context nodes. Markus has come across a use case where we may want to also use XDI variables for literal nodes (e.g. in link contract instantiation). The challenge here is that XDI variables are themselves context nodes, not literal nodes. Markus will explain further and ask for feedback on a proposed solution.
Markus has finished his “change of address walkthrough” and is now working on completing the original “messaging walkthrough”. See:
https://wiki.oasis-open.org/xdi/MessagingWalkthrough
https://wiki.oasis-open.org/xdi/ChangeOfAddressWalkthrough
The next call is next week at the usual time (Monday 10AM PT). The link to where agenda items can be posted for the next meeting is: https://docs.google.com/document/d/19oDl0lbb56Grehx2a5flZnhrgnua5l8cVvC_dJ8fTXk/edit?usp=sharing
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]