On 22/8/05 10:28 AM, "Bob Wyman" <[EMAIL PROTECTED]> wrote:
> What should an aggregate feed generator like PubSub do when it finds
> an entry in a feed that contains unscoped extensions as children of the
> feed?
It's an interesting problem. A pity now that the idea of segregating
entry-defaults at the feed level didn't get sufficient momentum.
But what if there was an widely known extension developed for just this
purpose -- providing entry metadata at the feed level. Possibly in a
wrapper, possibly by flagging with an attribute.
Like this...
<feed ...>
...
<entry:defaults>
<ext1:foo ../>
<ext2:bar ../>
<ext3:qaz ../>
</entry:defaults>
<entry>
...
</entry>
</feed>
or like this ...
<feed ...>
...
<ext1:foo .. entry:default="true"/>
<ext2:bar .. entry:default="true"/>
<ext3:qaz .. entry:default="true"/>
<entry>
...
</entry>
</feed>
e.
