license

From IndieWeb


license is terms under which you are allowed to (re)use a piece of work; in the context of the IndieWeb, for source code such as in open source projects, or content, like the IndieWeb wiki itself which has a specific Copyright.

How to

How to markup licensing of a post

You can markup the licensing of an entire post on its permalink page with rel-license. Link from the permalink page to the license you're using (e.g. Creative Commons) and put rel="license" on that link.

Brainstorming

Why and when

  • When reposting a post, it would be nice to know if you have permission for such repost. If you tell your server to repost something, it can check for a usable license and then either display the full post, or only link to it.
  • The above could also apply to reply context.
  • The above could also apply to displaying remote comments and likes.

Licensing specific things

There's no good current way to markup licenses for specific / individual posts in a feed like a composite stream.

Similarly, if you only want to license part of a post, there's no good current way to do that either.

Some possibilities:

  • Introduce a u-license property to h-entry that links to the license for that entry. This would replace rel-license, and provide more flexibility.
  • Have some separate specific license for the u-photo / u-video / u-audio in a post
    • Or just use the same u-license that is there for the entire post

IndieWeb Examples

Christian Weiske

Christian Weiske links a license in the <head> of each blog post, e.g. http://cweiske.de/tagebuch/broken-plain-sight.htm:

<link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-nc-sa/3.0/"/>
<link rel="license" type="application/rdf+xml" href="http://creativecommons.org/licenses/by-nc-sa/3.0/rdf"/>

Jamie Tanna

  Jamie Tanna defines two licenses per post:

  • Prose, for the post's written content (defaults to CC-BY-SA-NC-4.0)
  • Code, for any code snippets in the post (defaults to Apache-2.0)

Jamie wrote about changing the way he approach licensing on 2018-07-29 and 2019-09-28

Add yourself here… (see this for more details)

Other Examples

<a rel="license" href="http://creativecommons.org/licenses/by/4.0/">
  <img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" />
</a><br />
This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.


Sessions

Related sessions at IndieWebCamps:


See Also