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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

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


Subject: Minutes: XRI TC Telecon 8-9AM PT Thursday 2008-09-25


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

Date:  Thursday, 25 September 2008 USA
Time:  8:00AM - 9:00PM Pacific Time

ATTENDING

John Bradley 
Markus Sabadello 
Nick Nicholas
Drummond Reed 
Nat Sakimura 
Nika Jones
Peter Davis
Marty Schleiff 
Les Chasen


AGENDA

1) PILIN

Nick Nicholas gave us some background on PILIN, a project set up in
Australia for persistence infrastructure for the library and e-learning
space. 

	https://www.pilin.net.au/ 

He explained that PILIN's research led them to decide they needed to be able
to formulate a policy for identifier persistence that was not bound to any
specific identifier or protocol. That's what took them in the direction of
abstraction.

The relevance of XRI is that it proposes an embodiment of abstract
identifier architecture in which the PILIN team is interested.


2) XRI AND OPENID AUTHENTICATION 2.1

We had a short followup to last week's discussion about XRI and the possible
OpenID Authentication 2.1 work. The consensus is still that OpenID discovery
should be an integral unit that supports all forms of OpenID identifiers. In
particular Nat said that XRI should not be factored out due to its strong
security features. Also, there was consensus that next version of OpenID
should factor out discovery into a separate spec.

# DRUMMOND to pass that feedback on to David Recordon.


3) XRDS DISCOVERY UPDATE

We had a short discussion about Eran Hammer-Lahav's blog post:

	http://www.hueniverse.com/hueniverse/2008/09/discovery-and-h.html 

There was consensus that the discovery problem highlighted there is in fact
only a problem when concrete http(s): URIs are used to identify an abstract
resource. When XRIs are used to identify the abstract resource,
it does not violate Web architecture to request the XRDS descriptor directly
over HTTP(S) using an Accept header asking for an XRDS document.

This is explained in more detail in the content on our Abstract Identifier
Architecture page (see below).


4) W3C TAG DISCUSSION/ABSTRACT IDENTIFIER ARCHITECTURE PAGE

We reviewed the new content posted last weekend to:

	http://wiki.oasis-open.org/xri/AbstractIdentifierArchitecture

In particular we discussed the graphic and the table. The graphic
illustrates the fact that the descriptors to which abstract identifiers
resolve are themselves concrete resources that can have concrete
identifiers, precisely the way XRDS documents have their own URLs today. The
diagram makes it clearer to see the relationship between these descriptors,
the abstract resources they describe, and the concrete resources that they
locate.

John suggested that the next step was to take this graphic and illustrate
specifically how it applies to XRI, and what they corresponding identifiers
at the http(s): URI level will look like.

Nick pointed out that the DOI descriptor identifier needed parameters to
actually address the metadata.

# DRUMMOND to fix. (DONE)


5) NEXT MEETING

John and Drummond will be at the OASIS Open Standards Forum in London next
week, so Peter will handle the agenda and minutes (John and Drummond may or
may not be able to join the call).



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