Aim

To make trusted metadata a ubiquitous part of the Web

Objectives

• Identify resources that meet specific criteria, such as:
  • Quality
  • Accuracy
  • Educational value
  • Trustworthiness
  • Will work on your mobile device (probably)
  • Is licensed for public access
  • Approriateness for children

And many, many more...

Objectives

• Identify resources that meet specific criteria, such as:
  • Quality
  • Accuracy
  • Educational value
  • Trustworthiness
  • Will work on your mobile device (probably)
  • Is licensed for public access
  • Approriateness for children
• Identify who is making the claim

Objectives

• Identify resources that meet specific criteria, such as:
  • Quality
  • Accuracy
  • Educational value
  • Trustworthiness
  • Will work on your mobile device (probably)
  • Is licensed for public access
  • Approriateness for children
• Identify who is making the claim
• Support automated authentication of the claims

Objectives

• Identify resources that meet specific criteria, such as:
  • Quality
  • Accuracy
  • Educational value
  • Trustworthiness
  • Will work on your mobile device (probably)
  • Is licensed for public access
  • Approriateness for children
• Identify who is making the claim
• Support automated authentication of the claims
• Hook up with shared bookmarks, user-generated ratings, reviews etc.

Basic Requirements for a Description Resource

Basic Requirements for a Description Resource

• Attribution
  • Who is offering the description

Basic Requirements for a Description Resource

• Attribution
  • Who is offering the description
• Scope
  • What resources are being described

Basic Requirements for a Description Resource

• Attribution
  • Who is offering the description
• Scope
  • What resources are being described
• The description itself

Basic Requirements for a Description Resource

• Attribution
  • Who is offering the description
• Scope
  • What resources are being described
• The description itself

The DR itself is a Resource and has a URI of its own.

Basic Requirements for a Description Resource

• Attribution
  • Who is offering the description
• Scope
  • What resources are being described
• The description itself

The DR itself is a Resource and has a URI of its own.

It can therefore be the subject of a certificate, a user-generated comment, bookmark or whatever.

History...

• W3C PICS 1995 - 1997
• ICRA Labelling Working Group (June 2004)
• QUATRO Project (October 2004 - 2006)
• ICRA switched to RDF-CL labels (July 2005)
• W3C Content Label Incubator Group (February 2006)
• W3C POWDER WG chartered (February 2007)

Description Resource Strawman

<wdr:WDR>
  <foaf:maker rdf:resource="http://authority.org/foaf.rdf#me" />
  <dcterms:issued>2006-09-01</dcterms:issued>
  <wdr:validUntil>2007-09-01</wdr:validUntil>
  <wdr:hasScope>
    <wdr:Scope>
      <wdr:hasHost>example.org</wdr:hasHost>
    </wdr:Scope>
  </wdr:hasScope>
  <wdr:hasDescription rdf:resource="#description" />
</wdr:WDR>

<rdf:Description rdf:ID="description">
  <ex:property1>value 1</ex:property1>
  <ex:property2>value 2</ex:property2>
</rdf:Description>

DR Attribution

<wdr:WDR>
  <foaf:maker rdf:resource="http://authority.org/foaf.rdf#me" />
  <dcterms:issued>2006-09-01</dcterms:issued>
  <wdr:validUntil>2007-09-01</wdr:validUntil>
  <wdr:hasScope>
    <wdr:Scope>
      <wdr:hasHost>example.org</wdr:hasHost>
    </wdr:Scope>
  </wdr:hasScope>
  <wdr:hasDescription rdf:resource="#description" />
</wdr:WDR>

<rdf:Description rdf:ID="description">
  <ex:property1>value 1</ex:property1>
  <ex:property2>value 2</ex:property2>
</rdf:Description>

DR Scope

<wdr:WDR>
  <foaf:maker rdf:resource="http://authority.org/foaf.rdf#me" />
  <dcterms:issued>2006-09-01</dcterms:issued>
  <wdr:validUntil>2007-09-01</wdr:validUntil>
  <wdr:hasScope>
    <wdr:Scope>
      <wdr:hasHost>example.org</wdr:hasHost>
    </wdr:Scope>
  </wdr:hasScope>
  <wdr:hasDescription rdf:resource="#description" />
