appcast-brainstorming

From Microformats Wiki
Revision as of 09:40, 28 July 2007 by DenisDefreyne (talk | contribs)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Appcast Brainstorming

The purpose of this page is to capture software updates practices in the wild, as one effort to codify practices currently used in the automatic update system called Sparkle.

Authors

Context

Sites like iusethis.com, versiontracker.com, macupdate.com and download.com among others should be investigated and documented for object names and attributes.

Among common data in a software update changelog are changes or fixes, completed bugs, new features or modified behavior, and known issues. A version number is also typically supplied, but takes on many forms and is not always numeric.

Lastly, this work should be seen as compatible with hAtom, possibly as a prelude to a format that could be embedded as the payload of an hfeed object.

Work should be carried out on the Appcast Examples page.

Sparkle-specific Appcast enhancements

Sparkle adds a few extra features to appcasts:

  • External release notes URL: used when the release notes are not included in the appcast itself
  • MD5 sums and DSA signatures: used for some extra security
  • Advanced version string: Sparkle determines the application version from the enclosure name, which is assumed to be APPNAME_VERSION.zip; the advanced version string allows this convention to be overridden

hAppcasts should probably support these features as well.