Skip to main content

Home/ Diigo Community/ Contents contributed and discussions participated by Scott Linford

Contents contributed and discussions participated by Scott Linford

Graham Perrin

Diigo, API, RDF, semantic web - 114 views

API semantic RDF suggestion wish gpd4 application programming interface spam (electronic)
started by Graham Perrin on 25 May 09 no follow-up yet
  • Scott Linford
    Me too. Diigo, please make semantic markup painless... somehow. Yes, I know painless is torture for the developer. I'd help code if you'd let me.

    Brain storming (or just possible cerebral flatulence)

    Diigo is perfectly situated to bring semantic tools to the public. Please convert the average Joe into an RDF contributor. Make it simple and, at first, stupid. E.g., a predefined vocabulary for common relationships: Manchester is a City; This particular Manchester refers to the one in NH, USA. Automate the rote work of translating to RDF.

    Give the contributor the option to make meta data private, public but attributed (like a shared tag), or publicly available while the contributor remains anonymous to most users (not to admins to control spam, graffiti, and politically motivated flotsam).

    For this to take off, Diigo must provide immediate benefit for Joe's effort; let Joe know that a topic of interest is being researched in Manchester, NH. Slap SPARKLE "magic" to Diigo's current objects (tags, comments, bookmarks, highlighting). Possible triple store entry: Joe uses tag XYZ. Use his existing contributions to feed the immediate payoff.

    Eventually -- when people start to "get it" and want more flexibility -- allow them to customize their semantic vocabulary. Allow meta data and related vocabularies to be created collaboratively. Help out communities by plugging into tools like and existing ontologies. Open Calais makes inferences (guesses); let the user decide whether the guesses are correct and relevant. If so, a single click could add the Calais guess to the store of trusted knowledge. Anonymous feedback could be provided to engines like Calais to help them improve. Again, make the value obvious. Visually connect the Calais data with the important stuff on the page. Go crazy, even prioritize the connections by the user's current goal (what is the user currently interested in).

    The highlighting feature already generates RDF like data. Example triple store entry: Joe cares about passage XYX on page PDQ. Add it to the triple store as such. The advantage of RDF over the existing highlighting feature will be for future searches. I'd like relevant portions of site to be "highlighted" before Joe sets eyes on it for the first time. With usage (and incremental refinement on Diigo's part) Joe's interest of the moment will be honored, the search will be short, and the browser's "find in page" feature will be obsolete.

    And maybe someone on the Diigo team will be knighted, like Sir Tim.
1 - 1 of 1
Showing 20 items per page