Minutes: XDI TC Telecon Thursday 1-2PM PT 2008-07-10

["Drummond Reed" <drummond.reed@cordance.net>]

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

Date:  Thursday, 10 July 2008 USA
Time:  1:00PM - 2:00PM Pacific Time

ATTENDING

Bill Barnhill 
John Bradley 
Jeff Hodges 
Drummond Reed 
Markus Sabadello
Tatsuki Sakushima
Giovanni Bartolomeo
Paul Trevithick

REGRETS
Peter Davis

AGENDA

1) STANDING RULE BALLOT

TC Administrator Mary McRae has suggested we have a ballot on the following
Standing Rule in order to formalize our informal meeting schedule:

	"Standing Rule: Does the TC wish to adopt a standing rule to conduct
regular business only by electronic ballot, without Meetings, with the
exception of Meetings called for a special purpose with a minimum of 15
calendar days notice?"

# DRUMMOND to post the a ballot.


2) XDI RDF LINK CONTRACT BASIC PATTERN

Our tech topic for the day was a very core one: confirming the basic pattern
of XDI link contracts in the XDI RDF model. This has been assigned Issue #4
on and a proposal written up at:

	http://wiki.oasis-open.org/xdi/XdiOneIssues/LinkContractPattern

John asked a question about how the XDI contexts displayed there would be
addressed.

# DRUMMOND to add text to the page giving an example.

Bill noted that the very simple contract example did not suggest how to
handle more complex policies such as:
* Finer grained access control by factors such as time of day
* Access control by attributes of the policy subject.

John noted that in his experience with ATI link contracts, he has seen
requirements for policies that:
* Provide permissions based on reciprocity.
* Provide permissions based on about the policy subject (example: make
medical information available to an Emergency Medical Technician (EMT) on
the basis that they can prove they are an EMT).
* Make request to a resource that is dynamically identified, i.e., doesn't
have a fixed i-number.

John also noted the need for contracts to have signatures, i.e., that Bob
signings the contract to indicate his agreement. If both parties take on
obligations; then both parties have to sign. Also, a contract may require a
third party to approve by signing the contract.

He also noted that is may be better to separate contract assignments from an
instance of the contract itself.

Bill asked if we had a collection of link contract use cases. Drummond noted
that a number had been submitted early in the TC's history but not formally
collated. Bill suggested we collec standard XP user stories that capture
link contract use cases and requirements before we go further into
discussing the design and specification.

Bill sent the following link to the XP user story format:

	http://agilesoftwaredevelopment.com/node/422 

# DRUMMOND to create a page for link contract use cases in this format.


3) SUMMER CALL SCHEDULE

Drummond explained that he needs to take a six week sabbatical for travel,
summer vacation, and to handle a number of domestic chores. There was a
consensus that we should take a hiatus from telecons for six weeks and then
restart in August. In the meantime work should continue forward on all the
current topics in play, and use of the list for discussion is encouraged.

# DRUMMOND AND BILL to send a message when telecons will restart.