[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XRD delegated identifer element (was part of: questions about LRDD / OpenID)
I'm latching onto the very last question Will put in his response to Markus' XRD/LRDD questions this morning: > To add one additional question... for the delegation use case, how is > it expected that one would specify the OpenID delegate URL in XRD? I > can't think of any existing XRD element that would be suitable for > this, so I'm assuming we are expecting OpenID Discovery to define a > new Link sub-element, like they already do in XRDS? Of course, if > there is no delegate specified, you would just use the XRD Subject. The "existing XRD element that would be suitable for this" is supposed to be the LocalID element, listed near the bottom of http://wiki.oasis-open.org/xri/XrdOne/XrdSchema. That was already the element designed to replace the openid:delegate element for identifier delegation in OpenID 2.0 discovery. So, my first question is to confirm with Eran and everyone that this is still the case, i.e., the <XRD:Link:LocalID> element is the element intended to be used for identifier delegation by OpenID (or any other protocol that needs local identifier delegation). My second question is whether, if this is the case, we should (as we are doing with all the other XRD 1.0 elements) revisit the semantics of the element name itself and decide if there is a better alternative. My third question is how this factors into trust verification, since you are effectively asserting a synonym here. Thoughts? =Drummond
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]