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://labellingauthority.example.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://labellingauthority.example.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://labellingauthority.example.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://labellingauthority.example.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://labellingauthority.example.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:robots>allow</ex:robots>
  <ex:access>subscription</ex:access>
</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

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

rel="meta" is very vague

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

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>; /="/";

www.fosi.org