Some feature requests are awesome, some good, some are strange and some are just weird. I'm not yet sure where to put this request for HTML5 that proposes adding a <nsfw> ("not safe for work") tag into the language specification. While it definitely has more semantic meaning than adding a CSS-class "nsfw" into each relevant node, it in my opinion doesn't warrant its own tag. If you think it through, you would also have to create tags like <spoiler>, <shoppingcart> and <answer>.
In a comment on Jeffrey Zeldman's blog Darcy Murphy suggested the use of rel="nsfw" which is probably a really good solution for links, but probably doesn't help with inline-content. There using a class is perhaps the best way also when it comes to semantics. In either case, native support within browsers as perhaps part of some profile systeme (plus some parental control) is required to make the whole idea useful.
[via www.zeldman.com]
I'm not sure. The term NSFW, though well known by many netizens, does not imply anything directly related to parental control. Even though you can assume things marked as NSFW may also need to be screened by parental control, it is not necessary. NSFW is not reserved for porn only, but may also be related to other content that may not be suitable for a work-screen, but would be fine in a home setting, even for young adults or kids. Granted, those situations are scarce and usually parental control and NSFW go hand in hand, but not always.
A better term to use would be "PC" or "parentalcontrol" then, because then you really imply that it needs to pass parental control demands.
June 10, 2009, 2:07 p.m.
I dislike the idea of marking something like that with special tags, especially when it doesn't offer any benefits over using classes.
June 10, 2009, 2:11 p.m.