RE: [xri] XRI Resolution working draft 9 sec 3.2.5

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

First, a clarification: Working Draft 9 of the Resolution spec has not been
posted yet. Victor was commenting on a proposed draft he is contributing to
is still in the editing stage. However both issues he raises (the one below
and in his last message about versioning of XRIDs) apply to the current
Committee Draft 01 spec (assuming the addition of the priority attribute we
have ageed to).

Second, I understand Victor's point - from the resolver's standpoint, it's
more work to have to parse the contents of the element than just be able to
select a URI using of two attributes: scheme and priority.

Parsing this out per our agreed to process -- which means next step is
posting to the wiki for analysis/discussion of the requirements. Following
is a quick first pass. Anyone who disagrees/wants to modify, please reply,
otherwise I'll post it to the wiki after the upcoming TC calls.

=Drummond 

RESOLUTION ISSUE/CHANGE PROPOSAL
Proposed attribute for URI element.

MOTIVATION
Processing efficiency and simplified development.

REQUIREMENTS
 * Minimize the processing burden on XRI clients. 
 * Make it easier to develop XRI clients.

PROPOSAL
Add a xrid:scheme attribute on URI elements within an XRID.

QUESTIONS
* Should it be required?
* Should it be optional if the scheme is HTTP? In other words, should we
specify if this attribute is missing, the scheme MUST be HTTP.

=Drummond 

-----Original Message-----
From: Victor Grey [mailto:victor@idcommons.org] 
Sent: Thursday, September 15, 2005 5:51 PM
To: xri@lists.oasis-open.org
Subject: [xri] XRI Resolution working draft 9 sec 3.2.5

WD9 in section 3.2.5 (Construction of the Next Service Endpoint URI) 
states that:
"For the selected Service element, select the highest priority URI 
element that contains an HTTP or HTTPS URI (depending on the desired 
transport protocol.)"

This would be an expensive query, because you would first have to go 
through -all- of the <URI> elements in the relevant Service section, 
determine which ones match the desired scheme (http or https) by 
examining the text node in each element, and then go back through the 
URI elements that match the desired scheme to determine which has the 
highest priority.

I'd propose therefore that for processing efficiency the <URI> element 
also have a xrid:scheme attribute, thus making it possible to select 
the URIs matching the desired scheme before comparing their priority 
attributes.

=vg


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php