C:\My Download Files\xml2rfc-1.21>java com.icl.saxon.StyleSheet draft-obasanjo-feed-URI-scheme-02.xml rfc2629.xslt The feed URI scheme (PRE-DRAFT)
 RFC 
 TOC 
Network Working Group  D. Obasanjo 
INTERNET DRAFT  December 2003 
<draft-obasanjo-feed-URI-scheme-02>    
Category: Standards Track   
Expires: June 2004   

The feed URI scheme (PRE-DRAFT)
draft-obasanjo-feed-URI-scheme-02

Status of this Memo

This draft HAS NOT been submitted for publication, and does not have any status; it should be referred to as a "pre-draft."

Discussion of this draft happens on the Information Aggregators mailing list. It should be noted that this list is invitation only and is a forum for developers of news aggregators which consume RSS and/or ATOM feeds.

If you are not a member of the aformentioned mailing list but would like to provide feedback please contact the author of this specification directly via email.

Copyright Notice

Copyright (C) Dare Obasanjo (2003). All Rights Reserved.

Abstract

This document specifies the "feed" URI (Uniform Resource Identifier) scheme for identifying data feeds used for syndicating news or other content from an information source such as a weblog or news website. In practice, such data feeds will most likely be XML documents containing a series of news items representing updated information from a particular news source.


 RFC 
 TOC 

Table of Contents

Introduction
 1.1  Requirements notation
The "feed" URI Syntax
Examples
Intended Usage
Security Considerations
§  References
§  Author's Address


 TOC 

1  Introduction

The "feed" URI scheme is used to identify network retrievable resources that contain information syndicated from one or more news sources. As of this writing the most popular way to represent a syndication feed is through the use of an XML based file format such as [RSS0.91], [RSS1.0] or [RSS2.0]. The "feed" URI scheme is not limited to identifying the aforementioned XML-based file formats but can and should be used to identify other network retrievable resources used to syndicate information from a particular news source.

1.1  Requirements notation

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].


 TOC 

2  The "feed" URI Syntax

The feed URI syntax is primarily dependent on the scheme used to retrieve the data feed over the network. In general, a "feed" URI is written as follows

feedURI = 'feed:' absoluteURI | 'feed://' hier_part

the syntax for the 'absoluteURI' and 'hier_part' are defined in section 3 of [RFC2396]. A "feed" URI is basically the string 'feed:' or 'feed://' followed by a URI which when accessed over the network returns a representation of the data feed. If the "feed" URI string begins with the string 'feed://' then it MUST be followed by an authority with optional path and query string with the scheme for the URI for accessing the data feed being inferred as the "http" scheme. If the "feed" URI string begins with the string 'feed:' then it must be followed by an absolute URI which is the network accessible location of the data feed.

The "feed" URI scheme has no relative URI forms.


 TOC 

3  Examples

The following are examples of the "feed" URI scheme

feed:http://example.com/rss.xml   - Identifies the RSS feed at 'http://example.com/rss.xml'  
feed:https://example.com/rss.xml   - Identifies the RSS feed at 'https://example.com/rss.xml'  
feed://example.com/rss.xml   - Identifies the RSS feed at 'http://example.com/rss.xml'  

 TOC 

4  Intended Usage

The primary purpose of "feed" URIs is to provide a straightforward way for end users to subscribe to the data feed for a particular online resource while browsing the World Wide Web. The expectation is that clicking on a hyperlink that points at a "feed" URI will cause the Web browser to invoke the specified handler for the "feed" URI scheme which SHOULD provide the user with information about the data feed as well as the possess the ability to subscribe to the feed.


 TOC 

5  Security Considerations

None.


 TOC 

References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2396] Berners-Lee, T., Fielding, R. and Masinter, L., "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RSS0.91] Winer, D., "RSS 0.91", RSS 0.91, June 2000.
[RSS1.0] Swartz, A., MacLeod, K., Dodds, L., Guha, R.V., van der Vlist, E., Brickley, D., Dornfest, R., Eisenzopf, J. and Miller, E., "RDF Site Summary (RSS) 1.0", RSS 1.0, December 2000.
[RSS2.0] Winer, D., "RSS 2.0", RSS 2.0, September 2002.

 TOC 

Author's Address

  Dare Obasanjo
 
EMail:  kpako@yahoo.com
URI:  http://www.25hoursaday.com