Difference between revisions of "HTML"
Jon Phillips (talk | contribs) (update) |
|||
| (19 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Filetype | ||
| + | |license_url=Yes | ||
| + | |web_statement=Yes | ||
| + | |more_permissions=Yes | ||
| + | }} | ||
| + | |||
Using a few lines of HTML given to you during the licensing process, you can reference the license that covers your work. To do so as clearly as possible, you should try to do the following: | Using a few lines of HTML given to you during the licensing process, you can reference the license that covers your work. To do so as clearly as possible, you should try to do the following: | ||
| Line 6: | Line 12: | ||
Some examples: | Some examples: | ||
| − | |||
| − | |||
<table align="center"> | <table align="center"> | ||
<tr> | <tr> | ||
<td> | <td> | ||
| − | [[ | + | [http://www.scottandrew.com/main/songs/american_thing Scott Andrew] lets visitors know each song is licensed with a prominent button and message. |
| + | </td> | ||
| + | <td> | ||
| + | [http://blogs.law.harvard.edu/stickbug/ Stickbugblog] places its button visibly on its sidebar, asserting specifically that all content is licensed. | ||
| + | </td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td> | ||
| + | [http://www.scottandrew.com/main/songs/american_thing http://creativecommons.org/images/technology/scottandrew.gif] | ||
| + | </td> | ||
| + | <td> | ||
| + | [http://blogs.law.harvard.edu/stickbug/ http://creativecommons.org/images/technology/stinkblog.gif] | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td> | ||
| − | [ | + | [http://bgbg.blogspot.com Bag and Baggage] explains that all pages within the site are licensed. |
</td> | </td> | ||
<td> | <td> | ||
| − | [[ | + | [http://www.lightningfield.com/ Lightningfield.com] notes that only the site's photos are licensed. |
| + | </td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td> | ||
| + | [http://bgbg.blogspot.com/ http://creativecommons.org/images/technology/bgbg.gif] | ||
| + | </td> | ||
| + | <td> | ||
| + | [http://www.lightningfield.com/ http://creativecommons.org/images/technology/lightningfield.gif] | ||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| + | |||
| + | For more information, see [[CC REL]]. | ||
| + | |||
| + | {{Translations | ||
| + | | articles = Pt:HTML, Ru:HTML | ||
| + | }} | ||
| + | |||
| + | [[Category:Developer]] | ||
| + | [[Category:Technology]] | ||
| + | [[Category:Tagging]] | ||
| + | [[Category:Example]] | ||
Latest revision as of 08:25, 28 April 2011
| File Type Information | ||
|---|---|---|
| Supports embedding license URL: | supports_license_url::Yes | |
| Supports embedding web statement: | supports_web_statement::Yes | |
| Supports embedding more permissions: | supports_more_permissions::Yes | |
| Metadata Location: | [[Metadata location::{{{metadata_location}}}]] | (unknown) }} | |
| Metadata Format: | [[Metadata format::{{{metadata_format}}}]] | (unknown) }} | |
Using a few lines of HTML given to you during the licensing process, you can reference the license that covers your work. To do so as clearly as possible, you should try to do the following:
- Specifically define what you're licensing. Websites are often made up of several components. You should note whether you're licensing the entire site, or just certain text, pages, graphics, or files.
- Put the reference in a prominent, visible place. You should place the reference right next to the work you intend to license. If you cannot easily place it next to each work or if you are licensing a large group of works, place the reference somewhere near the top of the page or along a sidebar, rather than hidden at the footer of the page. In addition, make sure that the link appears wherever the licensed works appear on your site, rather than just on the front page.
- If possible, use the CC button to mark your content. This symbol will help people easily recognize that your content is licensed. You can add this button to your site by using the full HTML/RDF supplied during your license selection process. Otherwise, use an ostensible, plain text link.
Some examples:
|
Scott Andrew lets visitors know each song is licensed with a prominent button and message. |
Stickbugblog places its button visibly on its sidebar, asserting specifically that all content is licensed. |
|
http://creativecommons.org/images/technology/scottandrew.gif |
|
|
Bag and Baggage explains that all pages within the site are licensed. |
Lightningfield.com notes that only the site's photos are licensed. |
|
http://creativecommons.org/images/technology/lightningfield.gif |
For more information, see CC REL.
