Difference between revisions of "attention-brainstorming"

From Microformats Wiki
Jump to navigation Jump to search
(first take)
Line 35: Line 35:
 
=== Each Attention Item contains ===
 
=== Each Attention Item contains ===
  
 +
* item url (rss article url, etc)
 +
* parent context (feed or source site, )
 
* last read
 
* last read
 
* duration
 
* duration
 
* followed links
 
* followed links
* rel/voatlink
+
* rel/votelink
 
* tags
 
* tags
 
* dateremoved
 
* dateremoved

Revision as of 21:46, 14 December 2005

Attention Brainstorming

This page is for brainstorming about ideas, proposals, constraints, requirements for an Attention microformat.

Authors

  • Tim Brown
  • Tantek Çelik
  • Eric Hayes
  • Rohit Khare
  • Kevin Marks

Experience

Both Technorati and Attensa have implementation experience with Attention.XML and other attention formats.

Other Attention-like Things

Lessons Learned

  • Hierarchy in the format gets in the way more than it helps
  • Need to define a minimally useful subset for ease of implementation and interoperability
  • Need to "chunk" any sets of additional data

Goals / Requirements

Definite

  • Needs to be represent sparse (over time and source) data
  • "Blendable" - get an attention "chunk" every day from a source and be able to aggregate the chunks into one attention file.
  • Flat by default. Permit hierarchy but don't require it, and don't require parsing of a hierarchy (i.e. allow treating the attention as set of attention items).

Strawman Schema Thoughts

Each Attention Item contains

  • item url (rss article url, etc)
  • parent context (feed or source site, )
  • last read
  • duration
  • followed links
  • rel/votelink
  • tags
  • dateremoved
  • read state
  • rating

Item Containers

  • .

See Also