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: RE: [xdi] Agenda:Joint XRI & XDI TC Telecon 10AM PT Thursday 2007-09-27


In the breadth and depth discussion ....  I disagree with this
statemtent ...

"If a ref is followed successfully but the result does not satisfy the
original resolution query, the resolver MUST follow any other ref of
LOWER (not equal) priority in the selected SEP. The reason for excluding
other refs of equal priority is that they represent the same logical
result of the ref that was already tried."

... All refs regardless of priority should be followed.  It does not
make sense to state that REFs that happen to have the same priority by
definition have the "same logical result".  Besides that these types of
rules just add complexity in understanding meaning in the XRD.

Regarding the removing of the authority REF, I can't think of a solid
'why not' reason except backward compatibility.   I am not certain how
many REFs we have in the world today but do we want to break those that
do?

It just occurred to me that service REFs have a cardinality of 0-N.  I
think maybe it should be 0-1.  We should not need multiples for
redundancy since that is handled better in other protocols such as
authority resolution in the case of an XRI and DNS resolution in the
case of a URL.  If you make this change and remove authority REFs (which
I am not comfortable with yet :)) than the breadth discussion becomes
moot.

On the topic of the Refs attribute, what does a negative value mean in
regards to the XRDS outputted by the resolver?   How are *all* matched
SEPs indicated?






contact: =les
sip: =les/(+phone)
chat: =les/skype/chat
 
 
> -----Original Message-----
> From: Drummond Reed [mailto:drummond.reed@cordance.net]
> Sent: Thursday, September 27, 2007 4:05 AM
> To: xri@lists.oasis-open.org; xdi@lists.oasis-open.org
> Subject: [xdi] Agenda:Joint XRI & XDI TC Telecon 10AM PT Thursday
2007-09-
> 27
> 
> Following is the agenda for a joint unofficial telecon of the XRI and
XDI
> TCs at:
> 
> Date:  Thursday, 27 September 2007 USA
> Time:  10:00AM - 12:00PM Pacific Time
> 
> Event Description:
> Weekly unofficial joint call of the XRI and XDI Technical Committees.
> 
> TO ACCESS THE AUDIO CONFERENCE:
>     Dial In Number: 571-434-5750
>     Conference ID: 5474
> 
> 
> AGENDA
> 
> 1) REVISED REF PROCESSING PROPOSAL
> Based on the very active email thread, followed by in-person
discussions
> between XRI TC members and XRI resolver implementers at Digital ID
World,
> a
> page summarizing all proposed changes to ref processing has been
posted
> to:
> 
> 	http://wiki.oasis-open.org/xri/XriCd02/RefProcessing
> 
> Please review it before the call if you have time -- coming to closure
on
> this so it can be revised in ED06 is our highest priority.
> 
> 2) CLOSURE ON XML NAMESPACING FOR XRD ATTRIBUTES
> 
> The proposal is to NOT declare namespaces for XRD attributes (which is
> what
> the spec currently says normatively but does not show correctly in
> examples). We will confirm there is consensus on this.
> 
> 
> 3) SCHEDULE FOR XRI RESOLUTION 2.0 WD11 ED06 AND COMMITTEE DRAFT VOTE
> 
> We will review the remaining action items at...
> 
> 	http://wiki.oasis-open.org/xri/Xri2Cd02/ResWorkingDraft11
> 
> ...and assign tasks to complete ED06 ASAP so we can prepare for a
> Committee
> Draft vote.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 



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