NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
API design (Score:1)
Sounds like bad API design to me.
permaLinkshould always be the permalink, if there is one, andguidshould always be the GUID, if there is one. How this is specified in the wire format is something the API should not expose.I don’t know if you’re at liberty to make such changes, though.
(In fact, I boggle at the effort you’re putting into a module for RSS… Atom’s
Re:API design (Score:2)
It is bad API design in my opinion. But this was the API since XML::RSS 1.05 [cpan.org]. BTW, in RSS 2.0 what happens is that the guid element has an isPermaLink attribute which can be "true" or "false". If it is true, then permaLink will hold the contents of the "guid" tag, and if it's false then "guid" will.
Not at the moment, no.
Indeed. I didn't take a close look at Atom yet. But I'm making use of XML::RSS personally and so do many other people who generate or parse the various versions of RSS. My work on XML::RSS started when I saw that a feed I generated did not validate, and decided to fix it. Since then it's been quite an obsession for me to work on it in my copious time.
Reply to This
Parent
Re: (Score:1)
Atom [rfc.net]’s just RSS without the bugs [diveintomark.org].