Thanks Nat for pointing out the inaccuracies. But I don't see how it changes the argument I am making.<br><br><div class="gmail_quote">On Fri, Nov 6, 2009 at 5:51 PM, Nat Sakimura <span dir="ltr"><<a href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Inline:<div class="im"><br>
<br>
Santosh Rajan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ok, let me get this straight. We are going to have<br>
<br>
1) XRD's with <Subject><br>
2) XRD's without <Subject><br>
3) XRD with <Host> instead of <Subject><br>
</blockquote></div>
That is inacculate. In fact, it will be something like <hm:Host> rather than <Host><br>
where hm is the XML ns for host-meta.<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
4) Someone might come along and decide lets have <Title> instead of <Subject><br>
</blockquote></div>
Yes, but it will be like <ab:Title> where ab is the XML name space.<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
5) Anyone can have anything else instead of <Subject><br>
</blockquote></div>
That's the nature of the extensibility of XML.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
Is this your idea of future compatibility?<br>
Why is it so difficult for people to see that this whole thing is leading to a mess?<br>
<br></div><div class="im">
On Fri, Nov 6, 2009 at 12:43 PM, SitG Admin <<a href="mailto:sysadmin@shadowsinthegarden.com" target="_blank">sysadmin@shadowsinthegarden.com</a> <mailto:<a href="mailto:sysadmin@shadowsinthegarden.com" target="_blank">sysadmin@shadowsinthegarden.com</a>>> wrote:<br>
<br>
I think I have a better understanding now. I will try to explain it:<br>
<br>
<br>
Are you suggesting that you guys know something which those<br>
guys didn't know?<br>
<br>
<br>
No. But . . . forward-compatibility.<br>
<br>
History has shown us that we (and others) will continue to have<br>
ideas that are not covered by existing specs, requiring us to<br>
either come up with new specs or modify existing specs. We don't<br>
need to specifically anticipate these ideas, we don't need to know<br>
all the details, to foresee that they (probably) *will* be<br>
pursued. If, at that time, the XRD spec does not support them,<br>
their development will be slowed down, and their implementors may<br>
go make a rival spec to accomplish/support what *they* are after,<br>
faster than XRD can be modified to allow for it. This splinters<br>
what would otherwise be a single XRD community into several<br>
similar groups, and divides the attention of those whose interest<br>
is rooted more in the compatible ideas than steadfast loyalty to<br>
particular specs.<br>
<br>
By putting greater flexibility into the XRD spec than any specific<br>
*need* has been shown for, compatibility with future ideas is made<br>
more likely. Today the Subject may be necessary for 99% of use<br>
cases; that percentage may change again in future, though.<br>
<br>
-Shade<br>
<br>
<br>
<br>
<br>
-- <br>
<a href="http://hi.im/santosh" target="_blank">http://hi.im/santosh</a><br>
<br>
<br></div>
------------------------------------------------------------------------<div class="im"><br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@lists.openid.net" target="_blank">general@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-general" target="_blank">http://lists.openid.net/mailman/listinfo/openid-general</a><br>
<br>
</div></blockquote>
<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="http://hi.im/santosh">http://hi.im/santosh</a><br><br><br>