Loading Profile...
Please reconsider the use of XRDS/XRI
"We are not satisfied that XRIs provide functionality not readily available from http: URIs." -- Tim Berners-Lee, http://lists.w3.org/Archives/Public/w... .
Please do not try to establish a standard around an unproven competing technology to the shared foundation of HTTP URIs that the open Web builds upon.
Please do not try to establish a standard around an unproven competing technology to the shared foundation of HTTP URIs that the open Web builds upon.
I’m disappointed
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company thinks this is not a problem.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?While TBL makes a fine point about the use of XRI identifiers as compared to http URIs, that is separate from our use of XRDS as a service discovery mechanism for EAUT. You'll note that XRDS is also used for service discovery in both OpenID and OAuth. XRIs and XRI resolution (XRDS) are defined defined in two separate specs so neither is tied to the other. In fact, there is discussion of making XRI resolution an extension of XRDS-Simple (which we use) as opposed to the other way around.
1 person says
this solves the problem
-
Inappropriate?Can I ask: what specific recommendations do you have for alternative methods for discovery? Have you implemented any specifically? I'm open to becoming more educated on the subject.
I’m curious
1 person says
this solves the problem
-
Inappropriate?Hi Will, Chris,
Thanks for the link to the discussion in the XRDS-Simple group (August 12th - super fresh!). My concern was that XRDS-Simple, even as a simplified protocol, was still built around XRI; but I see that Eran Hammer-Lahav also shares that concern. His proposal to rebuild it around HTTP URIs is totally in line with my feelings on the matter, and, in fact, is startlingly similar to what I was going to reply to Chris with, right down to the mention of the HTTP LINK draft RFC.
Thanks, guys.
I’m pleased the underlying technology is moving in the right direction!
1 Comment Add a comment
This solves the problem
-
Eran's a smart guy, and I support his intuition to move closer to being HTTP-native. I don't like the XRI origins either, but I need to take the time to look more closely at his thinking so far.
