<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 22 Jan '06, at 12:25 PM, Johannes Ernst wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Verdana" size="3" style="font: 11.0px Verdana">1) The response contains an X-YADIS-Location header in the HTTP header, and an X-YADIS-Location in the http-equiv attribute in the HTML, and they point to different YADIS files.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>This issue comes up a lot in conjunction with document encodings, especially XML. I believe you are correct that the specs say that HTTP headers have higher priority; but I also believe that, for reasons explained by your Argument B, in the real world the file content is given precedence. (My ISP has no clue what encoding I use for the .html files I upload to it, so why should its word count more than mine?)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Sam Ruby discusses this in his hilarious-because-it's-true presentation " 'Just' Use XML", starting here:</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN><A href="http://intertwingly.net/slides/2005/xmlconf/70.html">http://intertwingly.net/slides/2005/xmlconf/70.html</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This leads to his "Ruby's Postulate":</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>"The accuracy of metadata is inversely proportional to the square</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN> of the distance between the data and the metadata."</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>...But to play devil's advocate against myself, from the POV of my earlier post about security, it is certainly somewhat harder to hack the HTTP headers than the page content.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>--Jens</DIV></BODY></HTML>