source-brainstorming: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (Use cases)
m (Add example of a "fork me on Github" ribbom)
Line 19: Line 19:
* [https://daneden.me/ Dan Eden's website] links to [https://github.com/daneden/daneden.me the source code on GitHub].
* [https://daneden.me/ Dan Eden's website] links to [https://github.com/daneden/daneden.me 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://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].

Revision as of 19:12, 3 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.