Difference between revisions of "WebSchemas/Audience"

From W3C Wiki
Jump to: navigation, search
m
(tidying)
Line 229: Line 229:
 
There are some works on adult content markup:
 
There are some works on adult content markup:
  
[http://www.rtalabel.org rtalabel.org] - alive, but only restrictive model
+
* [http://www.rtalabel.org rtalabel.org] - alive, but only restrictive model
 
+
* [http://www.icra.org/ ICRA] - closed, see [http://philarcher.org/icra/ICRAfail.pdf icrafail.pdf]
[http://www.icra.org/ ICRA] - dead, replaced by PICS
+
* [http://www.w3.org/PICS/ PICS] - replaced by RDF in general, POWDER in particular
 
+
* [http://www.w3.org/2007/powder/ POWDER] - recent W3C recommendation, last update in 2009. Also the additional-xml-file format seems to be unconvenient for our purposes
[http://www.w3.org/PICS/ PICS] - dead, replaced by POWDER
+
 
+
[http://www.w3.org/2007/powder/ POWDER] - seems to be also dead, last update in 2009. Also the additional-xml-file format seems to be unconvenient for our purposes
+
 
+
  
 
Also some current schema.org proposals with similar ideas:
 
Also some current schema.org proposals with similar ideas:
  
[http://www.w3.org/wiki/WebSchemas/MedicalHealthProposal Medical/Health]
+
* [http://www.w3.org/wiki/WebSchemas/MedicalHealthProposal Medical/Health]
 
+
* [http://www.w3.org/wiki/WebSchemas/LearningResources LRMI]
[http://www.w3.org/wiki/WebSchemas/LearningResources LRMI]
+
* [http://www.w3.org/wiki/WebSchemas/TechArticleSchema TechArticle]
 
+
[http://www.w3.org/wiki/WebSchemas/TechArticleSchema TechArticle]
+

Revision as of 14:07, 25 July 2012


This is a WebSchemas proposal Audience proposal for schema.org. See Proposals listing for more. Status: Proposal



Overview

This page describes schema.org proposal (second version, first one can be found here), containing necessary types and properties to describe Internet content audience.

Vocabulary changes summary

Add type Thing->Intangible->Audience

Add property audience to type CreativeWork

Thing->Intangible->Audience->PeopleAudience

Property Type Description
minAge Number Minimal age recommended for viewing content
maxAge Number Maximal age recommended for viewing content
gender Text People target gender.







Thing->Intangible->Audience->PeopleAudience->ParentAudience

Property Type Description
childMinAge Number Minimal age of the child. A negative value means child isn't born yet.
childMaxAge Number Maximal age of the child.





Adding recommendations

First, add an abstract type Thing->Intangible->Audience

Add property audience to type CreativeWork

Every subclass of Audience type must contain some recommendations. A recommendation can be or an enumeration, or a complex type object. I expect necessary types can be added as soon as we need them.

Age recommendations

As you might think, the first goal of recommendations is to protect children from adult content (porn, violence, etc.). But I doubt all the porn sites will gladly markup their content. But they aren't our primary goal, because we don't want negative constraints, we do want positive recommendations. I think we should stimulate publishers to label their target audience explicitly.

Hence, there is an age recommendation:

Thing->Intangible->Audience->PeopleAudience

Property Type Description
minAge Number Minimal age recommended for viewing content
maxAge Number Maximal age recommended for viewing content





This class can be used in many ways:

1) Means: this is a game for children

  1. <!--Game for children-->
  2. <div itemscope itemtype="http://schema.org/CreativeWork">
  3.     <span itemprop="audience" itemscope itemtype="http://schema.org/AgeAudience">
  4.         <meta itemprop="minAge" content="7"/>
  5.         <meta itemprop="maxAge" content="13"/>
  6.     </span>
  7.     <object>... some flash game ...</object>
  8. </div>

2) Means: this is an adult movie

  1. <!--Porn movie-->
  2. <div itemscope itemtype="http://schema.org/VideoObject">
  3.     <span itemprop="audience" itemscope itemtype="http://schema.org/AgeAudience">
  4.         <!--Since it has no maxAge, it has no upper age limit-->
  5.         <meta itemprop="minAge" content="18"/>
  6.         <!--Being optimistic: <meta itemprop="maxAge" content="115"/>-->
  7.     </span>
  8.     <object>... some video object ...</object>
  9. </div>

Gender recommendations

Second useful targeting property is gender. Currently gender is expressed as Text. I don't know if it was already discussed, but maybe we need also gender enum. Here is the recommendation type:

Thing->Intangible->Audience->PeopleAudience

Property Type Description
gender Gender? Recommended gender





An example:

  1. <!--E-shop for woman-->
  2. <html itemscope itemtype="http://schema.org/WebPage">
  3.     <span itemprop="audience" itemscope itemtype="http://schema.org/GenderAudience">
  4.         <meta itemprop="gender" content="female"/>
  5.     </span>
  6.     <body> ... Some lingerie here ... </body>
  7. </html>

Another example:

  1. <div itemscope itemtype="http://schema.org/Article">
  2.     <span itemprop="audience" itemscope itemtype="http://schema.org/GenderAudience">
  3.         <meta itemprop="gender" content="male"/>
  4.     </span>
  5.     <h2 itemprop="name">Bodybuilding</h2>
  6.     <div itemprop="text">
  7.         Use dumbbells, Luke!
  8.     </div>
  9. </div>

Recommendations for parents

Third recommendation type I want to propose: content for parents. There is a lot of sites for parents in the Internet, and they are all different depending on child age. So, there can be some recommendation based on child age: Thing->Intangible->Audience->PeopleAudience->ParentAudience

Property Type Description
childMinAge Number Minimal age of the child. A negative value means child isn't born yet.
childMaxAge Number Maximal age of the child.





An example can look so:

  1. <div itemscope itemtype="http://schema.org/Article">
  2.     <span itemprop="audience" itemscope itemtype="http://schema.org/ParentAudience">
  3.         <meta itemprop="childMinAge" content="2"/>
  4.         <meta itemprop="childMaxAge" content="5"/>
  5.     </span>
  6.     <h2 itemprop="name">Teaching your child reading</h2>
  7.     <div itemprop="text">
  8.         Bored to read books for your children?
  9.     </div>
  10. </div>

Another example:

  1. <div itemscope itemtype="http://schema.org/Article">
  2.     <span itemprop="audience" itemscope itemtype="http://schema.org/ParentAudience">
  3.         <meta itemprop="childMinAge" content="-1"/>
  4.         <meta itemprop="childMaxAge" content="0"/>
  5.     </span>
  6.     <h2 itemprop="name">Childbirth for dummies</h2>
  7.     <div itemprop="text">
  8.         Five steps to bear a child: ...
  9.     </div>
  10. </div>

Medical/Health, LRMI and TechArticle alignment

Medical/Health, TechArticle and LRMI proposals contain similar issues, these proposals can be merged together.

These proposals need some minor changes to share common audience schema:


For Medical/Health (approved by Aaron Brown):

a) move Thing->Intangible->Enumeration->Audience to Thing->Intangible->Audience

b) move MedicalAudience to have base types Audience and MedicalEnumeration


For LRMI:

a) create Thing->Intangible->Audience->PeopleAudience->EducationalAudience type with property 'educationalRole' (expected type: schema.org/Text)

b) remove typicalAgeRange from proposal and use PeopleAudience 'maxAge' and 'minAge' properties instead

c) remove 'intendedEndUserRole' from LRMI proposal and use EducationalAudience 'educationalRole' instead


For TechArticle:

a) create Thing->Intangible->Audience->PeopleAudience->TechnicalAudience type with property 'technicalAudience' (expected type: schema.org/Text)

b) remove 'technicalAudience' property from TechArticle type and use common 'audience' property instead

How to Join the Discussion

No way yet

Related

There are some works on adult content markup:

  • rtalabel.org - alive, but only restrictive model
  • ICRA - closed, see icrafail.pdf
  • PICS - replaced by RDF in general, POWDER in particular
  • POWDER - recent W3C recommendation, last update in 2009. Also the additional-xml-file format seems to be unconvenient for our purposes

Also some current schema.org proposals with similar ideas: