Tip

Atom: XML-based publishing and Web syndication


XML Developer Tip
(Receive this column in your inbox,
click Edit your Profile to subscribe.)

Atom: XML-based publishing and Web syndication

Last fall (Autumn, 2003,

    Requires Free Membership to View

that is) an initiative got underway at the IESG/IETF to define "... a common syntax for syndication, archiving, and publishing." According to Robin Cover's excellent summary of this work in progress, which now also involves the W3C as well as the IETF, Sam Ruby of the Emerging Technologies Group at IBM gets credit for most of the core ideas and design work in this area, which is now a cause celebre on numerous Internet wikis and weblog development sites.

How Atom is most commonly understood, however, is as a more general and powerful replacement for RSS (Really Simply Syndication or RDF Site Summary). RSS serves as the basis for most news headline feeds, Website metadata syndication, and content syndication—and is most strongly associated in many people's minds as the XML foundation for Web blogging. Much like RSS, Atom is developing as a consensus process from volunteers in the global Web community, but unlike RSS, Atom is intended to provide ways to keep content and metadata separate and distinct, and to provide mechanisms for delivery of all kinds of content from binary code to multimedia to the text and graphics most commonly associated with RSS feeds today.

In fact, Atom is intended to be extensible to support all kinds of application specific needs—such as licensing, access controls, content categorization, versioning, related resources, and more. Also, its core capabilities are built around primitives that should be familiar to anyone who's grappled with content creation and management issues already: sources or authorship, date stamps, resource identifier and locations, and numerous forms of content. The Atom API is described as presenting "... a technique for using XML and HTTP to edit content," where Cover explains "edit" to mean "ready, write, modify, delete" or HTTP GET, POST, PUT, DELETE operations.

Those who are interested in syndicating and managing collections of content will find Atom both interesting and challenging. It's not yet even reached draft recommendation status (nor is it completely clear if it will be an IETF, W3C, or joint specification effort). There are, however, some useful documents available for those interested in learning more:

Cover's article (cited in the first paragraph here) includes more pointers and information, and is updated regularly (last touched on May 5, 2004).


Ed Tittel is a writer, trainer, and consultant based in Austin, TX, who writes and teaches on XML and related vocabularies and applications. E-mail Ed at etittel@lanw.com.


This was first published in June 2004

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.