Or perhaps having at six year head start (RSS 0.90, 1999; Atom, 2005) and having it compound.
This includes podcasting, as the term was coined in 2004, but which was happening even before that (and before Atom was finalized):
* https://en.wikipedia.org/wiki/Podcast#Etymology
First mover advantage, leading to network effects, can be a thing.
CDATA > CDATA in XML: https://en.m.wikipedia.org/wiki/CDATA#CDATA_sections_in_XML
IIRC RSS was not originally an XML document, so CDATA tags (to prevent XSS) didn't work; and the issue remains with content syndication: feed elements should somehow HTML escape their content to prevent XSS (arbitrary JS on a different Origin)
AFAIK RDF Site Summary (the original meaning of "RSS") used XML from the start¹. You may be thinking of spiritual predecessors like the Apple-developed MCF².
¹ https://www.rssboard.org/rss-0-9-0 ² https://en.wikipedia.org/wiki/History_of_web_syndication_tec...
I was working on a standards committee for years and made the discovery that you can turn most XML Schema Definitions into an OWL ontologies and thus automatically transform conforming XML documents into RDF documents.
(People had attempted this before but all the systems I saw were lossy or didn't make valid and decidable ontologies.)
For better and worse my write up[ is about to become one of those ISO standard documents that costs 166 swiss franc but it looks like I'll get the opportunity to apply this method to a major financial standard and release the software that does it as open source.
I'd contrast that to the truly awful RDF/XML spec where people never really understood where the XML stopped and the RDF began. It turned a lot of people off to RDF and people never got to see how easy it is with Turtle. Unfortunately JSON-LD hasn't got the love it deserves because it fixes most of the major problems with JSONs except for the lack of /* comments */ and you can frequently add a touch of JSON-LD to a JSON document you find on the street and get instant RDF you can query w/ SPARQL.
It looks like the W3C has started the process of a SPARQL 1.2 spec which could be a very good thing if it catches up with what is possible w/ document database query languages like N1QL, AQL and such.
What does it mean to have caught on or not, though? How many RSS, XMP, ActivityPub implementations are actually considering things as triples and not just considering parent-child relationships within the XML tree?
Note that it's an XML file with <channel> elements, which contain <item> elements, which contain <title>, <link>, and <description> elements. Pretty familiar, no?
Dave famously introduced the <enclosure> element in 2001. This has made a lot of people very happy and has been widely regarded as a good move. http://backend.userland.com/rss092
With that app, at least, I don't remember trying to just include RSS feed elements in HTML4 or XHTML; that app tried to parse the RSS and failed, it wasn't copying the feed elements without escaping href=javascript: links etc.
EDIT on 'podcast':
I was literally wondering this AM where 'pod'cast came from - thank you for the link (I love in-sects, which is why I love Etymology!)
I don't follow. Out there in the world, RSS feeds provide their feeds in Atom format. The technical format is called "Atom" and the functionality that the Atom format implements is called "RSS".
In what sense did technically-correct Atom get trumped by anything? This is like complaining that social factors caused "the SAT" to get trumped by "standardized testing".
Your confusion probably comes from the fact that RSS is older, so it's sometimes used as the name of the functionality but it's improper. They're 2 different formats.
There are feed formats named "RSS". There is a feed format named "Atom". And there is a concept named "RSS". The RSS formats, like the Atom format, are all implementations of the RSS concept. Generally, when you subscribe to an RSS feed somewhere, it will be in the Atom format. It's still called an "RSS feed" for the simple reason that that is the name of the concept.
> it's sometimes used as the name of the functionality but it's improper.
No it isn't. What would you gain by insisting that RSS feeds delivered via Atom have to be called something different than RSS feeds delivered in legacy formats? Did we rename TLS when we updated the cipher suites?
Why, in your opinion, is rssboard.org even bothering to write about Atom?
The concept is called a (web/news) feed:
* https://en.wikipedia.org/wiki/Web_feed
> It's still called an "RSS feed" for the simple reason that that is the name of the concept.
No, it's because "RSS" is acting as an adjective to the noun of "feed". See also "Atom feed": Atom being the adjective, feed being the noun (concept).
> RSS (RDF Site Summary or Really Simple Syndication)[2] is a web feed[3] that […]
Instead I'd say that Atom feeds and RSS feeds are each an implementation of the syndication concept.
I just checked a few of the ones I follow, and ... turns out I don't immediately know how to distinguish when there's not a specific xml namespace reference in the doc or such.
But according to Wikipedia the RFC822 timestamps I'm seeing suggest they're RSS2 instead of Atom?
Atom feeds will almost always have <feed xmlns="http://www.w3.org/2005/Atom"> as the root element. In some cases they may use namespace prefixes but that tends to be rarer and less interoperable.
RSS feeds have an <rss version="2.0"> root element.
If you have a preference, use it and feed readers will likely just work.
RSS 1.0 was basically the first attempt to produce something like Atom without reinventing too much, but Dave threw his toys out of the pram, so the only option was to reinvent it with a different name and clean up the remaining sharp corners.
It's tragically funny. Atom is both more correct and easier to produce and parse than any RSS variant.
Were I to join Automattic in the morning, the first thing I'd try is to attempt to get them to abandon their weird RSS mashup as their default feed format. There's no good reason why Wordpress still generates RSS feeds.
Yes, I'm a bit bitter, but I was in the feed wars, and it still stings.
I wouldn't call it a weird mashup for WordPress to use atom:link in their RSS feeds. It does things no RSS element can do, such as allow a feed to identify its own URL.
For those who don't know, every WordPress site with an RSS feed also has an Atom feed available by adding "/atom" to the end of the RSS feed URL, such as this:
RSS feed: https://wordpress.com/blog/feed/
Atom feed: https://wordpress.com/blog/feed/atom/
Interestingly enough you can’t to do the reverse: because RSS never got a proper XML namespace, its elements can’t be embedded into other XML. I can understand that the early RSS 0.9x efforts didn’t do XML namespaces since those were rather new then, but the publication of RSS 2.0 could have been the right moment to introduce one, I think.
The advantage is that the imported Atom bits will be namespaced, so an old client can decide to ignore them and just treat the feed as RSS.
In format wars, wider compatibility tends to win, even if the overall standard is just worse. Developers are lazy.
DonHopkins on May 11, 2014 | parent | context | favorite | on: The Unix Haters Handbook (1994) [pdf]
[...]
The worst use of the <BLINK> tag ever was the discussion held in the early days of RSS about escaping HTML in titles, whose attention-grabbing title went something like this: "Hey, what happens when you put a <BLINK> tag in the title???!!!"
The content of that notorious discussion went on and off and on and off for weeks, giving all the netizens of the RSS community blogosphere terrible headaches, with people's entire blogs disappearing and reappearing every second, until it finally reached a flashing point, when Dave Winer humbly conceded that it wasn't the user's fault for being an idiot, and maybe just maybe there was tiny teeny little design flaw in RSS, and it wasn't actually such a great idea to allow HTML tags in RSS titles.
Meanwhile Dave added enclosures and popularized podcasting making RSS even more important. He knew where to focus and what mattered.
The person who pushed RSS to success (IMO) Dave Winer was superb at communicating and evangelizing his goals, connecting partners like Netscape and NYT, and documenting his work including the RSS related tools he built.
His spec was “worse” in the sense that it was under specified but better in the sense that it achieved wide support (both in text and podcast form) among people who made content. This is partly because Dave had first an influential email newsletter and Wired column (DaveNet) and second an influential very early blog Scripting News. He had also been working with news companies for years at prior startups. He could write well. He showed up for and arranged meetings with people who did not at first understand the need for something like rss. He was clear and relentless in his promotion which was borne out of what seemed to be a genuine desire for open standards in this area rather than greed / trying to do lock in.
People with technical backgrounds in places like this tend to fixate on the technical aspects of Atom vs RSS. There is no question Atom is more technically correct. There is also no question (IMO) it came too late and focused on the wrong things — being correct and complete at the expense of being complicated and hard to understand — and more importantly was led and promoted by people who lacked the social skills to make it popular outside of technical circles. (These folks could be brutal about rss's flaws without seeming to have awareness of this shortcoming in their own effort.)