source-brainstorming: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(→‎Usage: Fixing markup error)
(→‎Examples: Add unison.js as an example)
Line 20: Line 20:
* [http://danielmall.com/ Dan Mall's website] links to [https://github.com/danielmall/danielmallcom the source code on GitHub].
* [http://danielmall.com/ Dan Mall's website] links to [https://github.com/danielmall/danielmallcom the source code on GitHub].
* [http://tom.preston-werner.com/ Tom Preston-Warner] links to [http://github.com/mojombo his Github account].
* [http://tom.preston-werner.com/ Tom Preston-Warner] links to [http://github.com/mojombo his Github account].
* [http://responsivedesign.is/resources/javascript-jquery/unison.js The Unison.js project] links to [https://github.com/bjork24/Unison the source code on Github] and [https://github.com/bjork24/Unison/archive/master.zip a direct link to download a .zip file of the source code].

Revision as of 12:02, 4 February 2014

<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.

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.