<html>
<body>
<blockquote type=cite class=cite cite=""><font size=3>But; they don't
answer the questions above. (Why should I bother with Yadis -- in
particular "why bother with it instead of OpenID/
SXIP/...". <br>
[ I think I know the answer, but I haven't seen it spelled out in any of
the written documents ].</font></blockquote><br>
If there is any prize money involved, I'll take a shot:<br><br>
<br>
Long answer:<br><br>
<br>
This Yadis specification provides:<br><br>
A general purpose identifier for persons and any other
entities, which can be used in a variety of services. <br><br>
A syntax for a resource description document
identifying services available using that identifier and an
interpretation of the elements of that document.<br><br>
A protocol for obtaining that resource description
document, given that identifier.<br><br>
Together these enable coexistence and interoperation of a rich variety of
services using a single identifier. The identifier uses a standard syntax
and a well-established namespace; it requires no additional namespace
administration infrastructure. <br><br>
<br>
When a User offers a Yadis ID to a Relying Party, that Relying Party will
want to discover which services are available using that Yadis ID.
<br><br>
Examples: <br>
Is it an OpenID URL, an XRI, a LID or a Sxip ID? <br>
What authentication methods are available?<br>
What other services?<br><br>
<br>
Short answer:<br><br>
Bother with Yadis so you will have a choice among OpenID/
XRI/SXIP/LID/TheNextBestThing.<br><br>
<br>
Cordially, Joaquin<br><br>
</body>
</html>