attention-brainstorming: Difference between revisions
Jump to navigation
Jump to search
m (→Definite) |
m (→Definite) |
||
| Line 25: | Line 25: | ||
* 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). | |||
=== Possible === | === Possible === | ||
* Easily converted to a stream | * Easily converted to a stream | ||
Revision as of 21:23, 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.
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).
Possible
- Easily converted to a stream