appcast-brainstorming

(Difference between revisions)

Jump to: navigation, search
(Changed checksum to use type/value; changing entry-version to version; removing downloads microformat in proposal; cleanup)
m (formatting cleanup)
Line 63: Line 63:
</div>
</div>
-
&lt;p>&lt;a href="http://adiumx.cachefly.net/Adium_1.0.4.dmg" rel="enclosure">Download&lt;/a>. <span class="checksum">The <span class="type">MD5</span> checksum of this download is <span class="value">e0d123e5f316bef78bfdf5a008837577</span>.</span>.&lt;/p>
+
<p>
 +
&lt;a href="http://adiumx.cachefly.net/Adium_1.0.4.dmg" rel="enclosure">Download&lt;/a>.
 +
<span class="checksum">The <span class="type">MD5</span> checksum of this download is <span class="value">e0d123e5f316bef78bfdf5a008837577</span>.</span>.
 +
</p>
&lt;/div>
&lt;/div>
&lt;/body>
&lt;/body>

Revision as of 13:50, 3 August 2007

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.

Contents


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.

Related Work

Sparkle-specific Appcast enhancements

Sparkle adds a few extra features to appcasts:

The appcast microformat should probably support these features as well.

The MD5 sum and DSA signature is specific for an enclosure. It is, however, not possible to add these extra attributes to a rel-enclosure link; a larger "enclosure" microformat may be necessary.

Proposal

This proposal is mostly inspired by appcasts with Sparkle extensions.

Example:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
	<head>
		<title>Appcast</title>
	</head>
	<body>
		<h1>Appcast</h1>
		<div class="hentry">
			<h2 class="entry-title">Adium <span class="version">1.0.4</span></h2>
			<p>Updated on <abbr class="updated" title="2007-06-20T18:00+01:00">24 June</abbr>.</p>
			<div class="entry-content">
				<ul>
					<li>Fixed a crash introduced in 1.0.3 which could occur when accounts disconnected or status changed</li>
					<li>Fixed group chat when message history is enabled</li>
				</ul>
			</div>

			<p>
				<a href="http://adiumx.cachefly.net/Adium_1.0.4.dmg" rel="enclosure">Download</a>.
				<span class="checksum">The <span class="type">MD5</span> checksum of this download is <span class="value">e0d123e5f316bef78bfdf5a008837577</span>.</span>.
			</p>
		</div>
	</body>
</html>

The hash microformat used in this proposal is likely to change.

Multi-app/arch/OS/... appcasts

A single downloads page can have downloads for different applications, different versions, different architectures, different operating systems, etc (for example, the MySQL downloads page).

Here's a probably incomplete list of different download properties:

However, multi-* appcasts are hard to do right, and therefore probably not worth supporting. An appcast HTML page should therefore only contain updates for one application, one OS, one architecture, etc.

Software using appcasts

This is a list of programs and frameworks that use appcasts or appcast-like data.

Related Pages

appcast-brainstorming was last modified: Wednesday, December 31st, 1969

Views