Talk:OPML

message: Is there a reason, other than a flipside to the proponents of OPML, that there is a link to troll blog post about OPML? Unless someone can argue for it, I'm going to recommend removing it from the list of external links. DClifton 07:48, 4 March 2006 (UTC)
thread_title: Troll

message: This article seems to violate NPOV and advocate a specific approach to XML design (tags vs. attributes). Attributes are pretty widely used in data-style formats (as opposed to narrative and template doctypes). They are also useful to limit format bloat by restricting a value to simple character data (or other scalar values that may be serialized as such). If RSS had used attributes for titles, for example, the tendency to use inconsistently-encoded HTML titles might have been limited. HTML uses "title" attributes to provide simple character information available only upon request that should not interrupt the normal text flow. There is a rational balance between "elements and attributes.  Brianiac 15:58, 31 May 2006 (UTC)
thread_title: Element versus Attribute

message: Could we get some example applications that use this?  I see google reader exports and imports it.  Mathiastck (talk) 18:57, 20 June 2008 (UTC)
thread_title:  Usage 

message: This is not a rant, but an observation about OPML's limited functionality.  As an end-user, I'd like someone with more technical background to post an observation in the article to explain that OPML was not designed in a way that allows exporting a folder structure.  To my mind, this is what makes OPML a dud.  Once someone accumulates a good number of feeds, it's natural to want to categorize them in a useful way, using folders.  Bookmarks allow folder structures.  Why didn't OPML?  In OPML, the entire folder structure is erased.  End users cannot export their feeds without making their new client into which they're imported a veritable weed garden of feeds.  Very high maintenance to restore the original setup in a new client.  If anyone knows of any elegant workarounds for this problem, I'd be delighted to read about a solution.  At the very least, it would be great to mention this in the article so that future designers of OPML 2.0 will take note.
A.k.a. (talk) 23:17, 14 January 2010 (UTC)
thread_title:  Shortcomings 

message: I'm sorry, I came here to find out what OPML *IS* . This article is zero help in telling me anything about it. Its a markup language for hierarchical data? really? so how is that different from XML?
It appears to be written with the assumption that you already know what it is . I request someone who understands it to explain more clearly what this is, why it is needed, with 100 other markup langs already out there. Thanks !69.255.27.90 (talk) 23:57, 27 July 2010 (UTC)
thread_title:  What is OPML ? 

message: This article is not helpful to people wanting to know what OPML is. I echo immediately above sentiment.  — Preceding unsigned comment added by 216.13.210.98 (talk) 16:05, 25 June 2012 (UTC)
thread_title: Propeller-head Article

message: This document lacks explaining what outlines in its context are. Outlines can mean many things and I failed to find a proper definition of what they are in the context of OPML--Forage (talk) 16:11, 17 March 2013 (UTC)
thread_title:  What are outlines?