downloads-brainstorming - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:21:46Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:21, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Downloads Brainstorming ~~</entry-title>~~		{{DISPLAYTITLE:Downloads Brainstorming }}

	This page is part of the effort to develop a microformat for [[downloads]].		This page is part of the effort to develop a microformat for [[downloads]].

Tantek: move sparkle/appcast stuff together in adjacent subsections near the bottom, update header, authorship from history

2013-12-12T21:20:47Z

move sparkle/appcast stuff together in adjacent subsections near the bottom, update header, authorship from history

@@ Line 1: / Line 1: @@
-<h1>Downloads Brainstorming </h1>
+<entry-title>Downloads Brainstorming </entry-title>
-The purpose of this page is to capture software download and software update practices in the wild, as one effort to codify practices currently used in the automatic update system called Sparkle.
+This page is part of the effort to develop a microformat for [[downloads]].
-This page was recently merged from appcast-brainstorming, and may therefore still have references to an "appcast microformat".
+See previous research:
+* [[downloads-examples]]
-__TOC__
+* [[downloads-formats]]
 == Context ==
@@ Line 23: / Line 18: @@
 * [[hash-brainstorming]] has a section about hAtom integration. The example uses a "download" class, which contains a rel-enclosure link as well as a span with "md5" and "checksum" classes.
 == Proposal ==
@@ Line 167: / Line 150: @@
 * Figure out whether [[hListing]] could be used instead of [[hAtom]].
 * Figure out whether changesets can benefit from this microformat.
 == Software using appcasts ==

Tantek: Reverted edits by AaliyahCunningham (Talk) to last version by Kwill

2011-08-21T23:01:46Z

Reverted edits by AaliyahCunningham (Talk) to last version by Kwill

