As a fellow designer who spends a lot of designing these guidelines, I've thought about how to include these but it does hurt the idea of making it automated.
If this proposal is to remain in it's simplest form, it would require the default logo selected to be one that is as flexible as possible and would require the design to possibly build in the space required, background color, etc.
There may also be room for additional tags that would describe the usage i.e. rel="logo grayscale" or rel="grayscale knockout"
I'm not sure that this abuse would have much negative consequence. Am I missing something?
Let's say I copy the Google homepage and in the <head> there is a reference to http://google.com/logo.svg
How does that create any more problems than already exist?
I'm excited to see this come up again on Hacker News (I'm the guy proposing it). I would love for this to be an opportunity to improve my proposal. I originally put up the site over a year ago, and it has since been rejected by Microformats. I think there is room for improvement by offering variations of logos (grayscale, knockout, etc) and some way to referencing guidelines. I'd like to revisit this in hopes that it sees some larger adoption.
As a side note, for anyone interested in further thinking on this, I've discussed it on this podcast: http://onthegrid.co/post/40903339954
(discussion starts at 29:20)
If this proposal is to remain in it's simplest form, it would require the default logo selected to be one that is as flexible as possible and would require the design to possibly build in the space required, background color, etc.
There may also be room for additional tags that would describe the usage i.e. rel="logo grayscale" or rel="grayscale knockout"