</wdr:WDR>

<rdf:Description rdf:ID="description">
  <ex:property1>value 1</ex:property1>
  <ex:property2>value 2</ex:property2>
</rdf:Description>

DR Description

<wdr:WDR>
  <foaf:maker rdf:resource="http://authority.org/foaf.rdf#me" />
  <dcterms:issued>2006-09-01</dcterms:issued>
  <wdr:validUntil>2007-09-01</wdr:validUntil>
  <wdr:hasScope>
    <wdr:Scope>
      <wdr:hasHost>example.org</wdr:hasHost>
    </wdr:Scope>
  </wdr:hasScope>
  <wdr:hasDescription rdf:resource="#description" />
</wdr:WDR>

<rdf:Description rdf:ID="description">
  <ex:property1>value 1</ex:property1>
  <ex:property2>value 2</ex:property2>
</rdf:Description>

More on Scope

(Because it's the hard part)

More on Scope

(Because it's the hard part)

Want to be able to define a group through several means:

More on Scope

(Because it's the hard part)

Want to be able to define a group through several means:

• Pattern matching against (parts of) URIs, e.g.
  • host ends with example.org
  • Scheme is http or https
  • Path begins with foo

More on Scope

(Because it's the hard part)

Want to be able to define a group through several means:

• Pattern matching against (parts of) URIs, e.g.
  • host ends with example.org
  • Scheme is http or https
  • Path begins with foo
• Resource has one or more properties

More on Scope

(Because it's the hard part)

Want to be able to define a group through several means:

• Pattern matching against (parts of) URIs, e.g.
  • host ends with example.org
  • Scheme is http or https
  • Path begins with foo
• Resource has one or more properties
• Simple listing

More on Scope

(Because it's the hard part)

Want to be able to define a group through several means:

• Pattern matching against (parts of) URIs, e.g.
  • host ends with example.org
  • Scheme is http or https
  • Path begins with foo
• Resource has one or more properties
• Simple listing
• All should support negation

XML approach

The scope of the DR is the sport and fashion sections of example.mobi, example.net and any subdomains thereof; and excatly the sport and fashion sections of example.com.

<Scope>
  <host>
    <match name="example.com" type="exact"/>
    <match name="example.mobi"type="endsWith"/>
    <match name="example.net" type="endsWith"/>
    <path>
       <match name="/sport/" type="startsWith"/>
       <match name="/fashion/" type="startsWith"/>
    </path>
  </host>
</Scope>

RDF/Regular Expression Approach

<wdr:Scope>
  <wdr:hasHost>^example\.com$</wdr:hasHost>
  <wdr:hasHost>example\.mobi$</wdr:hasHost>
  <wdr:hasHost>example\.net$</wdr:hasHost>
  <wdr:hasPath>^sport|^fashion</wdr:hasPath>
</wdr:Scope>

The POWDER WG is chartered to produce a Recommendation on this and may offer alternative encoding methods.

DR Packages

A Package contains several DRs, each of which describes a subset of the resources covered by the Package as a whole.

DR package example

<wdr:Package rdf:ID="package">
  <wdr:hasPackageScope rdf:resource="#primaryScope" />

  <wdr:hasDRs rdf:parseType="Collection">
    <rdf:Description rdf:about="#dr_1" />
    <rdf:Description rdf:about="#dr_2" />
    <rdf:Description rdf:about="#dr_3" />
  </wdr:hasDRs>
</wdr:Package>

<wdr:Scope rdf:ID="primaryScope">
  <wdr:hasHost>example.org</wdr:hasHost>
</wdr:Scope>

DR package example

<wdr:Package rdf:ID="package">
  <wdr:hasPackageScope rdf:resource="#primaryScope" />

  <wdr:hasDRs rdf:parseType="Collection">
    <rdf:Description rdf:about="#dr_1" />
    <rdf:Description rdf:about="#dr_2" />
    <rdf:Description rdf:about="#dr_3" />
  </wdr:hasDRs>
</wdr:Package>

<wdr:Scope rdf:ID="primaryScope">
  <wdr:hasHost>example.org</wdr:hasHost>
</wdr:Scope>

DR package example

<wdr:Package rdf:ID="package">
  <wdr:hasPackageScope rdf:resource="#primaryScope" />

  <wdr:hasDRs rdf:parseType="Collection">
    <rdf:Description rdf:about="#dr_1" />
    <rdf:Description rdf:about="#dr_2" />
    <rdf:Description rdf:about="#dr_3" />
  </wdr:hasDRs>
</wdr:Package>

<wdr:Scope rdf:ID="primaryScope">
  <wdr:hasHost>example.org</wdr:hasHost>
</wdr:Scope>

DR package example

<wdr:Package rdf:ID="package">
  <wdr:hasPackageScope rdf:resource="#primaryScope" />

  <wdr:hasDRs rdf:parseType="Collection">
    <rdf:Description rdf:about="#dr_1" />
    <rdf:Description rdf:about="#dr_2" />
    <rdf:Description rdf:about="#dr_3" />
  </wdr:hasDRs>
</wdr:Package>

<wdr:Scope rdf:ID="primaryScope">
  <wdr:hasHost>example.org</wdr:hasHost>
</wdr:Scope>

HTTP Link Mechanism

HTTP Link Mechanism

Currently we use this:

<link rel="meta" href="http://www.example.org/labels.rdf" type="application/rdf+xml" title="Content labels" />

or its HTTP Header equivalent

Link: <http://www.example.org/labels.rdf>; /="/"; rel="meta"; title="Content labels";

HTTP Link Mechanism

rel="meta" is very vague

HTTP Link Mechanism

rel="meta" is very vague

Really want something like:

rel="POWDER mobileOK ICRA Foo"

HTTP Link Mechanism

Likely to use Profile concept as developed for HTML 4.0.1

Under active discussion in HTTP Working Group

Link-profile: <http://www.example.org/profile.html>; /="/";

Labelling AOL UK/Europe

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar).

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar). Controlled by an editor? Policy wonk?

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar). Controlled by an editor? Policy wonk?
2. The link tag

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar). Controlled by an editor? Policy wonk?
2. The link tag

Either in (X)HTML
<link rel="meta" href="/labels.rdf" type="application/rdf+xml" title="ICRA labels" />

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar). Controlled by an editor? Policy wonk?
2. The link tag

Either in (X)HTML
<link rel="meta" href="/labels.rdf" type="application/rdf+xml" title="ICRA labels" /> Controlled by page template(s)

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar). Controlled by an editor? Policy wonk?
2. The link tag

