OPML: Difference between revisions
Jump to navigation
Jump to search
(Ghastly memories are coming back) |
(RFC 822 (and not even that!) vs. ISO 8601) |
||
| Line 11: | Line 11: | ||
* Instacast | * Instacast | ||
* ''to be expanded'' | * ''to be expanded'' | ||
== Issues == | |||
OPML uses RFC 822 dates. The spec notes: | |||
: All date-times conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred). | |||
RFC 822 dates are less than ideal compared to [[ISO 8601]]. | |||
== See also == | == See also == | ||
* [[xoxo-opml-issues]] lists issues with OPML, documents the intricacies of the format and describes potential interoperability with [[xoxo]] | * [[xoxo-opml-issues]] lists issues with OPML, documents the intricacies of the format and describes potential interoperability with [[xoxo]] | ||
* [[List of XML-based formats]] | * [[List of XML-based formats]] | ||
Latest revision as of 16:57, 23 July 2014
OPML is an XML-based file format for representing hierarchical outlines, and is used most commonly for allowing transfer of lists of RSS subscriptions from a feed reader or from a podcast consuming client.
History
OPML was created by UserLand Software to store and share outlines, hierarchical text documents where child data could be hidden or expanded.
Subscription list / podcast list
Software that supports OPML export:
- iTunes — SuperUser question
- Instacast
- to be expanded
Issues
OPML uses RFC 822 dates. The spec notes:
- All date-times conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred).
RFC 822 dates are less than ideal compared to ISO 8601.
See also
- xoxo-opml-issues lists issues with OPML, documents the intricacies of the format and describes potential interoperability with xoxo
- List of XML-based formats