Attention. xml

Source: Internet
Author: User
Http://herock.net/archives/000108.html

Attention. xml

Nearly a month ago, when I saw Wenxin's Attention. XML-RSS extension technology, I immediately felt that FeedChoice would use it!

Owen said:

Current RSS reading problems:
1. Excessive information: a common problem in RSS reading. We may have collected 300 sources of information, which are updated every day and cannot be viewed at all.
2. Lack of participation: at present, RSS reading is an individual action. We can use some tools to know what RSS messages a friend has subscribed to, but what specific items they have read every day?
3. Collaboration is not possible: collaboration between teams or several persons is not possible.
4. Lack of accuracy: The subscribed RSS source may have hundreds or even hundreds of updates each day. Which of the following information is valuable to you? What are you interested in? This makes us unable to start.
5. Lack of prompt function: many times a piece of information may be written to a Blog by several or even a dozen people, which leads to repeated clicks on the same link from different RSS information.

All of the above are currently unsolved RSS reading methods, and the purpose of Attention. XML is to solve these problems.

That is to say, Attention. what XML tries to solve is to minimize the pressure on readers due to information overload during RSS reading. This overload has gradually become a common problem, incomplete (preliminary ideas and practices for dealing with RSS information overload), keso (information overload and market opportunities), and many others are plagued by this problem. I firmly believe that, "RSS information overload" must be a pain point in the market, because at least I am "sore" now ".

Attention. the idea of XML is the same as that of FeedChoice. FeedChoice also hopes to filter a large number of existing feeds for specific users, and select the Feed that he may consider important from the Feed that he has not subscribed.

This process may be complicated. It should not be a simple voting system or ranking system, because it is emerging in this way, under the interaction of various chaotic factors, although the public opinion may be representative, it is impossible to have an appetite for everyone. It cannot be a fully personalized evaluation system because people are socialized, it is necessary to retain definite coordinates in the social system. Personal likes and dislikes often need to be taken as an important reference based on socially recognized standards. This is also one of the drawbacks discovered by old pipes: reading news using rss, it is impossible to directly perceive the positioning of a specific news title under the social background ".

While Attention. XML seems to better solve this problem. You can record your reading habits to analyze the advantages and disadvantages of a Feed in your personal system, and share the Attention of others. XML to determine the advantages and disadvantages of Feed in the social system. The combination of the two is comprehensive.

The next question is, how can we turn this beautiful idea into reality? Attention is studied. I also consulted Owen about the XML protocol and understood that we should have dedicated support for Attention. XML online storage/synchronization service, in combination with Attention. XML parsing/reading services (web or client) can truly begin to enter the practical stage.

In the example that can be seen now, using feature will be back online soon ".

The other is yahoo's My web. It is said that the output of attention. xml has been provided, but after registration, I have rummaged up and down every corner, but I cannot find it! Only one XML icon is found, but it is in the standard Rss2.0 format. I cannot explain it. If it wasn't for the last time, click the address of the above RSS file ".. /rss. xml "".. /attention. xml.

However, finding it is useless. my web seems to only provide an attention format file output and cannot really use the attention feature. Maybe wait.

FeedChoice can't wait any longer. The previous development work has started, but we may consider developing an application that truly supports the attention. XML protocol.

To help you understand Attention as deeply as possible. XML, it took some time to put attention. the xml document contains Chinese characters (long, so it is included in the full text). I also want to know more about attention. XML is a bit useful.

The full text is here:

Attention. XML