Either in (X)HTML
<link rel="meta" href="/labels.rdf" type="application/rdf+xml" title="ICRA labels" /> Controlled by page template(s)

OR as HTTP Header
Link: </labels.rdf>; /="/"; rel="meta" type="application/rdf+xml"; title="ICRA labels";

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar). Controlled by an editor? Policy wonk?
2. The link tag

Either in (X)HTML
<link rel="meta" href="/labels.rdf" type="application/rdf+xml" title="ICRA labels" /> Controlled by page template(s)

OR as HTTP Header
Link: </labels.rdf>; /="/"; rel="meta" type="application/rdf+xml"; title="ICRA labels"; Controlled by server engineers

Labelling AOL UK/Europe

Two components:

1. The data file (labels.rdf or similar). Controlled by an editor? Policy wonk?
2. The link tag

Either in (X)HTML
<link rel="meta" href="/labels.rdf" type="application/rdf+xml" title="ICRA labels" /> Controlled by page template(s)

OR as HTTP Header
Link: </labels.rdf>; /="/"; rel="meta" type="application/rdf+xml"; title="ICRA labels"; Controlled by server engineers

http://www.t-online.de/labels.rdf (1)

<?xml version="1.0"?>
<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:label="http://www.w3.org/2004/12/q/contentlabel#"
  xmlns:icra="http://www.icra.org/rdfs/vocabularyv03#">

  <rdf:Description rdf:about="">
    <dc:creator rdf:resource="http://www.icra.org" />
    <dcterms:issued>2005-12-02</dcterms:issued>
    <label:authorityFor>http://www.icra.org/rdfs/vocabularyv03#</label:authorityFor>
  </rdf:Description>

