title: Where to place the humans.txt file if I cannot put it on the site root?
body: <h3>Background</h3>
  
  <hr>
  
  <ul>
  <li>I'm building a web application for a client.</li>
  <li>This app will be accessible to the world and will be placed in a directory (e.g., <code>/my-app</code>) in web-root. A subdomain isn't an option as they don't want to cough up the dough for another SSL cert.</li>
  <li><code>/my-app</code> is the only directory that I'm allowed to touch (unreasonable IT guys).</li>
  <li>I'm using an icon set which requires attribution.</li>
  <li>I've contacted the original author of the icon set and have gotten permission to link back to his work in the <code>THANKS</code> section of a <a href="http://humanstxt.org/Standard.html"><code>humans.txt</code></a> file.</li>
  <li>I also feel like I should mention some other people's work. This information combined with the above will probably take up a good 20 lines, so a separate file like <code>humans.txt</code> seems like an ideal place to put this considering that I'll be serving minified markup, CSS, and script files.</li>
  </ul>
  
  <h3>Questions</h3>
  
  <hr>
  
  <ol>
  <li><p>Since I'm not allowed to place a <code>humans.txt</code> file in web-root, (and even if I was, it wouldn't really make much sense to put it there as it only applies to the <code>/my-app</code> portion of the site) is it acceptable to do the following:</p>
  
  <ul>
  <li>Create: <code>/my-app/humans.txt</code></li>
  <li>Place: <code>&lt;link rel="author" href="//example.com/my-app/humans.txt"&gt;</code> in my markup</li>
  </ul></li>
  <li><p>I'll be serving strict HTML 4.01 and the <code>author</code> value for the <code>rel</code> attribute doesn't seem to be a recognized link type in that specification. Do I need to do anything extra to define the <code>author</code> link type, or is the act of using it enough?</p></li>
  </ol>
  
  <p>I don't even know if there are any non-spider tools that actually use this file at the moment, but I'd like to minimize the chance of this not working in the future when something does come along.</p>