Wikipedia:Articles for deletion/4th Generation Data Leak Prevention
From Wikipedia, the free encyclopedia
- The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
The result was delete. -- Cirt (talk) 07:44, 12 February 2011 (UTC)[reply]
4th Generation Data Leak Prevention[edit]
- 4th Generation Data Leak Prevention (edit | talk | history | protect | delete | links | watch | logs | views) – (View log)
- (Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)
Seems to have been created by an employee of Next Tier Networks to advertise their "solution". My first impulse is simply to delete it as obvious spam, but I don't want to be overhasty if there's anything salvageable. Orange Mike | Talk 05:08, 5 February 2011 (UTC)[reply]
- Note: This debate has been included in the list of Computing-related deletion discussions. -- • Gene93k (talk) 19:38, 5 February 2011 (UTC)[reply]
- Delete. I can't find any evidence that anyone else assesses data leak prevention technology in terms of these four "generations". Zetawoof (ζ) 23:51, 5 February 2011 (UTC)[reply]
- Delete. DLP is a worthy subject but splitting it into four generations this way is, I think, strictly a method of selling a particular product; and the text goes into details of the specifications about one product rather than covering the generalities of this "fourth generation". I'd be happy with an article that considers modern DLP techniques under a more neutral title, but this isn't it. bobrayner (talk) 03:34, 11 February 2011 (UTC)[reply]
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.