XDI TC Minutes

Following are the minutes of the unofficial telecon of the XDI TC at:

Date: Friday, 25 April 2014 USA
Time: 09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)

ATTENDING

Drummond Reed
Dan Blum
Hubert Le Van Gong
Peter Davis
Joseph Boyle
Will Martin
Les Chasen
Markus Sabadello

GUESTS

REGRETS

Phil Windley
Animesh Chowdhury

NEWS & UPDATES

None scheduled.

PRESENTATIONS/DISCUSSIONS

Tour of XDI TC Jira

Peter gave an introduction on how we are going to use the XDI TC’s Jira system to manage issues during the spec drafting process:

https://tools.oasis-open.org/issues/browse/XDI

The “My Open Issues” page is probably the one we would be using most of the time.

Peter recommends that we will use the Jira issue list to drive the agenda of our weekly calls.

Project: OASIS XRI Data Interchange

Issue Type: Bug, Improvement, Task

Issue Status: commonly New → Open → Resolve (e.g. “Fixed”) → Applied → Closed

Summary: Make it meaningful, since it will show up in the issue list

Priority: Major, Minor

Due Date: Probably not necessary for our purpose

Components: The document (spec), can be more than one

Version: 1.0

Assignee: Automatically assigned to the lead of the component

Reporter: You

Description: General description of the issue
Proposal: Optionally a proposal of new content

Label: Arbitrary keywords for the issue

All of the above is typically static after the issue is created. The main work and discussion will happen via the “comment” mechanism. When you get the comment via e-mail, you can reply to it, and it will become a new comment in Jira.

Editors would probably look at all issues related to a certain document, rather than all issues assigned to them.

Filters can be useful to create views of certain issues that are relevant to you. You can subscribe to filters, which means you will get notified if something changes in the view.

We can use any editor we want, but all documents we want to review on a TC call should be uploaded in the OASIS Kavi system (e.g. an exported PDF or HTML file).

Spec weekly scrum status report

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

https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook

Status previously:

Markus: no actions

Joseph: working on the Messaging spec; would like to talk to Hubert on Monday; still working on revisions on Core that Markus requested.

Will: started scanning Core and will be doing a review of Discovery so he can form list of key questions.

Dan: has produced an outline for the privacy mechanisms spec; has taken the link contract patterns and started working on them; the Policy spec is also moving forward. He also did a symbol shift of the Graph Patterns Powerpoint.

Hubert: (same)

Peter: in process of restructuring XDI Signature that will cover both signatures and encryption; reviewing for other security action items; aiming to have first working draft for next week

Les: (on vacation this week)

Drummond: began reviewing Core for additional action items; noted the need to specify URL encoding rules for XDI addresses since there will no longer be an external to spec to reference. Other action item is to review Dan’s graph diagrams and get Joseph what he needs for core.

Status this week (to be filled out during the call):

Markus: Will practice the Jira processes we discussed

Joseph: Still working on messaging..

Will: Generating docbook outline from wiki pages, will flesh out and make more specific

Dan: Worked on XDI Policy draft (Google Doc), will work on XDI Privacy Mechanisms

Hubert: Started XDI Bindings docbook file, will look at Joseph’s work on messaging and coordinate with him

Peter: Worked on Jira setup, some progress with XDI Security Mechanisms; talked to Dan about tension between running code and spec requirements

Les: Dependency on Drummond’s work

Drummond: Working PPT and PDF of graph annotation format to get to Joseph; help Joseph add the following XDI Core 1.0 issues to Jira:

Section 2.7, note at the end – change the reference to Binding
URI normalization rules for xrefs
Graph notation format (in progress)
Normalization of all character sets to lowercase

Privacy Mechanisms

Dan asked if requirements for data use should be covered by the spec, e.g.: “If you use data, you have to encrypt it” or “If you use data, you have to anonymize it”

What do you call such requirements?

“Data use policies”, “Obligations”, “Output controls” ?

It seems there may be different types of policies that control different aspects of XDI data and XDI messaging:

1. Link contract policies: Used by link contracts for authorization decisions; enforced by an XDI authority

2. Message policies: Used for conditional execution of XDI messages; supplied by an XDI client

3. (see above) Data use policies: After you obtain XDI data, you are subject to certain obligations

Dictionary

How do we define our $ words in the specs?

- Should we have all $ words defined in a single place (e.g. the Dictionary spec itself)
- Or should each spec have a special section or appendix where it defines its own $ words?

NEXT CALL

The next call is next week at the regular time.

xdi message