depend-examples - Revision history

Brian: Reverted edits by LasitC4tol (Talk) to last version by Tantek

2008-12-20T18:56:46Z

Reverted edits by LasitC4tol (Talk) to last version by Tantek

← Older revision		Revision as of 18:56, 20 December 2008
Line 1:		Line 1:
	~~drondronc~~
	= depend examples =		= depend examples =
	== Overview ==		== Overview ==

LasitC4tol: darcnacla

2008-12-19T23:27:57Z

darcnacla

← Older revision		Revision as of 23:27, 19 December 2008
Line 1:		Line 1:
			drondronc
	= depend examples =		= depend examples =
	== Overview ==		== Overview ==

Tantek: en-US, added pre/nowiki as stopgap to expose inline markup as literals rather than having them screw up the page - needs cleanup.

2007-09-01T00:12:22Z

en-US, added pre/nowiki as stopgap to expose inline markup as literals rather than having them screw up the page - needs cleanup.

← Older revision		Revision as of 00:12, 1 September 2007
Line 27:		Line 27:
	=== Linux Kernel ===		=== Linux Kernel ===
	http://kernel.org/		http://kernel.org/
			<pre><nowiki>
	* uses <link> to provide RSS feed		* uses <link> to provide RSS feed
	* <div id="versions"> uses word "versions"		* <div id="versions"> uses word "versions"
Line 34:		Line 35:
	* includes the date published		* 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...		* uses keywords as anchor text to perform operations or view additional features. for example, V for view diff, changelog to see the changelog, etc...
			</nowiki></pre>
	=== libPNG ===		=== libPNG ===
	http://libpng.org/pub/png/libpng.html		http://libpng.org/pub/png/libpng.html
			<pre><nowiki>
	* <LINK REV="made" HREF="http://pobox.com/~newt/greg_contact.html">		* <LINK REV="made" HREF="http://pobox.com/~newt/greg_contact.html">
	Interesting. "made by "his guy" :-) . hcard would seem to be a		Interesting. "made by "his guy" :-) . hcard would seem to be a
Line 54:		Line 56:
	good example: easy to see how some semantic techniques would help.		good example: easy to see how some semantic techniques would help.
	would marking this up using hatom help at all?		would marking this up using hatom help at all?
			</nowiki></pre>
	=== libvc ===		=== libvc ===
	http://freshmeat.net/projects/libvc/		http://freshmeat.net/projects/libvc/
			<pre><nowiki>
	* uses <link> to an rss feed		* uses <link> to an rss feed
	* links to other project areas... issue tracking, forums etc...		* links to other project areas... issue tracking, forums etc...
Line 71:		Line 74:
	* download links provided		* download links provided
	* no semantic markup present.		* no semantic markup present.
			</nowiki></pre>

	=== Ruby FastCGI ===		=== Ruby FastCGI ===
	http://raa.ruby-lang.org/project/fcgi/		http://raa.ruby-lang.org/project/fcgi/
			<pre><nowiki>
	* <link> and <meta> used to convey authorship, "made", author, and		* <link> and <meta> used to convey authorship, "made", author, and
	some other attributes: search, index, home, glossary		some other attributes: search, index, home, glossary
Line 87:		Line 92:
	Shows a receptivity to semantic techniques as well as confirming the		Shows a receptivity to semantic techniques as well as confirming the
	list of properties published by software vendors.		list of properties published by software vendors.
			</nowiki></pre>

	=== Portage: dev-lang/erlang ===		=== Portage: dev-lang/erlang ===
	http://www.gentoo-portage.com/dev-lang/erlang/Dep#ptabs		http://www.gentoo-portage.com/dev-lang/erlang/Dep#ptabs
			<pre><nowiki>
	* <link> to rss feed		* <link> to rss feed
	* <body id="gentoo-portage"> intended consumer published in markup		* <body id="gentoo-portage"> intended consumer published in markup
Line 101:		Line 108:
	class="depbox with links.		class="depbox with links.
	* >= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1		* >= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1
	* the previous ~~behaviour~~ is used for each version of the published software		* the previous behavior is used for each version of the published software
			</nowiki></pre>

	Lots of semantic html. Could be clues for possibles property names.		Lots of semantic html. Could be clues for possibles property names.
