Re: Re: XML_Atom?
| From: | Joe Stump | Date: | Tue, 02 Aug 2005 18:39:52 +0000 |
| Subject: | Re: Re: XML_Atom? | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-39135@lists.php.net to get a copy of this message | ||
Well, I'd planned on shooting for how DB manages slight differences in the various DB engines. I'd rather support 80% of all of the features of the feeds in the ambiguous Entry class and then allow an interface to the "raw entry".
--Joe
On Aug 1, 2005, at 11:46 PM, Sergio Carvalho wrote:
Joe Stump wrote:2.) I disagree. I plan on having an ambiguous entry class that you could hand off to the Writer's driver that would then handle building the Atom/RSS specific tags. So you'd do something like this:Out of curiosity: How do you avoid creating a leaky abstraction? For example, Atom provides both 'author' and 'contributor' elements, while RSS (v2) provides 'author' and something called 'managingEditor' on the same line. Do you merge? Do you keep only common elements? This is one of many slightly different definitions on both standards. If you compare to RSS 0.xx then the diference is even bigger... -- Sérgio --PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php