xrate - Revision history

Tantek: warning historical brainstorming

2022-11-18T06:21:10Z

warning historical brainstorming

← Older revision		Revision as of 06:21, 18 November 2022
Line 1:		Line 1:
			{{warning\|This page is a single-author proposal from 2012 that did not see any uptake. It is kept only for historical brainstorming.}}

	==Authors==		==Authors==
	[http://kurapov.name/eng/tech/explicit_content_format/ Artjom Kurapov]		[http://kurapov.name/eng/tech/explicit_content_format/ Artjom Kurapov]

Tot ra: /* Draft */

2012-04-19T09:27:29Z

Draft

← Older revision		Revision as of 09:27, 19 April 2012
Line 11:		Line 11:

	== Draft ==		== Draft ==
	Author has to mark any html element with attribute, based on his subjective rating of content's danger. HTML5 gives attribute data- in free use, so namespace xrate (sort for explicit rating) with integer values (0-100) which represent danger to the viewer (the higher - the bigger), which will also ease filtering. Suggested format is not centralized and thus heavily depends on maintainer and owner of the content. A ~~social rating of the content (~~with ~~either~~ average or median result) is advised.		Author has to mark any html element with attribute, based on his subjective rating of content's danger. HTML5 gives attribute data- in free use, so namespace xrate (sort for explicit rating) with integer values (0-100) which represent danger to the viewer (the higher - the bigger), which will also ease filtering. Suggested format is not centralized and thus heavily depends on maintainer and owner of the content. A collective voting system with average or median result as rating value is advised to be used.

	=== Rating tags ===		=== Rating tags ===

Tot ra: /* Draft */

2012-04-19T09:26:20Z

Draft

← Older revision		Revision as of 09:26, 19 April 2012
Line 11:		Line 11:

	== Draft ==		== Draft ==
	Author has to mark any html element with attribute, based on his subjective rating of content's danger. HTML5 gives attribute data- in free use, so namespace xrate (sort for explicit rating) with integer values (0-100) which represent danger to the viewer (the higher - the bigger), which will also ease filtering.		Author has to mark any html element with attribute, based on his subjective rating of content's danger. HTML5 gives attribute data- in free use, so namespace xrate (sort for explicit rating) with integer values (0-100) which represent danger to the viewer (the higher - the bigger), which will also ease filtering. Suggested format is not centralized and thus heavily depends on maintainer and owner of the content. A social rating of the content (with either average or median result) is advised.

	=== Rating tags ===		=== Rating tags ===

Tot ra: /* Existing standards */

2012-04-19T09:00:53Z

Existing standards

← Older revision		Revision as of 09:00, 19 April 2012
Line 6:		Line 6:

	==Existing standards==		==Existing standards==
	Current formats of marking content (SafeSurf, RTA, ICRA, RSAC, PICS and now W3C POWDER) either mark entire page as pornographic using meta tag or headers, or are too complex for webmasters to handle. Ratings like ESRB, MPAA, PEGI are product specific and centralized, which though does provide confidence, cannot scale with internet media		Current formats of marking content (SafeSurf, RTA, ICRA, RSAC, PICS and now W3C POWDER) either mark entire page as pornographic using meta tag or headers, or are too complex for webmasters to handle.

			Ratings like ESRB, MPAA, PEGI are product specific and centralized, which though does provide confidence, cannot scale with internet media. They are also targeted for specific country and its legislation.

	== Draft ==		== Draft ==

Tot ra at 08:30, 19 April 2012

2012-04-19T08:30:19Z

← Older revision		Revision as of 08:30, 19 April 2012
Line 1:		Line 1:
			==Authors==
			[http://kurapov.name/eng/tech/explicit_content_format/ Artjom Kurapov]

	== Problem ==		== Problem ==
	Explicit content is a media that affects human psyche and disturbs it. Formatting violent, pornographic and other content should allow control with browser plugins, search crawlers, rss feed readers and other automated tools		Explicit content is a media that affects human psyche and disturbs it. Formatting violent, pornographic and other content should allow control with browser plugins, search crawlers, rss feed readers and other automated tools

Tot ra at 08:27, 19 April 2012

2012-04-19T08:27:50Z

← Older revision		Revision as of 08:27, 19 April 2012
Line 5:		Line 5:
	Current formats of marking content (SafeSurf, RTA, ICRA, RSAC, PICS and now W3C POWDER) either mark entire page as pornographic using meta tag or headers, or are too complex for webmasters to handle. Ratings like ESRB, MPAA, PEGI are product specific and centralized, which though does provide confidence, cannot scale with internet media		Current formats of marking content (SafeSurf, RTA, ICRA, RSAC, PICS and now W3C POWDER) either mark entire page as pornographic using meta tag or headers, or are too complex for webmasters to handle. Ratings like ESRB, MPAA, PEGI are product specific and centralized, which though does provide confidence, cannot scale with internet media

	== ~~suggestion~~ ==		== Draft ==
	Author has to mark any html element with attribute, based on his subjective rating of content's danger. HTML5 gives attribute data- in free use, so namespace xrate (sort for explicit rating) with integer values (0-100) which represent danger to the viewer (the higher - the bigger), which will also ease filtering.		Author has to mark any html element with attribute, based on his subjective rating of content's danger. HTML5 gives attribute data- in free use, so namespace xrate (sort for explicit rating) with integer values (0-100) which represent danger to the viewer (the higher - the bigger), which will also ease filtering.

	data-xrate-~~lang Obscene language~~		=== Rating tags ===
			data-xrate-violence Violence and its results - weapons, wounds, dead bodies, blood

	data-xrate-sex Romantic, erotic, pornographic		data-xrate-sex Romantic, erotic, pornographic
Line 15:		Line 16:

	data-xrate-disgust Might cause disgust (shit, larvae, decomposition)		data-xrate-disgust Might cause disgust (shit, larvae, decomposition)

	~~data-xrate-violence Violence and its results - weapons, wounds, dead bodies, blood~~

	data-xrate-asocial Smoking, alcohol, drugs, gambling, prostitution		data-xrate-asocial Smoking, alcohol, drugs, gambling, prostitution

	data-xrate-~~blink Blinking animation that might cause eplilepsy~~		data-xrate-lang Obscene language

	data-xrate-spoiler Story is retold		data-xrate-spoiler Story is retold

			data-xrate-blink Blinking animation that might cause eplilepsy

	data-xrate-camera If application (flash/applet?) gains access to videocamera		data-xrate-camera If application (flash/applet?) gains access to videocamera

	data-xrate-malware If resource can cause infection (viruses, trojans etc.) on viewer's machine		data-xrate-malware If resource can cause infection (viruses, trojans etc.) on viewer's machine

			===Examples===
			<pre><nowiki>
			<a href="http://meatvideo.com/" data-xrate-violence="100">omg</a>

			<img src="http://www.tema.ru/jjj/tits/renuar.jpg" data-xrate-nude="60" data-xrate-sex="0" />
			</nowiki></pre>

Tot ra: /* existing standards */

2012-04-19T08:18:13Z

existing standards

← Older revision		Revision as of 08:18, 19 April 2012
Line 2:		Line 2:
	Explicit content is a media that affects human psyche and disturbs it. Formatting violent, pornographic and other content should allow control with browser plugins, search crawlers, rss feed readers and other automated tools		Explicit content is a media that affects human psyche and disturbs it. Formatting violent, pornographic and other content should allow control with browser plugins, search crawlers, rss feed readers and other automated tools

	==~~existing~~ standards==		==Existing standards==
	Current formats of marking content (SafeSurf, RTA, ICRA, RSAC, PICS and now W3C POWDER) either mark entire page as ~~being say~~ pornographic using meta tag or headers, or are too complex for webmasters to handle.		Current formats of marking content (SafeSurf, RTA, ICRA, RSAC, PICS and now W3C POWDER) either mark entire page as pornographic using meta tag or headers, or are too complex for webmasters to handle. Ratings like ESRB, MPAA, PEGI are product specific and centralized, which though does provide confidence, cannot scale with internet media

	== suggestion ==		== suggestion ==

Tot ra: New page: == Problem == Explicit content is a media that affects human psyche and disturbs it. Formatting violent, pornographic and other content should allow control with browser plugins, search cr...

2012-04-19T08:13:47Z

New page: == Problem == Explicit content is a media that affects human psyche and disturbs it. Formatting violent, pornographic and other content should allow control with browser plugins, search cr...

New page

== Problem ==
Explicit content is a media that affects human psyche and disturbs it. Formatting violent, pornographic and other content should allow control with browser plugins, search crawlers, rss feed readers and other automated tools

==existing standards==
Current formats of marking content (SafeSurf, RTA, ICRA, RSAC, PICS and now W3C POWDER) either mark entire page as being say pornographic using meta tag or headers, or are too complex for webmasters to handle.

== suggestion ==
Author has to mark any html element with attribute, based on his subjective rating of content's danger. HTML5 gives attribute data- in free use, so namespace xrate (sort for explicit rating) with integer values (0-100) which represent danger to the viewer (the higher - the bigger), which will also ease filtering.

data-xrate-lang Obscene language

data-xrate-sex Romantic, erotic, pornographic

data-xrate-nude Level of nudity

data-xrate-disgust Might cause disgust (shit, larvae, decomposition)

data-xrate-violence Violence and its results - weapons, wounds, dead bodies, blood

data-xrate-asocial Smoking, alcohol, drugs, gambling, prostitution

data-xrate-blink Blinking animation that might cause eplilepsy

data-xrate-spoiler Story is retold

data-xrate-camera If application (flash/applet?) gains access to videocamera

data-xrate-malware If resource can cause infection (viruses, trojans etc.) on viewer's machine