Line 108:		Line 116:
	* [[rel-tag]] (for language, etc.)		* [[rel-tag]] (for language, etc.)
	* [[rel-license]]		* [[rel-license]]
	* [[hcard hCard]] (for authors)		* [[hcard\|hCard]] (for authors)

	* [http://usefulinc.com/doap/ DOAP] is an RDF representation of open source software projets		* [http://usefulinc.com/doap/ DOAP] is an RDF representation of open source software projets
	** [http://lists.usefulinc.com/pipermail/doap-interest/2004-September/000077.html Mike Stanley's post on doap-interest] is about software dependencies		** [http://lists.usefulinc.com/pipermail/doap-interest/2004-September/000077.html Mike Stanley's post on doap-interest] is about software dependencies

TomMorris: this page needs cleanup - it's all over the place!

2007-08-11T17:09:45Z

this page needs cleanup - it's all over the place!

← Older revision		Revision as of 17:09, 11 August 2007
Line 30:		Line 30:
	* <div id="versions"> uses word "versions"		* <div id="versions"> uses word "versions"
	* uses links to deliverable with version string as anchor text		* uses links to deliverable with version string as anchor text
	* uses a kind of "product/software id" (my made up term) <table		* uses a kind of "product/software id" (my made up term) <table class="kver"> to identify the thing being described
	class="kver"> to identify the thing being described
	* includes a description of the software		* includes a description of the software
	* includes the date published		* includes the date published
	* uses keywords as anchor text to perform operations or view		* uses keywords as anchor text to perform operations or view additional features. for example, V for view diff, changelog to see the changelog, etc...
	additional features. for example, V for view diff, changelog to see
	the changelog, etc...

	=== libPNG ===		=== libPNG ===
Line 105:		Line 102:
	* >= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1		* >= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1
	* the previous behaviour is used for each version of the published software		* the previous behaviour is used for each version of the published software

	Lots of semantic html. Could be clues for possibles property names.		Lots of semantic html. Could be clues for possibles property names.

Line 112:		Line 110:
	* [[hcard hCard]] (for authors)		* [[hcard hCard]] (for authors)

	* [[http://usefulinc.com/doap/ DOAP]] ~~(similar in nature)~~		* [http://usefulinc.com/doap/ DOAP] is an RDF representation of open source software projets
			** [http://lists.usefulinc.com/pipermail/doap-interest/2004-September/000077.html Mike Stanley's post on doap-interest] is about software dependencies

Phae: Reverted edit of CfaFg5, changed back to last version by DerrickPallas

2007-07-09T14:51:26Z

Reverted edit of CfaFg5, changed back to last version by DerrickPallas

@@ Line 103: / Line 103: @@
 * <h3>Runtime Dependencies</h3> dependencies published using <div
 class="depbox with links.
+* &gt;= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1

CfaFg5 at 15:54, 8 July 2007

2007-07-08T15:54:22Z

@@ Line 103: / Line 103: @@
 * <h3>Runtime Dependencies</h3> dependencies published using <div
 class="depbox with links.
-* &gt;= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1

DerrickPallas: /* Portage: dev-lang/erlang */

2007-02-01T03:33:04Z

Portage: dev-lang/erlang

← Older revision		Revision as of 03:33, 1 February 2007
Line 103:		Line 103:
	* <h3>Runtime Dependencies</h3> dependencies published using <div		* <h3>Runtime Dependencies</h3> dependencies published using <div
	class="depbox with links.		class="depbox with links.
	* >=<a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1		* >= <a href="/dev-lang/perl">dev-lang/perl</a>-5.6.1
	* the previous behaviour is used for each version of the published software		* the previous behaviour is used for each version of the published software
	Lots of semantic html. Could be clues for possibles property names.		Lots of semantic html. Could be clues for possibles property names.

	== See Also ==		== See Also ==

DerrickPallas at 03:31, 1 February 2007

2007-02-01T03:31:37Z

← Older revision		Revision as of 03:31, 1 February 2007
Line 5:		Line 5:

	* [[DerrickPallas\|Derrick Pallas]]		* [[DerrickPallas\|Derrick Pallas]]
			* [[BenWest\|Ben West]]

	== Motivation ==		== Motivation ==

DerrickPallas at 03:31, 1 February 2007

2007-02-01T03:31:12Z

New page

= depend examples =
== Overview ==
This page is dedicated to fleshing out examples of dependency (software and otherwise) on the Web-At-Large.
== Authors ==

* [[DerrickPallas|Derrick Pallas]]

== Motivation ==
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."

== Examples ==

=== Linux Kernel ===
http://kernel.org/
* 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...

=== libPNG ===
http://libpng.org/pub/png/libpng.html
* <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?

=== libvc ===
http://freshmeat.net/projects/libvc/
* 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.

=== Ruby FastCGI ===
http://raa.ruby-lang.org/project/fcgi/
* <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.

=== Portage: dev-lang/erlang ===
http://www.gentoo-portage.com/dev-lang/erlang/Dep#ptabs
* <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 behaviour is used for each version of the published software
Lots of semantic html. Could be clues for possibles property names.

== See Also ==
* [[rel-tag]] (for language, etc.)
* [[rel-license]]
* [[hcard hCard]] (for authors)

* [[http://usefulinc.com/doap/ DOAP]] (similar in nature)