Can / Should every site publish a web architecture manifesto?

[olivierthereaux]

Several BBC teams have published their "manifesto" on topics such as:

• URI creation,
• URI persistence,
• linking,
• availability of representations
• APIs or format negotiation

Examples: http://www.tomski.com/archive/new_archive/000063.html and http://derivadow.com/2011/07/30/our-manifesto/

Some of the principles they mention are globally-accepted (if not always followed) good practices, others are more of a choice ("our website is the API" vs "here is the documentation of our web API" vs "here's the machine-readable API description").

Is there a point in having more teams publish those? Would a survey help understand current and best practices? Should there be a survey of web architecture understanding and attitudes?