Difference between revisions of "depend-examples"
m (en-US, added pre/nowiki as stopgap to expose inline markup as literals rather than having them screw up the page - needs cleanup.)
|(One intermediate revision by one other user not shown)|
Latest revision as of 18:56, 20 December 2008
This page is dedicated to fleshing out examples of dependency (software and otherwise) on the Web-At-Large.
Right now, there many ways to install software; whether you're using binaries (apt-get, yum, rpm) or source (emerge, srpm, *-src), you have to go through a clearing house. Someone took the time to compile binaries or repackage source trees and write down what needed what.
But the fact is all of this information is already on the homepage for most software. Current aggregators rely on the author(s) submitting this information manually. Furthermore, commercial packages don't normally submit product information to sites like FreshMeat, SourceForge, or any language-specific repository (CPAN, PEAR). (This includes things like drivers.)
Because the information (version, dependency, package URLs, bug alerts) is already there (see below) it should be fairly straight-forward to figure out what people already do and "semantic it up."
* uses <link> to provide RSS feed * <div id="versions"> uses word "versions" * uses links to deliverable with version string as anchor text * uses a kind of "product/software id" (my made up term) <table class="kver"> to identify the thing being described * includes a description of the software * includes the date published * uses keywords as anchor text to perform operations or view additional features. for example, V for view diff, changelog to see the changelog, etc...
* <LINK REV="made" HREF="http://pobox.com/~newt/greg_contact.html"> Interesting. "made by "his guy" :-) . hcard would seem to be a perfect fit here. * <B>libpng</B> name of software in an element * <A HREF= "http://libpng.sourceforge.net/">http://libpng.sourceforge.net/</A> link to homepage * requires <B>zlib 1.0.4</B> or later (<B>1.2.3</B> or <B>1.1.4</B> lossy markup of requirements * The current public release, <B>libpng 1.2.15</B> again, lossy markup * includes a description of the software * <B>libpng 1.2.12</B> another mention of the software in it's own element * the site contains links to test suites, documentation, and download links * also includes a description of how to verify the contents * lots of content about the software, but very little semantic markup. good example: easy to see how some semantic techniques would help. would marking this up using hatom help at all?
* uses <link> to an rss feed * links to other project areas... issue tracking, forums etc... * branch info published * date added, created, modified all published * description * author * "trove" categories * might list dependencies, but there are none for this particular example * stats listed: vitality, popularity, downloads, graphs... * hits, subscribers * other projects depending on this one are listed * license published * download links provided * no semantic markup present.
* <link> and <meta> used to convey authorship, "made", author, and some other attributes: search, index, home, glossary * interesting, there is some semantic html... <p class="caption">fcgi / 0.8.7</p> <table class="entry"> * key value pairs (in a table) for: short description, category, status, created, last update, owner, homepage, download, source vieweing, license, dependency, versions as link text to the deliverable with date published outside the link * uses address to list contact for the document, and other uses of semantic html such as class names "footer", "header", and "caption". Shows a receptivity to semantic techniques as well as confirming the list of properties published by software vendors.
* <link> to rss feed * <body id="gentoo-portage"> intended consumer published in markup * links to other project areas * <h2 id="packageid">dev-lang/erlang </h2> product name * <h5> used for description * <div id="website_list"><ul>...</ul></div> used to list project websites * <div id="ebuild_list"><ul>... used for consumer-specific parameters * "view" and "download" links. * <h3>Runtime Dependencies</h3> dependencies published using <div class="depbox with links. * >= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1 * the previous behavior is used for each version of the published software
Lots of semantic html. Could be clues for possibles property names.