Well, I tested both with PaleMoon(a Firefox fork), and they both work well. I know Chrome has some tight security restrictions on applying XSLT-transformation to XML-content. Whyever...
So I try to annotate some differences between the BBC approach and yours:
- Your XML has the
standalone
attribute on its <?xml ...
processing instruction. I don't know if that matters, but the differences of the browsers regarding security restrictions applied to XML-XSLT are tremendous.
- The path of the XSLT given in the
href
of the <?xml-stylesheet type="text/xsl" ...
directive is relative for BBC and absolute for your site. This is very important. BBC has href="/programmes/downloads.xsl"
and you have href="http://fietsrapport.be/gijs/thenetworkeffect.xsl"
. Cross-domain XSLT appliance is often blocked for security reasons. So maybe the URL is not recognized to be on your domain?
- If you have a script blocker like
NoScript
active, it would surely block XML-XSLT-transformation, so you should disable it on your domain.
The rest of the RSS/XML looks pretty much isomorphic, so nothing to comment here. Hope this helps. So the best guess would be to change the path from absolute to relative.