Re: Low-hanging fruit: compulsory namespaces

[Antone Roundy <antone@xxxxxxxxxxxxxx>]

On Tuesday, July 13, 2004, at 03:56  PM, Tim Bray wrote:
> I suggest that we have good enough consensus to remove the paragraph 
> in draft-format-00 in section 2. beginning "All elements and 
> attributes in an Atom document MUST be namespace-qualified".  Because 
> lots of attributes aren't, and when it was pointed out that this would 
> forbid encapsulating RSS 2.0 and Docbook, nobody pushed back and said 
> "it's OK to forbid that".  -Tim
I think I missed something--where would one put RSS 2.0 into an Atom 
feed?  In a content construct?  As inline XML?  How would that be done 
without creating namespace conflicts, assuming the Atom document has 
Atom's namespace as the default namespace?  Is this the correct answer 
to my own question?

<feed xmlns="http://purl.org/atom/ns#draft-ietf-atompub-format-00";>
	<entry>
		<atom:content type="application/rss+xml" xmlns="" 
xmlns:atom="http://purl.org/atom/ns#draft-ietf-atompub-format-00";>
			<!-- RSS 2.0 goes here -->
		</atom:content>
	</entry>
</feed>