Bill de hÓra wrote:
James M Snell wrote:
As I've been going through the effort of defining a number of Atom
extensions, I've consistently come back to the thought that it would be
interesting to explore the creation of a "Common Extensions Namespace"
under which multiple standardized extensions can be grouped. I've
written an initial draft of the concept but before I submit it as an
Internet Draft, I'd like to get some feedback from the group. Please
review the attached and let me know what you think.
I don't get it. Why centralize names like this?
Illustration-by-example: suppose that I wanted to use all of the
extensions proposed thus far all at once:
right now I'd end up with:
<feed xmlns="http://www.w3.org/2005/Atom";
xmlns:fh="http://purl.org/syndication/history/1.0";
xmlns:fr="http://purl.org/syndication/index/1.0";
xmlns:fa="http://purl.org/atompub/age/1.0";
xmlns:fh="http://purl.org/syndication/thread/1.0";
xmlns:nf="http://purl.org/atompub/nofollow/1.0";>...</feed>
vs. if they were all covered under a single ace namespace:
<feed xmlns="http://www.w3.org/2005/Atom";
xmlns:ace="http://www.w3.org/2005/Atom-extensions";>
For feed publishers, it is a lot less complex.
Extension publishers would obvious not be required to use the ace
namespace, but it would likely help in the rollout of new extensions.
- James
