OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Minutes: XDI TC Telecon Friday 2015-03-20


XDI TC Minutes


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


Date:  Friday, 20 March 2015 USA
Time:  09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)

ATTENDING

Ning Zhang
Drummond Reed
Markus Sabadello
Peter Davis
Phil Windley
Les Chasen
Joseph Boyle

AGENDA

PRESENTATIONS/DISCUSSIONS

Review of the XDI Core Spec “Entities” Section

Drummond upload a draft of the next section of XDI Core—the Entities section—to review on the call.

https://www.oasis-open.org/committees/download.php/55319/draft-xdi-core-spec-sections-2015-03-19.docx


You can see where this section fits in the full outline of XDI Core 1.0:

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


Drummond ran through the new material in the Entities section. There were the following comments:


We also briefly reviewed the start of the Attribute section that Drummond has started drafting. Markus liked the introduction but felt that the definition of XDI attributes as “reifying” RDF predicates whose target was a literal node was distracting and confusing. Drummond agreed to rewrite it.

XDI Messaging Spec

Markus gave a status report of his work on XDI Messaging 1.0 WD03:

http://xdi.org/xdi-spec-docbook/xdi/xdi-messaging-1.0/xdi-messaging-1.0-wd03.xml
https://wiki.oasis-open.org/xdi/XdiMessagePatterns


Markus explained how he envisions a section about message patterns that are common to both request messages and response messages, and then one additional section each for request and response messages.

In particular he reviewed the opening section where he introduces the key terminology needed to describe XDI messaging patterns. This terminology would be independent of any particular binding. The one term that we felt needed revising was his use of “XDI authority”, e.g., where the specs says, “XDI messages are sent between XDI authorities”. Drummond said that the actual message traversal is between two XDI endpoints, but Markus felt that was too low-level—his intent is to express the logical senders and recipients of messages.

Drummond suggested that “XDI messages are sent between XDI graphs”, but it was felt that was too literal. Joseph pointed out that the XDI graphs are not the actual agents or actors involved in sending and receiving the messages, and advocated that we call the senders and recipients “agents” or “actors” to be consistent with industry terminology.

There was agreement that the senders and recipients are indeed agents or actors, but that those terms are generic and do not reflect the specific nature of XDI peer-to-peer messaging architecture. Drummond suggested using the term “peer” as a more precise term for an XDI agent or actor that sends/receives XDI messages.

Markus will continue to advance this new draft of XDI Messaging as far as he can before our April 8 meeting at Internet Identity Workshop in Mountain View, CA (and online via Webex).

NEXT CALL

The next call is next week at the regular time.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]