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: [xri] XRI discovery -vs- resolution



I'm torn. I like discovery, it sounds cleaner and is easier to remember.
OTH, isn't it different? You resolve a single address to a resource,
your discover resources by discovering their addresses (each of which
you can then resolve).

Discovery, as I'm using it above, seems missing from XRI specs. In my
own backyard I am using a simple home-grown XRI discovery using
variables and or convention:
(1) A discovery result in XRDS form is one which only contains nested
XRDS elements, each of which contains resolution of a discovered XRI.
Alternative form is URI-list in which case each URI in list is an HXRI
representing one of the discovered resources 
(2) XRIs of the XDI form xri:authsegmenthere/sometype.A.here each return
an a discovery result of all locally known XRIs of the form
xri:authsegmenthere/sometype.A.here/some.instance.id.here, uses xdi
discovery service
(3) XRIs of the form xri:xri.containing.XPL (for example
xri://@x*($(member/+Person))*blog) return a discovery result of all
locally known XRIs that match the expression (currently I'm working on
conditions, but only vars working), for example xri://@x*Alice*blog,
xri://@x*Bob*blog, xri://@x*Sue*blog.
  Note that for an XRDS discovery result each xrds representing a result
would have an attribute (http://x.com/xpl/0.7/binding):member with the
appropriate attribute value (Alice, Bob, or Sue).
Once I have a reference impl working I plan on pulling my home-grown
discovery mechanism into a proposal doc and submitting to XRI TC. The
domain name and @-authority above for XPL are not fixed yet, hence x,
but they will be when I submit my doc to the TC.  FYI, I am cognizant of
the security and privacy implications in this kind of discovery
mechanism, and have policy-enabled access control (eventually will move
to XDI link contracts).

Bill

-- 
William Barnhill                    Phone: (315) 491-6765
Associate                           Email: barnhill_william@bah.com
Booz | Allen | Hamilton             i-name: =Bill.Barnhill
"Delivering results that endure" 

-----Original Message-----
From: Victor Grey [mailto:victor@idcommons.org] 
Sent: Tuesday, December 19, 2006 12:00 AM
To: xri@lists.oasis-open.org
Subject: Re: [xri] XRI discovery -vs- resolution

+1
=vg


Chasen, Les wrote:
> I was wondering what everyone thinks about the idea of instead of 
> using the term XRI resolution we start calling it XRI discovery?


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