[uf-discuss] Google Code microformat?
mephtu at gmail.com
Mon Dec 8 17:56:34 PST 2008
I will try this again giving a scenario...
Joe Cool, adept coder, releases a project, AlphaBUG, to the web on the
code hosting site, www.attaboy.com. Every time Joe releases a new
update, he also publishes an RSS/Atom article describing. The problem
for Joe, who wants to empower AlphaBUG's stakeholders, knows that his
program 1) doesn't exist in a vacuum-it's dependent on other libraries
2) isn't the only program his stakeholders use-they don't want to be
encumbered by having to manually install each update 3) will have
frequent updates as he is prone to releasing updates often. What Joe
hasn't thought of but, what he *needs* is a microformat that will
markup all of this information in the vehicle of RSS/Atom.
So, when I read Joe's feed about the latest update of AlphaBUG on
www.attaboy.com, by a micromiracle I am looking at not only release
notes but library and version dependencies, a hyperlink to download
the package and version information of this update (is it major,
minor, bugfix, etc.), etc. All of this readily extractable from the
RSS/Atom feed because it has been tagged using a microformat.
Then, because this information can be extracted from the feed, I use a
platform installer, which I use to install all packages that have a
microformat-encoded RSS/Atom feed and have it install the update in a
predetermined directory selecting the version that I have specified by
an update policy.
In other words, Joe 's AlphaBUG has been steered onto the paved
highway of automated updates. Windows has it, why can't there be a
generic installer/auto-updater for open-source.
On Sat, Nov 22, 2008 at 1:19 PM, Scott Reynen <scott at randomchaos.com> wrote:
> On [Nov 22], at [ Nov 22] 7:09 , Samuel Richter wrote:
>> It seems to me that both hAtom and hDOAP present limitations of a sort
>> when it comes to providing feeds for software updates. On the one
>> hand with hAtom, you have a generic microformat with no way of
>> identifying any content beyond it merely being feed content and with
>> hDOAP, you have no mechanism for providing update information. Do you
>> see the gap I'm trying to show?
> Microformats are made to be modular. Using both together would seem to
> remove the gap you've described. But as David said, because this is all
> very abstract, it's hard to tell if this would actually meet your needs.
> microformats-discuss mailing list
> microformats-discuss at microformats.org
More information about the microformats-discuss