http://www.t-online.de/labels.rdf (2)

<label:Ruleset>
  <label:hasHostRestrictions>
    <label:Hosts>
      <label:hostRestriction>t-online.de</label:hostRestriction>
      <label:hostRestriction>t-online.net</label:hostRestriction>        
      <label:hostRestriction>erotic-lounge.com</label:hostRestriction>        
      <label:hostRestriction>eroticlounge.com</label:hostRestriction>        
      <label:hostRestriction>erotic-lounge.de</label:hostRestriction>       
      <label:hostRestriction>eroticlounge.de</label:hostRestriction>       
      <label:hostRestriction>t-online-vision.de</label:hostRestriction>     
      <label:hostRestriction>t-vision.de</label:hostRestriction>     
      <label:hostRestriction>ivwbox.de</label:hostRestriction>    
      <label:hostRestriction>sam.t-online.com</label:hostRestriction>   
      <label:hostRestriction>a.ads.t-online.de</label:hostRestriction> 
      <label:hostRestriction>chunnel.de</label:hostRestriction> 
      <label:hostRestriction>t-online.autoscout24.de</label:hostRestriction>
      <label:hostRestriction>ltur.com</label:hostRestriction>
      <label:hostRestriction>handy.de</label:hostRestriction>
      <label:hostRestriction>eu-xmedia.de</label:hostRestriction>
      <label:hostRestriction>intensifier.de</label:hostRestriction>
      <label:hostRestriction>mobile2day.de</label:hostRestriction>
      <label:hostRestriction>bunte.de</label:hostRestriction>
    </label:Hosts>
  </label:hasHostRestrictions>
  <label:hasDefaultLabel rdf:resource="#label_1" />
</label:Ruleset>

http://www.t-online.de/labels.rdf (3)

<label:ContentLabel rdf:ID="label_1">
  <rdfs:comment>Label for all/most of website</rdfs:comment>
  <icra:nz>1</icra:nz>
  <icra:sz>1</icra:sz>
  <icra:vz>1</icra:vz>
  <icra:lz>1</icra:lz>
  <icra:oz>1</icra:oz>
  <icra:cz>1</icra:cz>
  <rdfs:label>No nudity; No sexual material; No violence; 
  No potentially offensive language; 
  No potentially harmful activities; No user-generated content; 
  </rdfs:label>
</label:ContentLabel>

http://www.t-online.de/labels.rdf (4)

<label:ContentLabel rdf:ID="label_4">
  <rdfs:comment>Label for all/most of website</rdfs:comment> 
  <icra:na>1</icra:na> 
  <icra:nb>1</icra:nb> 
  <icra:nc>1</icra:nc> 
  <icra:sa>1</icra:sa> 
  <icra:sb>1</icra:sb> 
  <icra:sd>1</icra:sd> 
  <icra:sf>1</icra:sf> 
  <icra:vz>1</icra:vz> 
  <icra:la>1</icra:la> 
  <icra:oz>1</icra:oz> 
  <icra:cz>1</icra:cz> 
  <rdfs:label>Exposed breasts; Bare buttocks; Visible genitals; 
  Passionate kissing; Obscured or implied sexual acts; Explicit 
  sexual language; Erotica; No violence; Abusive or vulgar 
  terms; No potentially harmful activities; No user-generated content;</rdfs:label> 
</label:ContentLabel>

Labelling AOL UK/Europe

Either link to the file
<link rel="meta" href="/labels.rdf" type="application/rdf+xml" title="ICRA labels" />

OR link to a specific DR
<link rel="meta" href="/labels.rdf#label_4" type="application/rdf+xml" title="ICRA labels" />

Labelling AOL UK/Europe

Either link to the file
<link rel="meta" href="/labels.rdf" type="application/rdf+xml" title="ICRA labels" />

OR link to a specific DR
<link rel="meta" href="/labels.rdf#label_4" type="application/rdf+xml" title="ICRA labels" />

www.fosi.org