1 Introduction
2 Importing trust from the web, pgp, etc
3 Problems with broad sem web (attacks)
4 Annotation, trust, etc.
Note: trust here is at a syntactic not nec. semantic level.
Also: signature splitting: subset of information exposable? Maybe direct from the source (capabilities possible here)
Motivations: accident, misapplication, bugs, maliciousness, "a fast buck". Eg, the mess that email systems are currently in: if apps (like FOAF) start to be seen as having concrete value, they will be subject to attack.
Note: cross-application interop. Application-specific semantics? How much can be captured using rdf, rdfs, owl, rdf-rules, ... ?
Taking a holistic view, how do technologies fare against attacks, misapplications, gaming? How does a sem web application operate? Analogy with a person: discovering new sources, new data, integrating with existing knowledge, in order to reach a goal. Where does it go? How does it rate stuff? When does it stop chasing links?
Leads to: maybe large-scale inference or other mechanisms, must be proof against this (relevant logics?). Maybe strong inference on the document level - a document-centric approach.
Lead maybe to the notion of "reputation" - closely related with annotation. Reputation can mean many things: how reliable is this data? Can I trust the source? Also: how was it collected? How has it been processed? Also: provenance important. (Pointer to demo)
Example within RDF of simple annotation scheme. Context: FOAF + annotations. TU/TD. More fine-grained than simple "rating" but not overcomplex. [ Example of this: Hofstadter, Penrose both have expert knowledge in the subject of (broadly) mechanisability of human intelligence. Yet appear to draw opposing conclusions. So rate knowledge, opinions differently? Difficult problem in general ] Annotation of services? What about "service as data", eg mapping axioms.