RDF Site Summary 1.0 proposed modules (original) (raw)
RDF Site Summary 1.0 proposed modules and associated documentation.
This module provides administrative properties that can be used to help improve the robustness and reliability of broad RSS usage between providers, aggregators, clients, and other users.
is a URI (typically a 'mailto:' URL) for contacting the person or source of the particular instance of RSS/RDF information. This would generally be used to report technical errors in the use of RSS, RDF, or XML. is a URI of the software that was used to generate the RSS/RDF. This is similar to the User-Agent field in HTTP or the X-Mailer field in email. It can be used to spot and report errors in the generating software and for statistical information. The URI should include version information, and if it is a resolvable URL should return a user-readable HTML page.
Provides aggregator-added information about the original source of the RSS item.
Provides support for resources that annotate, follow-up to, or reference other resources. Examples would include annotation system such as crit, Usenet, and most web-based discussion groups. The module can be used in combination with other modules (e.g. Dublin Core) to provide additional information about resources.
For modules such as mod_mp3 for the Apache server to properly syndicate audio data, additional fields are needed. mod_audio adds those fields that are needed. These fields are based on information supplied by ID3 tags. The mod_audio RSS 1.0 module augments the RSS core and Dublin Core module's metadata with channel and item-level elements specific to audio data.
This module aims to give metadata regarding the copyright license under which the RSS feed, and the objects it points to, are released under. As the name suggests, it originates from the Creative Commons project, but is not restricted to the licenses that they produce. Rather, it is designed to allow for the inclusion of any existing and future licenses, and to provide for the simple description thereof. More details on this can be found on the Creative Commons site, especially the metadata specification page. This module is notable for another reason: it is the first RSS 1.0 module to fully utilise RDF syntax. As you will see, it requires the inclusion of another element at the same level as
and within the document. This should present no problems, but should be noted as historic, and quite cool.
Includes information necessary to subscribe to be notified when this RSS feed updates. Applications should follow the changedPage spec using cp:server as the notifier.
For syndication of news and market data, accompanied by ticker symbol, additional fields are needed. mod_company adds those fields that are needed for identifying the ticker symbol and the associated exchange. The mod_company RSS 1.0 module augments the RSS core and Dublin Core module's metadata with channel and item-level elements specific to company data.
This draft RSS 1.0 module is being released to support applications that wish to make use of the ANSI/NISO Draft Standard for Trial Use 'The OpenURL Framework for Context-Sensitive Services'. It is anticipated that a revised version of this module will be resubmitted following a successful ballot by NISO Voting Members when the Draft Standard is published as currently expected NISO Standard Z39.88-2004.
This module is designed to be allow Qualified Dublin Core metadata to be included in RSS feeds.
This module is designed to be used to represent email headers.
With RSS we have the ability grab news and summaries from other websites and display them on our portals. However, a key property of news is that they describe something that just happened. Therefore the most interesting news are the newest news. Not so with events such as conferences, product launches, training courses etc. Events take place on a certain date in the future, and can be announced years or just a few days in advance. So when we announce them, we need to sort them on the date of the event. because the most interesting events are those that are going to happen in the near future.
The mod_link module supports the syndication of site link information along with RSS 1.0 XML feeds. The W3C HTML link mechanism provides the original inspiration for this module.
The Publishing Requirements for Industry Standard Metadata (PRISM) specification (version 1.2) defines a standard for interoperable content description, interchange, and reuse for electronic serials publications. PRISM recommends the use of certain existing standards, such as XML, RDF, Dublin Core, and various ISO specifications for locations, languages, and date/time formats. Beyond those recommendations, it defines a small number of XML namespaces and controlled vocabularies of values, in order to meet the goals listed above. The RSS 1.0 module 'mod_prism' defines an RSS vocabulary which augments the RSS core and Dublin Core modules with channel- and item-level elements from the basic PRISM vocabulary.
This module defines elements defining properties which are equivalent to the title and description properties defined by the core RSS1.0 Spec, but allowing for the use of xml elements as content.
The RSS091 provides sideways compatibility with RSS 0.91 by providing a modularized version of the elements added to 0.91. Note that RSS 1.0 does indeed provide an item-level description element, borrowed from RSS 0.91 owing to the ubiquity of this one particular element; you'll note that the RSS091 module does, however, still contain its own compartmentalized copy of an item-level description element. For more specifics on RSS 0.91, please refer to the RSS specifications in the Resources section of the RSS 1.0 Specification Proposal.
Provides addional information about items resulting from search engine query results.
This module extends RSS to include elements which allow the description of the status and current availability of services and servers. Some data, such as whether a server is up or not, would normally be generated automatically, whilst other data, such as explanatory text for humans, might be the result of further processing or direct human input. A service as seen from a user's point of view might not be a one-to-one mapping to a service as seen from a system point of view. If, for example, a user service is dependent on more than one system service being available then the user service is available if and only if all those system services are available. This can easily be calculated with both input and output conforming to this specification.
Slash is the source code and database that was originally used to create Slashdot, and has now been released under the GNU General Public License. It is a bona fide Open Source / Free Software project. The Slash RSS 1.0 module augments the RSS core and Dublin Core module's metadata with channel and item-level elements specific to Slash-based sites.
This module addresses the additional needs of streaming-media providers. It is seen as an addition to existing standard and proposed modules, especially Dublin Core. The main features involve the associated application for the media stream, the codec the stream is encoded with and additional tags for the segmentation of live/continual broadcasts. It is predominantly technical/practical information: I envisage information such as music style, video content, contributors and rights-management to be dealt with by Dublin Core etc.
The mod_subscription module supports the syndication of site subscription information along with RSS 1.0 XML feeds.
The taxonomy module is a RSS 1.0 module and a RDF application enabling the identification of topics covered by a RSS channel or item.
Provides the ability for items to specify a parent/child relationship.