Extensions are proposals for non-core modifications or additions to the Atom Syntax or Protocol specifications.
Discussion of extensions should be limited to this wiki (for now) or private exchanges as opposed to the primary syntax and protocol mailing lists so as not to disrupt the very important work of finalizing the core of the specification upon which these extensions are built.
Extensions listed here are just proposals for Atom add-ons, they are not under consideration for addition to the atom core and should never be assumed to be "a part of the Atom specification"
See also discussion at ExtensionModule
Pick stuff that's already been proven to work and be interoperable, and writing it down in a clean, clear way
Keep it simple: The simplest thing that can possibly work tends to be preferred over more complex solutions.
QNames values in attributes are to be avoided whenever possible
Actual problems versus theoretical problems: At this point in the game, our primary focus is on solving problems that already exist rather than planning how we can solve problems that might arise in the future. While design should always be done with an eye to the future, if there are not actual use cases to support a proposal, it will tend to get less support for adoption. Once Atom's core is nailed down, more attention might be paid to what it could possibly do. For now, let's make sure it does well what we know we want it to do.
Use of extensions is always optional.
List of Proposed Extensions
- AlternativeRepresentation . . . . 1 match
- BiblioGraphy . . . . 1 match
- Categorization . . . . 1 match
- ComponentBlog . . . . 1 match
- DialogMappingExtension . . . . 1 match
- ExtensionModule . . . . 1 match
- ExtensionTemplate . . . . 1 match
- GeoLocation . . . . 1 match
- License . . . . 1 match
- Related . . . . 1 match
- SponsoredLinks . . . . 1 match