From the spec: "A RSS feed may contain elements not described on this
page, only if those elements are defined in a namespace."

Question: How does this sentence forbid namespace attributes in core
elements *while* allowing them in namespace elements?

We're already assuming that namespace attributes are OK inside
namespace elements. Isn't the simplest assumption that they are
permitted everywhere in RSS?

--- In rss-public@yahoogroups.com, Sam Ruby <rubys@...> wrote:
> Are you *sure* it was a typo?
> I'm certain I can find people to advocate one or more of the
following ...

Fear of your slippery slope is one reason the spec hasn't been revised
to deal with some longstanding issues that wreak havoc among
implementers. Instead, the RSS Profile attempts to address things like
item enclosures in this manner:

Step 1: Tell people there's confusion or a difference of opinion.

Step 2: Document current use.

Step 3: Come up with a suggestion on how to best deal with the
situation, based on current use.

This approach doesn't work with the namespace attributes issue,
because namespaces function independently of each other. Microsoft's
addition of cf:type to item-description only affects implementers of
its namespace.

So the only way the board can help is to tell people what the
Extending RSS section of the spec means, based on the best information
we have available to us.

If Randy wants to change elements to "elements and attributes" as a
spec clarification, I'm comfortable solving the
problem in that manner.