A: cool sharing on the website of agency X http://...
B: agency X GOOD: sharing on http://... BAD: woeful markup
Unfortunately this was in a public forum, one which I happen to know
that X's publicity people are actively monitoring. The techies in
agency X have just been embarrassed in front of their publicity
people, and the negative remark is so general that the techies have no
idea what's perceived as being wrong with http://... and no way to
make their next conversation with their publicity people end happily.
It's fine to be honest about the way things are, but imagine these
alternative come-backs:
B: agency X GOOD: sharing on http://... BAD: needs microformats
http://microformats.org/
B: agency X GOOD: sharing on http://... BAD: needs validation
http://validator.w3.org/
B: agency X GOOD: sharing on http://... BAD: needs to be in XHTML
http://www.w3.org/TR/xhtml1/
B: agency X GOOD: sharing on http://... BAD: needs an RSS feed
http://en.wikipedia.org/wiki/RSS
B: agency X GOOD: sharing on http://... BAD: needs tables removed
http://www.w3.org/TR/WCAG10-HTML-TECHS/#tables-layout
B: agency X GOOD: sharing on http://... BAD: needs license
http://dublincore.org/documents/dcmi-terms/#terms-license
All of these provide (a) actual clarity about what might be wrong (and
lets not forget, it might be like that for a reason); (b) a URL in
case the maintainer of http://... has never heard of the cast-iron
rule they've broken.
Public non-constructive slagging off of agencies does no one any good.
cheers
stuart