Speaking both as a member of the PASS Board of Directors and as a concerned DBA, it's an interesting and tricky subject. I do believe it has value for our profession if it can be done right,and my definition of right is:

- It has to be strictly ethics, not anything tied to any "best practice". If a business wants to use RAID 0 or a consumer grade PC for a server or deploy shoddy code, in general that is their right and shouldn't challenge our ethics

- We have to realize that these are guidelines with no power to enforce other than our own conscious. Are you willing to resign a position if they would ask you to violate one of the ethics rules?

- It can actually be used to support us by pointing to an industry standard definition of ethical behavior, in many cases I think employers might go "hey, there is guidance out there"

- It needs to include some add-on coaching. Let's say you work in banking and are pretty sure there is a sql injection vulnerability and you notify the business - does that complete your obligation, or are you in a position to have be a whistle blower?

Which may or may not be the right definition. I guess I see it having a lot of value for inexperienced DBA's that see something bad happening, just helping them understand how bad and how much responsibility/liability would be a useful thing.