ACTION-207: Develop a use case for content aggregation
Develop a use case for content aggregation
- State:
- closed
- Person:
- Kai Scheppe
- Due on:
- March 9, 2006
- Created on:
- March 2, 2006
- Related emails:
- RE: ACTION-207: Use case for mobileOK in content syndication (from jo@linguafranca.org on 2006-03-09)
- Minutes from Cannes F2F meeting (from dom@w3.org on 2006-03-08)
- ACTION-207: Use case for mobileOK in content syndication (from k.scheppe@t-online.net on 2006-03-03)
Related notes:
A content provider uses a variety of sources for his content. Some are internal to the company itself, others are provided by partner companies by means of an import mechanism, others again use iFrames and are inserted on the client.
In short, the content provider has, in some sense, very little control over the content he syndicates.
Since the mobileOK trustmark can only apply to the full page delivered to the end user, the content provider must ensure in some fashion that the content originating with partner firms does not in some fashion invalidate the trustmark.
The only realistic mechanism is the claim combined with the willingness to correct problems if they are discovered.
This hinges on the iFrames which remove any possibility of the content provider to control content prior to display.
Display change log.