Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.21.0

Bug #170 RDF examples produce incorrect code
Submitted: 2003-10-30 21:58 UTC
From: shaun at aegisdesign dot co dot uk Assigned: schst
Status: Closed Package: XML_Serializer
PHP Version: 4.3.2 OS: n/a
Roadmaps: (Not assigned)    
Comments Add Comment Add patch

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 20 + 14 = ?

 [2003-10-30 21:58 UTC] shaun at aegisdesign dot co dot uk
Description: ------------ I'm trying to output valid RSS/RDF with your PEAR class but coming up across a couple of problems. Firstly, I think the serializeRDF.php example is incorrect. The <channel> should be closed before the <item>s. Secondly, according to the spec at spec there needs to be an rdf:about="" attribute for each <item> and <channel>. eg. <item rdf:about=""> <title>Processing Inclusions with XSLT</title> <link></link> <description> Processing document inclusions with general XML tools can be problematic. This article proposes a way of preserving inclusion information through SAX-based processing. </description> </item> Is there a way of adding the attribute? or is it a bug in XML_Serializer? As it is, the XML created by this doesn't work in news aggregators eg. SlashDock.


 [2003-10-31 19:24 UTC] schst
The example only shows how XML can be produced, if the RSS is not valid, just change the data structure. Support for attributes and namespaces will be added in future versions.
 [2003-10-31 19:33 UTC] shaun at aegisdesign dot co dot uk
Without attributes it rules out using XML_Serializer for RSS news syndication so I hope they get added soon as I'd much prefer to use a standard PEAR class than rolling my own for each project. I imagine you'd get a lot more users of this if it did.
 [2004-05-24 19:45 UTC] schst
This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on In case this was a website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better.