Standard format specifications, French translation by Denis Surot, posted on .fr.
RDF Site Summary (RSS) - metadata description and easy universal extensible syndication format. RSS is an XML application that complies with the W3C RDF specifications and is extensible using XML namespaces and/or RDF-based modularization.
RSS-DEV Working Group Members:
Latest original English version: https://web.resource.org/rss/1.0/spec
1.3.4 2001-05-30 corrected a minor error in section 5.3.6.
1.3.3 2001-03-20 mime-type updated and URI.
1.3.2 2000-12-19 (model change and markup reduction; author of reviews: SBP)
1.3.1 2000-12-17 (corrected error: recommended upper limit of 15 articles per PCC document, not entered [5.5].
1.3 2000-12-09
Comments should be sent to the RSS-DEV mailing list archived on the http://www.egroups.com/messages/rss-dev.
Copyright 2000 by authors.
This allows you to use, copy, modify and distribute the RDF Site Summary 1.0 specifications and supporting documentation for any use and without payment rights, provided that the copyright notice above and this paragraph are contained in all copies. Copyright owners do not give any guarantees about the suitability of the specifications for any purpose. It is provided "as is" without express or implied warranty.
This copyright applies to the RDF Site Summary 1.0 specifications and supporting documentation and does not apply to the RSS format itself.
RDF Site Summary (RSS) - metadata description and easy universal extensible syndication format. RSS is an XML application that complies with the RDF W3C specifications. RSS is extended using XML namespace and/or RDF-based modularity.
An RSS summary is, at a minimum, a document describing a "feed" consisting of items whose URL can be found. Each article consists of a title, a link, and a brief description. Despite the fact that articles are traditionally news headlines, the RSS was often reassigned to its short existence. For an overview of RSS 1.0 documents, see Examples below.
RSS 0.9 was introduced in 1999 by Netscape as a framework/content collection mechanism with a channel description for their My Network Network (MNN) portal. By providing a snapshot in a simple document, site manufacturers acquired an audience with their content on My Netscape .
A byproduct of MNN's work was the use of RSS as a lightweight XML-based syndication format, quickly becoming a real alternative to special syndication systems and practicality in many scenarios where heavyweight standards such as ICE were overrepresented. And the usage didn't stop with title syndication; RSS feeds today transmit a group of content types: news headlines, discussion forums, program announcements, and various types of proprietary data.
RSS 0.91, echoing as "Rich Site Summary," soon followed on the heels of 0.9. He summed up his RDF roots and brought new elements to Userland's scriptingNews format - the most notable of which was the new <description> element at the article level, which puts RSS in the content syndication arena (lightweight).
While Netscape was interrupting his efforts towards RSS, the evangelism of Dave Wiener of Userland's led to a significant wave of adoption of RSS as a basis for syndication. The inclusion of RSS 0.91 as a syndication format for its Manila product and service in EditThisPage.com regard combined the worlds of weblog and syndication.
While RSS continues to be repurposed, aggregated, and categorized, there is a growing need for an increased metadata environment. Channel-level and part-level header and description elements are overloaded with metadata and HTML. Some even publishers inserted unofficial specialized elements (e.g. "category," "date," "author") to try to augment disparate metadata features from the RSS.
The proposed solution is to add more simple elements to the RSS kernel. This direction is probably the easiest in the short term, sacrificing extensibility and requiring repeated format changes, adding what is required and removing unused features. For a more specific representation of the use of elements, see Jan Davies' RSS survey (25-7-2000).
The second solution, and it has been made here, is to separate specific functions in the modules added to the RSS. This is one approach used in this specification: modularity is achieved by using XML namespaces to break up vocabulary. Adding and removing a function from the RSS is simply a matter of including a specific set of modules that are more suitable for the current task. Retouching of the RSS kernel is no longer required.
Advanced RSS applications require a richer representation of the relationship between in-channel and inter-channel elements (e.g., discussions over wires). The Resource Descriptive Framework (RDF) accurately provides a frame for such a rich metadata model. RSS 0.9 laid the groundwork (albeit limited) for the new structure.
The goal in the RSS 1.0 design is to describe metadata and a lightweight, universal, extensible XML-based syndication format. Uplink compatibility with RSS 0.9 is the goal of simply accepting existing syndicated content producers.
Much of the success of RSS comes from the fact that it is simply an XML document rather than a complete syndication structure such as XMLNews or ICE .
The following is an example of a basic RSS 1.0 document that uses only all elements of the RSS 1.0 kernel.
<?xml version="1.0"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns="http://purl.org/rss/1.0/"
>
<channel rdf:about="http://www.example.com/xml/news.rss">
<title>iqlevsha.ru</title>
<link>https://iqlevsha.ru/pub</link>
<description>
iqlevsha.ru propose un ensemble d'informations pour la communauté XML.
</description>
<image rdf:resource="http://example.com/universal/images/xml_tiny.gif" />
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://example.com/pub/2000/08/09/xslt/xslt.html" />
<rdf:li rdf:resource="http://example.com/pub/2000/08/09/rdfdb/index.html" />
</rdf:Seq>
</items>
</channel>
<image rdf:about="http://example.com/universal/images/xml_tiny.gif">
<title>example.com</title>
<link>http://www.example.com</link>
<url>http://example.com/universal/images/xml_tiny.gif</url>
</image>
<item rdf:about="http://example.com/pub/2000/08/09/xslt/xslt.html">
<title>Traiter les inclusion avec XSLT</title>
<link>http://example.com/pub/2000/08/09/xslt/xslt.html</link>
<description>
Traiter l'inclusion de documents avec les outils XML généraux peut
être problématique. Cet article propose un moyen de préserver
l'inclusion de l'information par un traitement fondé sur SAX.
</description>
</item>
<item rdf:about="http://example.com/pub/2000/08/09/rdfdb/index.html">
<title>Mettren en oeuvre RDF</title>
<link>http://example.com/pub/2000/08/09/rdfdb/index.html</link>
<description>
Le support d'outils et API pour Resource Description Framework
devient peu à peu mature. Edd Dumbill considère RDFDB,
une des plus intéressante nouvelle boite à outils RDF.
</description>
</item>
</rdf:RDF>
Within 12 months of version 0.91, there were various new ways to use RSS. RSS is designed to evolve with the growing needs of applications: aggregation, discussion wires, job listings, houses for sale (multiple registration services), sports scores, document catalogs, etc. Through modularity based on XML and RDF namespaces, RSS 1.0 establishes both standardized and tailored to specialized applications.
The key difference between RSS version 1.0 and earlier (or derivative) lies in its extensibility through XML compliance with the namespace and RDF (Resource Descent Framework or resource description frame).
Namespace-based modules provide separate extensibility. This allows you to extend the RSS:
RSS modules are described in more detail in the Modules section below.
Metadata is data data. Even if there is a shortage of information circulating on the Web, it has little description of itself. The W3C metadata progress report states the following:
"The possible use of the Web seems endless, but the technology lacks a key part. What is missing is the part of the Web that contains information about information - labeling, cataloging, and descriptive information structured to allow web pages to be searched and processed correctly, especially on a computer."
RDF takes into account the presentation of detailed metadata reports beyond what is possible in earlier unstructured RSS. The existing RDF base in RSS 0.9 became the reason for choosing to build on earlier versions of RSS; attempting to reintroduce RDF in RSS version 0.91 turned out to be a "return toothpaste to tube" type proposal.
Syndication here is defined as making data available online to find and transmit later, aggregation, or online publishing. Details of various difficulties of syndication systems (free by subscription, "push-ups," push against "sweaters," pull, etc.) go beyond this specification.
The RSS 1.0 kernel is based on RSS 0.9. RSS 1.0 focuses on expanding XML and RDF namespaces while maintaining uplink compatibility.
Uplink compatibility with RSS 0.9
Uplink compatibility depends on the statement and condition that the main persons, modules and RSS libraries do not know that they were not intended to be understood:
Attributes; RSS 0.9 has no attributes outside of RDF namespace declarations.
Modular extension elements are outside the default namespace.
Ad hoc elements that do not affect the overall structure of the RSS 0.9 document.
Extend with XML namespace-based modularity
RSS 1.0 is extended by namespace-based modules. While expansion on an ad hoc basis is certainly encouraged, it is hoped that a basic set of approved modules will emerge, covering functions such as taxonomy, aggregation, Dublin core, etc. See the modules section below, as well as the RSS 1.0 kernel modules registry.
The restriction is imposed on the sub-elements of the channel, images, products and the upper elements of the text <textinput> [, 5.3 <channel> 5.4 <image>, 5.5 <item>, 5.6], that is, these elements may not contain repeating sub-elements (for example ,<item><dc:sujet/><dc:sujet/></item>). This sentence applies only to immediate sub-elements. For large depths (repeating elements of rich content), this is already well defined in the RDF syntax.
BROADCASTING FRANCE
RSS 1.0 builds on the RDF framework that appears in RSS 0.9 (and played with RSS 0.91) through the following minimal additions :
rdf: about attribute 5.3, 5.4, 5.5, 5.6].To maximize support for RDF and RSS 1.0 representations in pure XML, RSS 1.0 recognizes only the use of RDF element syntax in kernel elements.
Mime type
The current mime type recommendation for an RSS 1.0 document is application/xml. However, work is underway to write a mime type for RDF (and probably RSS). After registration, you must use the RDF mime type (or, preferably, RSS).
File extension
The file extension for the RSS 1.0 document is not required. RDF or .xml recommended, with the former preferred.
Coding
While RSS 0.9 only recognized ASCII encoding, RSS 1.0 enforces UTF-8. Using US-ASCII (i.e. encoding all code characters greater than 127 as & # nnn;) matches the UTF-8 encoding (and ISO-8859-1 the default HTTP header encoding).
URL addresses
As a measure to ensure uplink compatibility with RSS 0.9, only the following schemes are allowed in URL reference elements: http:, https:, ftp:. mailto: only valid in textinput reference element.
Organizations:
XML will reserve some characters for markup. To include the latter in an RSS document, they must be replaced with an object reference:
< becomes & lt;> becomes & gt; & becomes & The next two object references are also defined by XML mapping parsers. Although their use is common, it is not mandatory. However, they are required when including quotation marks in a string using the same character; for example, "" hello, "" she said that "should be coded as" & quot; Hi, & quot; She said."
'becomes & apos;
"becomes & quot; Note: Since RSS 1.0 does not require a DTD, make sure it includes built-in declarations of objects used in addition to the five listed above. The following DTD fragments are very useful as a source of HTML compatible entities.
Example of use:
<?xml version="1.0"?> <!DOCTYPE rdf:RDF [ <!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent"> %HTMLlat1; ]> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" > ...
Content length:
While RSS 1.0 leaves the choice of content length for items such as title, link, and description if it is acceptable to the application, the maximum length of the RSS 0.9 "s character is outdated in favor of the proposed good practice status, in order to strictly adhere to uplink compatibility.
Rating:
The following kernel element descriptions use the following notation:
{quelque chose}- is just a container for URI, value, etc. + means "at least one instance" of this element or attribute. * signifie Zero instances of this element or attribute are allowed. As an XML application, an RSS document does not have to start with an XML declaration. As a best practice and to ensure further upstream compatibility with RSS 0.9 (this was required by specification 0.9), this specification recommends doing so.
Syntax: <? xml version = "1.0"?>
Condition: Optional (except for encoding)
The widest RDF element in each RSS 1.0 document. The public RDF tag associates the rdf: namespace with the RDF syntax schema and sets the RSS 1.0 schema as the default namespace for the document.
While any valid namespace prefix can be used, document creators are advised to consider "rdf:" normative. Those wishing to be strictly compatible with RSS 0.9 must use "rdf:."
Синтаксис: <rdf: RDF: xmlns: rdf =» http://www.w3.org/1999/02/22-rdf-syntax-ns #» xmlns = «http://purl.org/rss/1.0/»>
Condition: Required exactly, except for additional namespace declarations.
Model: (channel, picture?, element +, textinput?)
The channel element contains metadata describing the channel itself, including the title, short description and URL link of the resource described (the home page of the channel provider, in this case). The URL {resource} of the rdf: about attribute of the channel element must be unique with respect to all other rdf: about attributes in the document and is a URI identifying the channel. This is usually either the URL of the described home page or the URL where you can find the RSS file .
Syntax: <rdf channel: about = "{resource}">
Condition: Required.
Required attributes: rdf: about
Model: (title, link, description, image?, objects, textpoint?)
Example:
<channel rdf:about="http://www.example.com/xml/news.rss">
<title>example.com</title>
<link>http://example.com/pub</link>
<description>
example.com propose un ensemble d'informations pour la communauté XML.
</description>
<image rdf:resource="http://example.com/universal/images/xml_tiny.gif" />
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://example.com/pub/2000/08/09/xslt/xslt.html" />
<rdf:li rdf:resource="http://example.com/pub/2000/08/09/rdfdb/index.html" />
</rdf:Seq>
</items>
<textinput rdf:resource="http://search.example.com" />
</channel>
Descriptive name of the channel .
Syntax: <title> {channel_title} </title>
Condition: Required
Model: (# PCDATA)
(Suggested) Maximum length: 40 (characters)
The URL to which the HTML rendering of the feed name binds is usually the home page of the parent site or the news page.
Syntax: <link> {channel_link} </link>
Condition: Required
Model: (# PCDATA)
Maximum length: 500
Brief description of the contents of the channel, function, source, etc .
Syntax: <description> {channel_description} </description>
Condition: Required
Model: (# PCDATA)
Maximum length: 500
Establishes an RDF link between an optional pixel [5.4] and that particular RSS feed. Rdf: resource {image_uri} must be the same as rdf: about for image element {image_uri}.
Syntax: <image rdf: resource = "{image _ uri} "/>
Condition: Required only if there is an image element.
Model: Empty
The RDF Table of Contents linking the elements of the [5.5] document to this particular RSS Feed. Rdf: The resource for each {item_uri} article must be identical to the rdf: about for the related {item_uri} element.
The RDF Seq is used to place all elements rather than the RDF Bag to specify the order of the elements for rendering and reconstruction.
Note that items that appear in the document but are not members of the channel-level item sequence may be rejected by RDF counters.
Syntax: <items> <rdf: Seq> <rdf: li resource = "{item _ uri} "/>... </rdf: Seq> </items>
Condition: Required
Establishes an RDF association between the optional textpoint [5.6] and this particular RSS feed. {Rdf: resource textinput_uri} must be identical to rdf: about for the textpoint {textinput_uri}.
Syntax: <textinput: rdf: resource = "{textinput _ uri} "/>
Condition: Only required if textual input is available
Model: Empty
Image for rendering HTML feed. This image must be a format recognized by most web browsers. While specifications 0.91 and subsequent ones allow a width of 1-144 and a height of 1-400, the convention (and specifications 0.9) imposes 88x31.
Syntax: <rdf image: about = "{image _ uri}">
Condition: Optional; if present, must also be present in the channel element [5.3.4]
Required attributes: rdf: about
Model: (title, url, link)
Example:
<image rdf:about="http://example.com/universal/images/xml_tiny.gif">
<title>example.com</title>
<link>http://www.example.com</link>
<url>http://example.com/universal/images/xml_tiny.gif</url>
</image>
Alternative text ("alt" attribute) associated with the channel image tag in HTML rendering.
Syntax: <title> {text_alt_image} </title>
Condition: Required if an image element is present
Model: (# PCDATA)
Maximum length: 40
The URL of the image used in the "src" attribute of the channel image tag when rendered in HTML.
Syntax: <url> {url_image} </url>
Condition: Required if an image element is present
Model: (# PCDATA)
Maximum length: 500
The URL to which HTML rendering of the feed image binds. This, as with the link to the channel title, is usually a homepage or news page.
Syntax: <link> {lien_image} </link>
Condition: Required if an image element is present
Model: (# PCDATA)
Participant: Image
Maximum length: 500
Although this is usually a new name, with modular RSS 1.0 extensibility, it can actually be used for anything: a discussion ticket, a worksheet, software - any object with a URI. An RSS document accounts for at least one point. Although RSS 1.0 does not set an upper limit, a maximum of fifteen articles are recommended for uplink compatibility with RSS 0.9 and 0.91.
{item_uri} must be unique to any other rdf: about attribute of the RSS document, and it is the URI that identifies the article. {item_uri} must be identical to the value of the <link> subelement of the <item> element, if possible .
Syntax: <item rdf: about = "{item _ uri}">
Condition:> = 1
Recommendation (for uplink compatibility with 0.9x): 1-15
Required attributes: rdf: about
Model: (title, url, link?)
Example:
<item rdf:about="http://example.com/pub/2000/08/09/xslt/xslt.html">
<title>Traiter les inclusions avec XSLT</title>
<link>http://example.com/pub/2000/08/09/xslt/xslt.html</link>
<description>
Traiter l'inclusion de documents avec les outils XML généraux peut
être problématique. Cet article propose un moyen de préserver
l'inclusion de l'information par un traitement fondé sur SAX.
</description>
</item>
Article title.
Syntax: <title> {item_title} </title>
Condition: Required
Model: (# PCDATA)
Maximum length: 100
Article URL.
Syntax: <link> {item_link} </link>
Condition: Required
Model: (# PCDATA)
Maximum length: 500
Brief description/summary of the article .
Syntax: <description> {item_description} </description>
Condition: Optional
Model: (# PCDATA)
Maximum length: 500
The textinput element offers a method to transfer form data to an arbitrary URL - usually hosted on a parent website. It is assumed that only the form handler on the receive side supports the GET method for HTTP.
The field is usually used as a search field or subscription form - among other things. Even if it has some utility when RSS documents are translated as channels (see MNN) and accompanied by a human-readable title and description, ambiguity in automatically determining the meaning of this overloaded element does not make it particularly useful otherwise. Thus, RSS 1.0 assumes that it is deprecated or that this element is incremented by any form of resource retrieval in future versions, preserving it for uplink compatibility with RSS 0.9.
{textinput_uri} must be unique to any other rdf: about attribute in the RSS document and must be a URI that defines a text input. {textinput_uri} must be identical to the value of the <link> subelement of the <textinput> element, if possible.
Syntax: <textinput rdf: about = "{textinput _ uri} ">
Condition: Optional; if present, must also be present in the channel element [5.3.6]
Required attributes: rdf: about
Model: (title, description, name, reference)
Example:
<textinput rdf:about="http://search.example.com">
<title>Rechercher sur example.com</title>
<description>Chercher dans la collection XML de example.com</description>
<name>s</name>
<link>http://search.example.com</link>
</textinput>
Descriptive name of the text field. For example: "Subscription" or "Search !"
Syntax: <title> {textinput_title} </title>
Description: Textinput Header
Condition: Mandatory if textinput
Model: (# PCDATA)
(Suggested) Maximum length: 40
Brief description of the purpose of the text-path field. For example: "Subscribe to our newsletter for..." or "Search our site archive..."
Syntax: <description> {textinput_description} </description>
Condition: Mandatory if textinput
Model: (# PCDATA)
Maximum length: 100
Name (variable) of the input text field.
Syntax: <name> {textinput_varname} </name>
Condition: Mandatory if textinput
Model: (# PCDATA)
Maximum length: 500
The URL to which the text path will be sent (using GET).
Syntax: <link> {textinput_action_url} </link>
Description: Textuple Action URL
Condition: Mandatory if textinput
Model: (# PCDATA)
Maximum length: 500
Namespace-based modularity provides separate extensibility for RSS 1.0.
The only modules that ship "boxed" with RSS 1.0 are the Dublin core and syndication. Refer to the appropriate module documentation for more information.
Refer to RSS 1.0 Modules for instructions on creating a module and stored RSS 1.0 kernel modules.
A few examples of using the module can be found in the Examples section below .
A basic RSS 1.0 document (style 0.9) that uses only the RSS 1.0 kernel element set.
<?xml version="1.0"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns="http://purl.org/rss/1.0/"
>
<channel rdf:about="http://www.example.com/xml/news.rss">
<title>example.com</title>
<link>http://example.com/pub</link>
<description>
example.com propose un ensemble d'informations pour la communauté XML.
</description>
<image rdf:resource="http://example.com/universal/images/xml_tiny.gif" />
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://example.com/pub/2000/08/09/xslt/xslt.html" />
<rdf:li rdf:resource="http://example.com/pub/2000/08/09/rdfdb/index.html" />
</rdf:Seq>
</items>
<textinput rdf:resource="http://search.example.com" />
</channel>
<image rdf:about="http://example.com/universal/images/xml_tiny.gif">
<title>example.com</title>
<link>http://www.example.com</link>
<url>http://example.com/universal/images/xml_tiny.gif</url>
</image>
<item rdf:about="http://example.com/pub/2000/08/09/xslt/xslt.html">
<title>Traiter les inclusions avec XSLT</title>
<link>http://example.com/pub/2000/08/09/xslt/xslt.html</link>
<description>
Traiter l'inclusion de documents avec les outils XML généraux peut
être problématique. Cet article propose un moyen de préserver
l'inclusion de l'information par un traitement fondé sur SAX.
</description>
</item>
<item rdf:about="http://example.com/pub/2000/08/09/rdfdb/index.html">
<title>Mettre ne oeuvre RDF</title>
<link>http://example.com/pub/2000/08/09/rdfdb/index.html</link>
<description>
Le support d'outils et API pour Resource Description Framework
devient peu à peu mature. Edd Dumbill considère RDFDB,
une des plus intéressante nouvelle boite à outils RDF.
</description>
</item>
<textinput rdf:about="http://search.example.com">
<title>Rechercher sur example.com</title>
<description>Chercher dans la collection XML de example.com</description>
<name>s</name>
<link>http://search.example.com</link>
</textinput>
</rdf:RDF>
An RSS 1.0 document that uses elements of different modules (underlined in different colors). Note: The modules in this example are for illustration purposes only; For module information, see RSS 1.0 Modules.
<?xml version="1.0" encoding="utf-8"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:co="http://purl.org/rss/1.0/modules/company/" xmlns:ti="http://purl.org/rss/1.0/modules/textinput/" xmlns="http://purl.org/rss/1.0/" > <channel rdf:about="http://meerkat.oreillynet.com/?_fl=rss1.0"> <title>Meerkat</title> <link>http://meerkat.oreillynet.com</link> <description>Meerkat: Un service Open Wire</description> <dc:publisher>The O'Reilly Network</dc:publisher> <dc:creator>Rael Dornfest (mailto:rael@oreilly.com)</dc:creator> <dc:rights>Copyright © 2000 O'Reilly & Associates, Inc.</dc:rights> <dc:date>2000-01-01T12:00+00:00</dc:date> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>2</sy:updateFrequency> <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase> <image rdf:resource="http://meerkat.oreillynet.com/icons/meerkat-powered.jpg" /> <items> <rdf:Seq> <rdf:li resource="http://c.moreover.com/click/here.pl?r123" /> </rdf:Seq> </items> <textinput rdf:resource="http://meerkat.oreillynet.com" /> </channel> <image rdf:about="http://meerkat.oreillynet.com/icons/meerkat-powered.jpg"> <title>Meerkat Powered!</title> <url>http://meerkat.oreillynet.com/icons/meerkat-powered.jpg</url> <link>http://meerkat.oreillynet.com</link> </image> <item rdf:about="http://c.moreover.com/click/here.pl?r123"> <title>XML: Une technologie de rupture</title> <link>http://c.moreover.com/click/here.pl?r123</link> <dc:description> XML provoque une augmentation constante du poids des transferts sur l'infrastructure technique actuelle d'Internet. </dc:description> <dc:publisher>The O'Reilly Network</dc:publisher> <dc:creator>Simon St.Laurent (mailto:simonstl@simonstl.com)</dc:creator> <dc:rights>Copyright © 2000 O'Reilly & Associates, Inc.</dc:rights> <dc:subject>XML</dc:subject> <co:name>example.com</co:name> <co:market>NASDAQ</co:market> <co:symbol>XML</co:symbol> </item> <textinput rdf:about="http://meerkat.oreillynet.com"> <title>Search Meerkat</title> <description>Rechercher dans la base de données RSS de Meerkat...</description> <name>s</name> <link>http://meerkat.oreillynet.com/</link> <ti:function>search</ti:function> <ti:inputType>regex</ti:inputType> </textinput> </rdf:RDF>