Attention. XML is an open standard based on open source code (see example: XOXOSampleCode.

Using this standard helps you understand what you have read, where your time is spent, and what you may be concerned about.

Issue Statement (Summary)

How many sources of information must be tracked?
Why have you been exhausted by clicking the same link from N different blogs?
The RSS reader automatically updates the content, but which of the following information should be taken into consideration?
Attention. XML is designed to solve these problems, making it possible to construct a brand new Blog and Feed-related service.

Format

Format Overview

Attention. XML is an XML file. The format of this file contains the outline of the Feed and Blog. Each Feed is an outline, and each Post under the Feed is an outline. Note the following information in this hierarchical outline: The last loading time of the Feed/post, the time spent on the Feed/post, the number of recent accesses to the Feed/post, such as "agree" or "disagree" set by the user.

Format Protocol

The Attention. XML outline contains the following types of entries. The attribute values of these entries are strings unless otherwise specified.

Group: the Group does not have URL tags, but each Group has the following tags:
Title. In fact, this title is set by the user for a blog group or Feed group.
Children: groups or Blogs
Blog/Feed/site. Each Blog/Feed/site has the following tags:
Title. name or title
Url. Each entry has a primary URL address.
Alturls. Resource secondary URL/Title List. For example, for a Blog or other Feed type, type information can be retrieved through HTTP request and cached as necessary.
Etag. HTTP 1.1, sec. 14.19
Lastupdated. Written by the attention. xml storage/Analysis Server
Dateadded. the date and time when the Feed is added to Blogroll. When the Feed is added, it is added by the application. If it is not added for the first time but retrieved again, the application may ignore it. The format of ISO8601 datetime must be followed.
Dateremoved. The time when data is deleted from Blogroll and added through the application. This process is completed by sending commands by the storage/Analysis Server. The format of ISO8601 datetime must be followed.
Lastread. indicates that the user determines the time when a Feed is read (maybe through the "select" method ). The format of ISO8601 datetime must be followed.
Readtimes. FIFO (first-in-first-out) sequence (the length is equal to the time required for the operation. We recommend that you add the reading time at least 16 seconds. Must follow ISO8601 datetime
Userfeedtitle. The title set by the user for a Feed, written through the application.
Rel/xfn. The social relationships presented by the author in this Blog/Feed. For details, see XFN.
Rev/votelink. "vote in favor", "Vote against", and "Drop permission ". For details, see VoteLinks.
Tags. A mechanism for users to customize Tags/Annotations for content. Here, let's look at the Tags example: Technorati tags
Children. Articles/entries.
Post/Item/Page. Each article/entry/Page contains the following tags:
Title. name or title.
Permalink/guid. Act as the unique identifier and make it look standard, as described here: http://www.xml.com/lpt/a/2004/08/18/pilgrim.html
Type. defines the MIME type of permalink. The default value is "text/html.
Etag. HTTP 1.1, sec. 14.19
Lastupdated. defines the last update time of the article, which must follow the ISO8601 datetime.
Lastread. indicates that the user determines the time when a Feed is read (maybe through the "select" method ). The format of ISO8601 datetime must be followed.
Duration. The number of seconds that the user takes to read this article/entry (a non-negative integer ).
Followedlinks. The URL list you click or enter in this article.
Rev/votelink. "vote in favor", "Vote against", and "Drop permission ". For details, see VoteLinks.
Tags. A mechanism for users to customize Tags/Annotations for content. Here, let's look at the Tags example: Technorati tags
Children: None
Example

Each Feed

The following are OPML fragments. After the head information is sent, the information of each Feed is transmitted if the Feed exists.

The typical Attention. xml xoxo should look like this:

Atitle
Description
Descstr
Alturls
Atomurl
Xmlurl
Attention. XML includes the following attributes mentioned in the preceding plan:

Alturls, etag, lastupdated, dateadded, dateremoved, lastread, readtimes, userfeedtitle, rel, tags

Each article

In OPML, each Feed has a set of child elements, which are expressed through outlines.

In the typical Attention. XML document XOXO, it is as follows:

Title
Lastread
ISO-8601 date
Duration
Seconds value
Followedlinks
Link1
Link2
Permalink and guid values are required-this will be the identifier of each article or entry.
The requirements for the value of lastread are the same as above and must follow the ISO-8601 time format to indicate the last loading time of the entry.
The same is true for duration-the number of seconds spent on the entry.
Others are described in detail in the aforementioned plan.
This is the format requirement. AttentionSample is for reference.

Concept Verification

Here, Technorati will use the Attention. XML file or the subscription list output in OPML format (similar to NetNewsWire ):
Http://www.technorati.com/attention.html
By the way, after the test period is completed, the website of this network service may be converted from here to other places, but it will still be retained as an image and updated.

Here is the Attention. XML Service API file of Technorati: AttentionQuery.

Summary

There are many different types and layers of Attention. XML applications. Defining a general set of outlines helps to establish high interoperability among a variety of tools.

Overview of the simplest Feed Synchronization Service

The simplest Feed synchronization application or service must support a subset of the following Attention. XML plan:

Group. Group does not have the URL attribute. However, each Group has a "title ". Groups is parsed only when all the Feed lists must be exported.

Title. The application must check whether the title exists, but its content may be ignored.

Subclass: Groups or Blogs.

Blog/Feed. Each Blog/Feed contains the following tags:

URL. Each entry has a major URL, which we will change later.

Lastread. it is used to indicate the time (ISO8601) for the reader to read an article/entry for the last time (ISO8601). It may be selected and the application must make appropriate settings for it, if the reader has never passed this Feed, leave it blank or do not display it.

Children: posts/items.

Post/item. Each post or item is a Feed containing the following tags.

Permalink/guid.

Lastread. it is used to indicate the time (ISO8601) for the reader to read an article/entry for the last time (ISO8601). It may be selected and the application must make appropriate settings for it, if the reader has never passed this article/entry, leave it blank or do not display it.

After startup, the application needs to load the user's Attention. XML file from the storage service (maybe local files or online synchronization service) to the memory.

When a user clicks or selects a Feed in another way, the application must update the "lastread" attribute in the memory.

When a user clicks or selects an item from a Feed in other ways, the application must update the "lastread" attribute in the content.

Other unrecognized and supported attributes contained in Attention. XML obtained from the storage service must be retained without being damaged.

When exiting, the application must write the Attention. XML in the memory back to the storage service (such as local files or online Synchronization Service), including the following actions:

Re-read the Attention. XML file, in case another client changes it after the last read.

Add local changes and write the final Attention. XML file.

The application should synchronize Attention at the appropriate time (maybe regular or after the user has been in a certain time. XML file, so that you can synchronize local changes with other users in a timely manner, and reflect the latest change status of "lastread" by other users.

Feed Reader Overview

In addition to the most basic synchronization functions described above, a typical blog/feed reading tool should support the following complete Attention. XML protocol:

When a user adds a Feed to its list, the "dateadded" attribute is set accordingly.

When a user deletes a feed from the list, do not delete it. Instead, hide it in the user interface and set the "dateremoved" attribute.

When updating the "lastread" attribute of a blog/feed, write the available read duration in the current "lastread" to the "readtimes" attribute.

When a user reads a post/item, if the reading duration can be detected, the time value is immediately written into the "durationread" of the post/item.

If you click a link in post/item, add it to "followedlinks" in post/item.

If you have customized the title of post/item in the list, save the title to the "userfeedtitle" attribute.

A user interface is provided to express the social relationship (if any) through a feed/blog list ), the "rel" attribute is updated based on the xfn value.

A user interface is provided so that he can make the following comments on every blog/post and feed/item: "satisfied", "not satisfied", and "not commented ", once a user makes a choice, some "tags" examples are combined with Technorati tags.

Attention storage/synchronization service Overview

An attention storage/synchronization service must support the following actions:

Get. The client must be able to get the attention. xml file from the server. Optional extension features include the ability to use a specific user name/password to request the user's attention. XML files, and can be shared with other users (maybe included in their social networks) their attention. XML file. In addition, the following attributes of some blog/feed/post/item may be updated frequently: "lastupdated", "etag", "alturls", "title ". When the server receives and parses these blogs/feeds again, it is necessary to add all the URLs automatically found in the received blogs/feeds to the "alturls" attribute.

Post. The server must be able to receive the attention. xml file from any client and merge it into any earlier versions of the following files:

For all blogs/feeds/posts/items, specify the last "lastread" value.

If a blog/feed has the "dateremoved" attribute and the time is later than any "dateadded", remove the blog/feed from the list, and remove the "dateremoved" attribute.

Sort by the attributes of each blogs/feeds New and Old combined "readtimes" and keep those that have been recommended for at least 16 times.

Combine "followedlinks" in a post/item into a set.

Accept the "durationread" attribute of any feed/item that is higher than the current value.

Accept the "userfeedtitle", "rel", "Rev", "tags" attributes of any new feed sent from "Post.

Accept the "rel", "Rev", and "tags" attributes of any new entries in the feed sent from "Post.

DEMO code

For the sample code, see xoxosamplecode.

References

References

Xhtmlmod
XOXO
Xmdp
Xfn
Votelinks
Reltag
References

Identifying atom by Mark Pilgrim
Opml 1.0
Execution Tool

AttentionQuery API (Attention query API) in TechnoratiApi of Technorati)
Niall Kennedy's NetNewsWire export
Major version improvements

200-06-09

Use "rev" in VoteLinks to replace the previous "rel ".
2004-12-28

Remove the "groups" attribute from "blog/feed/site", because there is no well-known reading/parsing service that allows users to add one Feed to multiple Groups. The original attribute is defined as follows: "groups": the list of groups used to place Feeds. It means that one Feed can be put into multiple groups. Note: The application can restrict each Feed to only one group. If this setting exists, the first one in the Application List is used.
Add the "tags" attribute to the blog/feed/site and post/item/page.
2004-10-01

The first version Design Based on XOXO.
Discussion

Join Technorati Developer program and Developer list to participate in Attention. XML discussion.
AttentionXMLFAQ
AttentionXML discussion board
Here are some links from my Furl for your reference.

Technorati Tags: attentionxml, attention, web2.0

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.