source-brainstorming: Difference between revisions
Jump to navigation
Jump to search
(Adding an example from Dan Mall's site) |
m (Use cases) |
||
Line 11: | Line 11: | ||
== Use Cases == | == 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 | 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 == | == Examples == |
Revision as of 19:06, 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.
- Dan Eden's website links to the source code on GitHub.
- Dan Mall's website links to the source code on GitHub.