[[PageOutline]] == Random ideas == * '''User interface''' * non binary features: link to objects, reverse lookup, link to property * template streamlining (mouseover comments for all items/features, link detection for all comments, etc.) * item page streamlining (reviews first, list all feature instances instead of recent only) * welcome ST page for user * ST annotation wizard * partially done but should additionally generate annotation overlaps between users * allow some simple HTML in comments (,) * recommendation channel edit functionality * filter negative features in view * '''Refactoring''' * diff-based syncer * use Beans instead of JSON for ST models (fix String vs. HTML escaping ugliness in the process) * use TDB named graphs for SF namespaces? * '''Annotating items''' * explicit similar-to/part-of feature type (further input for feature type recommender) * rules for deducing features (per-user basis, let user confirm generated feature instances) * sameAs links to other data sources * '''Adaptation for music domain''' * simplify entering song/band information * download/cache songs * generate/play playlists, possibly with changing style over time (AutoDJ) * '''Book domain ontology''' * see also [wiki:DBTropes DBTropes] * [http://en.wikipedia.org/wiki/Literary_technique Literary technique], [http://en.wikipedia.org/wiki/Fiction-writing_modes Fiction-writing modes], [http://en.wikipedia.org/wiki/Style_(fiction) Style], [http://en.wikipedia.org/wiki/Outline_of_fiction Outline of fiction] * '''Metadata sharing''' * optimize synchronization * cache and forward data on intermediate nodes in a secure fashion * superpeer nodes? Possibly represented within the network? (superpeer3-hasFeature-!IsHubForMusic) * detect 'hot topics' * '''Trust network''' - trust as in "peer is competent/peer's metadata is important") * [http://www.informatik.uni-freiburg.de/~dbis/Publications/04/EEE04.html Spreading Activation Models for Trust Propagation] * explicit representation of trust (see Skippies ontology) * user interface changes for that * trust metric changes for that * '''Ontology evolution''' * simple skipinions ontology editor * update and synchronize ontologies (and facts!) on peers == Implementation details == * '''Facts/graph synchronization''' idea * every peer implements * {{{String getDiffForNamespace(String namespace, String haveHash, String wantHash)}}} * {{{String getMostCurrentHash()}}} * {{{String isValid(String hash)}}} * {{{String getPubkey()}}} * {{{? subscribe(?)}}} * logic: once a day, every machine dumps its 'own' facts to an NTriples file along with a timestamp and the data's hash * when peers call {{{getDiffForNamespace()}}}, a diff from ''haveHash.dat'' to ''wantHash.dat'' is calculated and sent * Distributed Storage * simple distributed storage (without signatures) with trust can be implemented usind {{{getMostCurrentHash}}} and {{{isValid}}} * distributed storage with signatures can be implemented with {{{getPubkey}}} (using a true keyserver might be desirable though) * optimized push synchronization could use some subscription mechanism. Integrate with [http://www.xmpp.org/extensions/xep-0060.html XMPP pubsub]? * Ontology evolution/rules * rules that upgrade existing facts could be added to the diff file == Done == * '''Internal namespaces for ontologies''' ({{{xmpp://schwarz@xmpp.km.opendfki.de/ont/ludopinions#UsesDice}}}) * this way people can create own ontologies, and ontology management/evolution can be done similar to facts synchronization * Play sounds from !JavaScript: http://www.schillmania.com/projects/soundmanager/ * show number of (existing) feature instances for each item (in !ItemPane) - metadata certificates * show number of feature instances for each feature class (in !FeaturePane) and arithmetic mean/standard deviation for applicability - metadata certificates * red/green blobs * RDF importer that changes namespaces * FloriansDiplomaThesis topics (Jul-Dec 2008) * related work: Semantic audio - [http://www.semanticaudio.org/htmls/publications.html List of publications] * finish skiptrax ontology (see [http://musicontology.com/ Music Ontology]) * metadata importers/exporters (ID3, LastFM, etc.) * expert recommender (ask friends about people having knowledge about X/interests in Y) * scalable trust metric * fast computation of feature summaries * '''User interface''' * Plain HTML pages for item/feature instances, just for browsing and linked data * For ''Person instances'': Trust, feature(types) I (dis)agree with, last annotations, list of annotated items (by date/...) * For ''Item instances'': Review stats, list of annotators (by degree of agreement), list of feature instances (by date/...) * For ''Feature types'': Comment, example positive/negative item instances (by number of annotations), experts for this type, dispute list (for the current item), list of instances (for the current item)