WebSchemas/Audience old

From W3C Wiki
Jump to: navigation, search


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



Overview

This page describes schema.org proposal, 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->AgeAudience

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





Thing->Intangible->Audience->GenderAudience

Property Type Description
gender Gender? Recommended gender




Thing->Intangible->Audience->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.





Add type Thing->Intangible->Audience->Negation with condition property

Add type Thing->Intangible->Audience->Conjunction (alternatively: And) with condition property

Add type Thing->Intangible->Audience->Disjunction (alternatively: Or) with condition property

Add type Thing->Intangible->Audience->ExclusiveDisjuction (alternatively: Xor) with properties condition1 and condition2

Adding recommendations

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

Add property audience to type CreativeWork

Note that Medical/Health Proposal contains similar issues, these proposals can be merged together.

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->AgeAudience

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->GenderAudience

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->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>

Audience Boolean logic

Sometimes an audience can be too complex to be described in schema.org type. But it can be expressed by using some Boolean logic constructs over existing types. I suggest to use Decorator pattern over Audience type. These at least three types:

1) Thing->Intangible->Audience->Negation

2) Thing->Intangible->Audience->Conjunction (alternatively: And or LogicalAnd)

3) Thing->Intangible->Audience->Disjunction (alternatively: Or or LogicalOr)

will make the logic complete (i.e. every boolean function can be expressed). Another type:

4) Thing->Intangible->Audience->ExclusiveDisjuction (alternatively: Xor or LogicalXor)

isn't necessary, but maybe someone will find it useful.

Each type must have condition property, which contains other Audience objects.

Complex examples:

  1. <!--Game for girls (i.e. children and females)-->
  2. <div itemscope itemtype="http://schema.org/CreativeWork">
  3.     <span itemprop="audience" itemscope itemtype="http://schema.org/Conjunction">
  4.         <span itemprop="condition" itemscope itemtype="http://schema.org/AgeAudience">
  5.             <meta itemprop="minAge" content="7"/>
  6.             <meta itemprop="maxAge" content="13"/>
  7.         </span>
  8.         <span itemprop="condition" itemscope itemtype="http://schema.org/GenderAudience">
  9.             <meta itemprop="gender" content="Female"/>
  10.         </span>
  11.     </span>
  12.     <object>... Some game with pink unicorns ...</object>
  13. </div>

  1. <!--Book for teenagers and their parents-->
  2. <div itemscope itemtype="http://schema.org/Book">
  3.     <span itemprop="audience" itemscope itemtype="http://schema.org/Disjunction">
  4.         <span itemprop="condition" itemscope itemtype="http://schema.org/AgeAudience">
  5.             <meta itemprop="minAge" content="12"/>
  6.             <meta itemprop="maxAge" content="16"/>
  7.         </span>
  8.         <span itemprop="condition" itemscope itemtype="http://schema.org/ParentAudience">
  9.             <meta itemprop="childMinAge" content="12"/>
  10.             <meta itemprop="childMaxAge" content="16"/>
  11.         </span>
  12.     </span>
  13.     <h2 itemprop="name">Children and parents</h2>
  14.     <span itemprop="headline">Three ways to understand each other</span>
  15. </div>

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 - dead, replaced by PICS

PICS - dead, replaced by 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:

Medical/Health

LRMI