attention-brainstorming

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

• Personal Status Pages

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).

Non-goals

These are things we want to avoid in an Attention format, mostly due to privacy reasons.

• cookies
• login information
• personally identifiable information in URLs (e.g. PHP session info)

Strawman Schema Thoughts

Each Attention Item contains

item info

• item url (rss article url, etc)
• parent context (feed or source site, )
• attention date (article last read time)

implicit info

• duration (attention duration, how long did i look at this page or article)
• followed links (click through. could result in a next attention item)
• read state

explicit info

• voting
• hReview
  • rating
  • tags
• explicit read or unread state

• date removed

Item Containers

• .

See Also

• attention-examples
• attention-formats