Attention.xml Brainstorming
This page is for work in progress on evolving the ![[WWW]](https://cdn.statically.io/img/web.archive.org/web/20060108154410im_/http://developers.technorati.com/content/rightsidebar/img/moin-www.png){kind=small}
Attention.XML specification.
Table of Contents
Authors
-
[
Eric Hayes] - [Attensa, Inc.]
-
...
Proposed Improvements
Microformats and Additional Fields Discussion
Proposed by [Eric Hayes], [Attensa, Inc.] History
[Attensa, Inc.] is currently using an attention stream to accomplish communication of attention data for both analysis and synchronization between client side components in real time, and server side systems in near-real time. We are currently in the process of creating and accepting Attention.XML as a shared generic context both client and server side. My goal in the use of Attention.XML is to communicate all of the data required for a full featured sharing of the users current state, and action history. It is important that I say this, so that my suggestions do not seem as an exercise in theory, rather real world needs. (I will be careful to point out when i deviate from true current needs.)
Introduction
I believe it possible to make up an Attention.XML Microformat, based on a number of new and existing Microformats (some of which are pointed out in the main [Microformats wiki page] Existing Microformats
-
[[XOXO]]
-
[
XFN]
-
[[votelinks]]
-
[[hcard|hCard]]
Discussion Points
My stab at a few things we probably need to work out sooner, rather than later.-
Sparse Attention.XML - I think one of the major shifts i am proposing has to do with creation of sparse Attention.XML files.
-
discuss...
-
internalid
-
Do we want this concept?
-
Or leave it to namespace add-ons?
-
Attention Stream Support
-
Article level Parent Context field
-
Do we allow for the parent feed in the article? (optionally)
-
Or just use a thin version of the parent feed container to accomplish the same thing?
-
I'm already talking myself out of this one... -eh
-
Feed level group path
-
I think my desire to add this comes from it being the way we internally represent a feeds group hierarchy as a full path attached to the feed.
-
Much more efficient when representing a sparse tree of feed(s).
-
Tags, votes, rating - In the world of attention data, explicit attention is greatly valuable.
-
How do we capitalize on this?
-
I would like to explore if an Attention.XML file, created correctly, could be used to share a users Tags & the items they have tagged
Attention.XML Uses
-
Get complete picture of a person's Attention.XML
-
I am at a stumbling point with regard to ever wanting a completely unfiltered Attention.XML file, but...
-
Most expensive to create
-
Large to transport
-
Get Users Feeds
-
OPML replacement
-
Used for syncing feed adds/removes
-
Get Filtered Attention.XML file
-
Active Articles only (those still in feed)
-
Recent Articles only (those in feed within last amount of time)
-
By Group
-
By Feed
-
By Date (range?)
-
Only those with Attention
-
Only those with Tags
-
Only those with Vote Attention
-
Only those with Rating Attention
-
more...
Attention Stream Support
At Steve Gillmor's prompting, I would like the group to explore some optional flattening of some of the Attention Microformats to better support streaming. In the below Microformats will be support for a light chain of context for articles and feeds. This could allow for an article or feed to be a standalone element in an attention stream.Proposed Base Microformats
Here is an initial proposal for a collection of Microformats which could be used to build up Attention.XML as it exists to day, and add in a few pieces required to flush out the format.Attention Data Microformat
I would like to have this single Attention Microformat available to both feeds and articles, and as I move forward with this initial straw man, I will see how they fit for both uses. A decision will have to be made as to if this is another case of excessive overloading... I am not sure at this pointThis Microformat describes a block of attention attached to either a feed or article.
All elements optional, unless specified otherwise
-
Existing Elements
-
lastread
-
duration
-
followedlinks
-
rel/votelink
-
tags
-
Proposed Additional Elements
-
dateremoved ISO8601 datetime indicating when this article was marked as removed.
-
Note: a duration of zero is valid, and should indicate the article was removed without reading.
-
readstate read | unread. Indicating if this article is currently marked as read. Note: a non-zero duration and a read state of unread indicates the user has either read the article and specifically marked it as unread.
-
It is possible that duration accumulation could come from the article being visible to the user, but not specifically marked as read. Discussion is needed here, as metrics on faulty duration values are undesired.
-
rating 1 | 2 | 3 | 4 | 5 or something like that. I believe that a good attention picture is gained by both implied and explicit interaction by the user. It is quite valuable to inspire users to interact, and ratings are a great way to accomplish this.
-
Q: could [[votelinks]] be made to support a rating as part of the vote?
Attention Article Microformat
This Microformat describes an article, and optionally article level attention data. It must be contained inside of Attention Feed container.All elements optional, unless specified otherwise
-
Existing Elements
-
permalink/guid (required)
-
title
-
type
-
etag
-
lastupdated
-
Proposed Changed Element(s)
-
internalid An unique value for this article, generated by the generationsource. This could be used for more efficient synchronization. Guaranteed to be consist ant between generations of the Attention.XML file.
-
Discussion is needed here. I assume this could be handled by use of a namespace, given a standard, support for multiple internalid's could be useful in the form of <generationsource:internalid>
-
feedurl (Stream element, allowing an article to stand on its own.) Parent Feed's url.
-
Attention Data Microformat
Attention Feed Microformat
This Microformat describes a feed, acts as a container of articles, and optionally feed level attention data. It may be contained inside of either the Root Attention.XML file, or an Attention Group container.All elements optional, unless specified otherwise
-
Existing Elements
-
url (required)
-
title
-
alturls
-
etag
-
lastupdated
-
dateadded
-
dateremoved
-
userfeedtitle
-
Proposed New/Changed Elements
-
internalid An unique value for this article, generated by the generationsource. This could be used for more efficient synchronization. Guaranteed to be consist ant between generations of the Attention.XML file.
-
Discussion is needed here. I assume this could be handled by use of a namespace, given a standard, support for multiple internalid's could be useful in the form of <generationsource:internalid>
-
grouppath (Stream element, allowing a feed to stand on its own.) Group hierarchy flattened.
-
Attention Data Microformat
Attention Group Microformat
This Microformat is container of sub-groups and/or feeds used to define an Attention.XML file.All elements optional, unless specified otherwise.
-
Existing Elements
-
title (required)
-
Proposed New/Changed Elements
-
internalid An unique value for this article, generated by the generationsource. This could be used for more efficient synchronization. Guaranteed to be consistent between generations of the Attention.XML file.
-
Discussion is needed here. I assume this could be handled by use of a namespace, given a standard, support for multiple internalid's could be useful in the form of <generationsource:internalid>
-
Attention Subscription Microformat [array]
-
Attention Group Microformat [array]
Attention.XML (Root) Microformat
This Microformat is the root of an Attention.XML file. It contains header information, and arrays of groups or subscriptions.All elements optional, unless specified otherwise.
-
title Some optional title assigned by the owner. (an example of this would be "pre-upgrade backup snapshot", or "2005.06 backup")
-
hcard I wonder if this is overkill, additionally, it does not really support the concept of an anon id hash as an option to support merging.
-
generationsource A unique identifier for the who created the file. See article and feed internalid elements. (an example could be "Attensa for Outlook", where internalid's would be our internal database ids). I could be talked out of this quite easily, but this is such a useful tool when doing efficient synchronization.
-
generationdate ISO8601 datetime indicating when this Attention.XML file was created
-
trimdate ISO8601 datetime indicating when used as a trim datetime when creating this Attention.XML file.
-
Attention Subscription Microformat [array]
-
Attention Group Microformat [array]