← Older revision		Revision as of 23:01, 21 August 2011
Line 22:		Line 22:
	== Related Work ==		== Related Work ==

	* [[hash-brainstorming]] has a ~~<span class="plainlinks">[http://mycaal.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">loan modification</span>]~~ section about hAtom integration. The example uses a "download" class, which contains a rel-enclosure link as well as a span with "md5" and "checksum" classes.		* [[hash-brainstorming]] has a section about hAtom integration. The example uses a "download" class, which contains a rel-enclosure link as well as a span with "md5" and "checksum" classes.

	== Sparkle-specific Appcast enhancements ==		== Sparkle-specific Appcast enhancements ==
Line 106:		Line 106:
	* Marking up a single download with hAtom doesn't make much sense.		* Marking up a single download with hAtom doesn't make much sense.

	A simpler download microformat, which is basically a rel-enclosure with some extra data (MD5 sum, DSA signature) may be useful. Something along these ~~<span class="plainlinks">[http://diamondlinks.net/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">link building</span>]~~ lines, perhaps:		A simpler download microformat, which is basically a rel-enclosure with some extra data (MD5 sum, DSA signature) may be useful. Something along these lines, perhaps:

	* download		* download

AaliyahCunningham at 17:44, 21 August 2011

2011-08-21T17:44:37Z

← Older revision		Revision as of 17:44, 21 August 2011
Line 22:		Line 22:
	== Related Work ==		== Related Work ==

	* [[hash-brainstorming]] has a section about hAtom integration. The example uses a "download" class, which contains a rel-enclosure link as well as a span with "md5" and "checksum" classes.		* [[hash-brainstorming]] has a <span class="plainlinks">[http://mycaal.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">loan modification</span>] section about hAtom integration. The example uses a "download" class, which contains a rel-enclosure link as well as a span with "md5" and "checksum" classes.

	== Sparkle-specific Appcast enhancements ==		== Sparkle-specific Appcast enhancements ==
Line 106:		Line 106:
	* Marking up a single download with hAtom doesn't make much sense.		* Marking up a single download with hAtom doesn't make much sense.

	A simpler download microformat, which is basically a rel-enclosure with some extra data (MD5 sum, DSA signature) may be useful. Something along these lines, perhaps:		A simpler download microformat, which is basically a rel-enclosure with some extra data (MD5 sum, DSA signature) may be useful. Something along these <span class="plainlinks">[http://diamondlinks.net/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">link building</span>] lines, perhaps:

	* download		* download

Kwill: /* Software using appcasts */ added Wakoopa, which supports a variety of formats, linked to the non-appcast formats for reference

2009-05-06T13:12:38Z

Software using appcasts: added Wakoopa, which supports a variety of formats, linked to the non-appcast formats for reference

← Older revision		Revision as of 13:12, 6 May 2009
Line 175:		Line 175:
	* [http://metaquark.de/appfresh/ AppFresh] uses Sparkle-enhanced appcasts, including those generated by [http://iusethis.com/ iusethis] (e.g. [http://osx.iusethis.com/appcast/igtd the iGTD appcast]).		* [http://metaquark.de/appfresh/ AppFresh] uses Sparkle-enhanced appcasts, including those generated by [http://iusethis.com/ iusethis] (e.g. [http://osx.iusethis.com/appcast/igtd the iGTD appcast]).
	* [http://hohle.net/projects/spangle/ Spangle] (formerly known as Perrier) uses Sparkle-enhanced RSS appcasts.		* [http://hohle.net/projects/spangle/ Spangle] (formerly known as Perrier) uses Sparkle-enhanced RSS appcasts.
			* [http://www.wakoopa.com Wakoopa]'s [http://www.wakoopa.com/vendors vendor program] (web application) supports VersionTracker [http://en.wikipedia.org/wiki/VersionTracker], Appcast and PAD [http://en.wikipedia.org/wiki/Portable_Application_Description]

	== Implementations ==		== Implementations ==

Kwill: added note that there are users who want to see and use the MD5 checksum

2009-05-06T13:05:23Z

added note that there are users who want to see and use the MD5 checksum

← Older revision		Revision as of 13:05, 6 May 2009
Line 156:		Line 156:

	Additionally, stuff such as MD5 checksums and DSA signatures should probably be hidden from the release notes view as well, because they can't be used by the user anyway (but they are used by Sparkle).		Additionally, stuff such as MD5 checksums and DSA signatures should probably be hidden from the release notes view as well, because they can't be used by the user anyway (but they are used by Sparkle).
			** MD5s are used manually, i.e. on some download pages they appear as visible text next to the download link, and there are tools (MD5 apps and download apps with MD5 options) for manual copying and pasting

	To prevent this download link (as well as the MD5 sum etc) from showing up, anything inside a mini "download" microformat (see above) could be hidden.		To prevent this download link (as well as the MD5 sum etc) from showing up, anything inside a mini "download" microformat (see above) could be hidden.
			** MD5s should not be hidden from users who would copy and paste it (see above)

	== To Do ==		== To Do ==

DenisDefreyne: Adding shortVersionNumber to Version Numbers issue

2007-08-18T15:19:53Z

Adding shortVersionNumber to Version Numbers issue

← Older revision		Revision as of 15:19, 18 August 2007
Line 135:		Line 135:

	In the proposal above, the "version" class name is used, but I'm not happy about it. In other microformats, "version" is used to indicate the version of the microformat, not the version of something that is described using the microformat. "revision" is probably a better name.		In the proposal above, the "version" class name is used, but I'm not happy about it. In other microformats, "version" is used to indicate the version of the microformat, not the version of something that is described using the microformat. "revision" is probably a better name.

			Sparkle can actually use a "shortVersionNumber" argument, which is displayed in Sparkle instead of "version" if present.

			These two version attributes will need to be marked up in some way in the appcast microformat at well. Some possible names:
			* "revision" and "short-revision"
			** The term "revision" isn't usually used in released software; I think I've only heard the term in VCSes (CVS, SVN, etc).
			* "app-version" and "app-version-short"
			* "enclosure-version" and "short-enclosure-version"
			** Seems to refer to the version of the download, and not necessarily the version of the application included in the download

	=== Overlap with Changesets ===		=== Overlap with Changesets ===

DenisDefreyne: Adding "download link in entry-content" issue

2007-08-18T13:10:25Z

Adding "download link in entry-content" issue

← Older revision		Revision as of 13:10, 18 August 2007
Line 139:		Line 139:

	Changesets are very similar to downloads, with the exception that there are no downloads (another reason why the "downloads" name sucks?). Each changeset entry (hentry) usually has a short description (entry-title), a list of changes (entry-description), and a revision number.		Changesets are very similar to downloads, with the exception that there are no downloads (another reason why the "downloads" name sucks?). Each changeset entry (hentry) usually has a short description (entry-title), a list of changes (entry-description), and a revision number.

			=== Download Link in entry-content ===

			It makes sense for the download link (the one with rel-enclosure) to sit inside the entry-content. Otherwise, what's the point of having a download link if it doesn't show up in the feed?

			If the download link is inside the entry-content, though, Sparkle's "release notes" view will show that download link as well. This is confusing, because people could click that link in the release notes view, which would download the update in Safari like a regular file. Instead, the user should click the "Install Update" button.

			Additionally, stuff such as MD5 checksums and DSA signatures should probably be hidden from the release notes view as well, because they can't be used by the user anyway (but they are used by Sparkle).

			To prevent this download link (as well as the MD5 sum etc) from showing up, anything inside a mini "download" microformat (see above) could be hidden.

	== To Do ==		== To Do ==

DenisDefreyne: Improving the Smaller Download Microformat section.

2007-08-15T10:05:25Z

Improving the Smaller Download Microformat section.

← Older revision		Revision as of 10:05, 15 August 2007
Line 88:		Line 88:

	It's been suggested that tags could be used to mark up OSes and architectures.		It's been suggested that tags could be used to mark up OSes and architectures.

	== Issues ==		== Issues ==

Line 105:		Line 106:
	* Marking up a single download with hAtom doesn't make much sense.		* Marking up a single download with hAtom doesn't make much sense.

	A simpler download microformat, which is basically a rel-enclosure with some extra data (MD5 sum, DSA signature) may be useful.		A simpler download microformat, which is basically a rel-enclosure with some extra data (MD5 sum, DSA signature) may be useful. Something along these lines, perhaps:

			* download
			** [[rel-enclosure]]
			** hash (see [[hash-brainstorming]])
			** signature

			For example:

			<code><pre><p class="download">
			Download <a href="blah.zip" rel="enclosure">Blah 2.1</a>!
			(<span class="checksum"><span class="type">MD5</span> checksum: <span class="value">c23316cb51ca5125d1417faba5cef51e</span></span>).
			</p></pre></code>

			This smaller download microformat could then be used inside a hentry in the larger appcast microformat.

	=== Naming ===		=== Naming ===

Silona at 19:09, 14 August 2007

2007-08-14T19:09:56Z

← Older revision		Revision as of 19:09, 14 August 2007
Line 1:		Line 1:
	<h1>Downloads Brainstorming </h1>		<h1>Downloads Brainstorming </h1>

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

	This page was recently merged from appcast-brainstorming, and may therefore still have references to an "appcast microformat".		This page was recently merged from appcast-brainstorming, and may therefore still have references to an "appcast microformat".