Re: [cti] Proposed normative text available for Report object refactoring - (Goal: Reach official consensus by Monday)

["Jordan, Bret" <bret.jordan@bluecoat.com>]

Back to Bret’s original comment, I can see both approaches for the Report object working. The relationship-based approach is more powerful and allows for a lot of flexibility for a report to evolve over time, have ad-hoc producers relating things, and relate objects with some confidence assertion.

IMO, if someone wants to add stuff or take stuff away from my report, they should be required to generate their OWN version of the report. They should not be allowed to add or remove content from MY report.  That report is mine, and my view.  You can disagree with my view, but it is still my REPORT.  

Thanks,

Bret

Bret Jordan CISSP

Director of Security Architecture and Standards | Office of the CTO

Blue Coat Systems

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail