source-brainstorming

<entry-title> Source Brainstorming </entry-title>

Per the microformats process, this page is for brainstorming about ideas, proposals, constraints, requirements for a microformat for indicating the link relationship between a document (or site) and its source code.

Usage

<a href="https://github.com/adactio/html5forwebdesigners" rel="source">the source for this book</a>

<link href="https://github.com/adactio/html5forwebdesigners" rel="source" />

Use Cases

When an author links to a project's (or document's) source code (e.g. on GitHub, Google Code, etc.) a rel value of "source" could be used to explicitly define that relationship.

Discussions

rel="code"

source could be better used to define a source where the information came from. When someone writes an article, which is based on informations somewhere else, rel="source" would be a more appropriate name.

Better naming recommendations for the case of this rel-Attribute:

1. code
2. sourcecode

Examples

These examples demonstrate situations where an explicit rel value could be used to mark up an existing document (or project's) link to its source.

• Dan Eden's website links to the source code on GitHub.
• Dan Mall's website links to the source code on GitHub.
• Tom Preston-Warner links to his Github account.
• The Unison.js project links to the source code on Github and a direct link to download a .zip file of the source code.