attention-brainstorming: Difference between revisions
Jump to navigation
Jump to search
m (Reverted edits by PaserRovar (Talk) to last version by LynX) |
|||
| (10 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
= Attention Brainstorming = | = Attention Brainstorming = | ||
This page is for brainstorming about ideas, proposals, constraints, requirements for an Attention microformat. | This page is for brainstorming about ideas, proposals, constraints, requirements for an [[attention|Attention]] microformat. | ||
This is part of an open standards community effort to update (even rethink and rewrite) the [http://developers.technorati.com/wiki/attentionxml Attention.xml] format on a strong foundation of research of existing examples and formats, as well as leveraging the Attention.XML implementation experience from [http://attensa.com Attensa], [http://commerce.net CommerceNet], [http://technorati.com Technorati], and any other interested Attention developers. | |||
== Authors == | == Authors == | ||
| Line 29: | Line 32: | ||
* Needs to be represent sparse (over time and source) data | * 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. | * "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). | * 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 a simple flat 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 == | == Strawman Schema Thoughts == | ||
| Line 35: | Line 45: | ||
=== Each Attention Item contains === | === Each Attention Item contains === | ||
==== item info ==== | |||
* item url (rss article url, etc) | * item url (rss article url, etc) | ||
* parent context (feed or source site, ) | * parent context (feed or source site, ) | ||
* attention date (article last read time) | * attention date (article last read time) | ||
==== implicit info ==== | |||
* duration (attention duration, how long did i look at this page or article) | * duration (attention duration, how long did i look at this page or article) | ||
* followed links (click through. could result in a next attention item) | * followed links (click through. could result in a next attention item) | ||
* read state | * read state | ||
* rating | |||
==== explicit info ==== | |||
* [[vote-links|voting]] | |||
* [[hreview|hReview]] | |||
** rating | |||
** [[rel-tag|tags]] | |||
* explicit read or unread state | |||
* date removed | |||
=== Item Containers === | === Item Containers === | ||
| Line 53: | Line 71: | ||
* [[attention-examples]] | * [[attention-examples]] | ||
* [[attention-formats]] | * [[attention-formats]] | ||
* Previous [http://developers.technorati.com/wiki/AttentionXMLBrainstorming Attention.xml brainstorming] thoughts. | |||
Latest revision as of 18:53, 20 December 2008
Attention Brainstorming
This page is for brainstorming about ideas, proposals, constraints, requirements for an Attention microformat.
This is part of an open standards community effort to update (even rethink and rewrite) the Attention.xml format on a strong foundation of research of existing examples and formats, as well as leveraging the Attention.XML implementation experience from Attensa, CommerceNet, Technorati, and any other interested Attention developers.
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 a simple flat 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
- date removed
Item Containers
- .
See Also
- attention-examples
- attention-formats
- Previous Attention.xml brainstorming thoughts.