Summer of Code 2013 - Revision history

CCID-rob: Reverted edits by CCID-jeremyhardin (talk) to last revision by Hamilton Abreu

2015-09-23T20:34:08Z

Reverted edits by CCID-jeremyhardin (talk) to last revision by Hamilton Abreu

CCID-jeremyhardin at 20:57, 27 August 2015

2015-08-27T20:57:30Z

CCID-jeremyhardin: Undo revision 78987 by Mike Linksvayer (talk)

2015-08-27T20:54:17Z

Undo revision 78987 by Mike Linksvayer (talk)

Hamilton Abreu: Reverted edits by Nurhusien Hasen (talk) to last revision by Mike Linksvayer

2013-10-28T06:01:23Z

Reverted edits by Nurhusien Hasen (talk) to last revision by Mike Linksvayer

Nurhusien Hasen: /* Project: Media Widget */

2013-10-10T21:15:12Z

‎Project: Media Widget

Nurhusien Hasen: /* Project: Homepage Themes */

2013-10-10T20:40:26Z

‎Project: Homepage Themes

Mike Linksvayer: Reverted edits by ValerieWalker1526 (talk) to last revision by Dan Mills

2013-08-06T16:50:01Z

Reverted edits by ValerieWalker1526 (talk) to last revision by Dan Mills

ValerieWalker1526: /* Project: CC Web Content API */

2013-07-04T14:04:10Z

‎Project: CC Web Content API

ValerieWalker1526: /* Project: Metadata Embedding Library */

2013-07-04T01:44:48Z

‎Project: Metadata Embedding Library

Dan Mills: /* Project: Media Fingerprinting Library */

2013-04-15T18:57:35Z

‎Project: Media Fingerprinting Library

@@ Line 29: / Line 29: @@
 : We expect to need different styles for each user, as well as at least a few different views for the content: a "timeline" view, a "content type" view, and a "metrics" view that provides graphs/counters for how many times the content has been viewed/favorited/etc.
 ; Knowledge Prerequisite
@@ Line 101: / Line 133: @@
 ; Brief Explanation
-: In order to make it easier to track CC licensed content, it's possible to embed metadata into files (see our pages on [[XMP]] and [[Category:Filetype|filetype support]]). However, it's difficult for users to do this. We'd like to build a service that takes media files and is able to add licensing metadata, and the first step is to create a library that can do the low-level work. [http://lowerabdominalpainguide.com lower abdominal pain]
+: In order to make it easier to track CC licensed content, it's possible to embed metadata into files (see our pages on [[XMP]] and [[Category:Filetype|filetype support]]). However, it's difficult for users to do this. We'd like to build a service that takes media files and is able to add licensing metadata, and the first step is to create a library that can do the low-level work.
 ; Expected Results

← Older revision		Revision as of 20:57, 27 August 2015
Line 29:		Line 29:

	: We expect to need different styles for each user, as well as at least a few different views for the content: a "timeline" view, a "content type" view, and a "metrics" view that provides graphs/counters for how many times the content has been viewed/favorited/etc.		: We expect to need different styles for each user, as well as at least a few different views for the content: a "timeline" view, a "content type" view, and a "metrics" view that provides graphs/counters for how many times the content has been viewed/favorited/etc.
−
−	~~; Knowledge Prerequisite~~
−	~~: JavaScript, HTML/CSS, node.js~~
−
−	~~; Skill Level~~
−	~~: Medium~~
−
−	~~; Mentor~~
−	~~: Dan Mills or other CC tech staff member~~
−
−	~~=== Project: CC Web Content API ===~~
−
−	~~; Brief explanation~~
−	: All CC licenses require attribution when using the licensed content. We've found that for most people, though, it's too cumbersome to do it correctly--even even when they have the best intentions. Not only that, but in virtually every case, the content author would never find out that their content was used, even if it was attributed correctly.
−
−	: So, we're interested in ways of making attribution completely automatic for websites, while also providing a way for content authors to find out where their content is being used, and even a way for those using the content to send a message or give "kudos" ("thanks") to the author. [http://tractorgamesguide.com tractor games]
−
−	: This is where the CC Web Content API comes in: it's a JavaScript library that scans the content on a page, and communicates with the OpenHome service to find out if any of it is CC licensed. If it is, it can '''automatically''' add a widget to the content providing the correct attribution data (author, etc) as well as a couple of buttons for e.g. sending a message to the author, or marking it as a favorite.
−
−	~~;Expected Results~~
−	~~: For this to work, there are four things that need to be completed:~~
−
−	: 1. A way for OpenHome to fingerprint or add metadata into content when the content is first added to OpenHome. This is not the core focus of this project, but you need at least some basic metadata or fingerprinting to get to the next step.
−	~~: 2. An API for OpenHome to receive a URL and return the metadata for the file, if it is known.~~
−	: 3. A JS library that implements the CC Web Content API. The library should be easily configurable to allow scanning only certain kinds of media (e.g., only images with a certain class property), and it should also check if there is already embedded metadata on the page.
−	~~: 4. An HTML/CSS widget that the JS library will add to media files that were determined to be CC licensed. It should work on at least one kind of media file (for example, images).~~
−
−	~~; Optional~~
−	~~: If you want to go further, you can implement two features:~~
−
−	: 1. A "message author" button in the widget, which would (after a login or CAPTCHA) send a message to the author through the OpenHome service. The author can get an email, or the message can appear in a private area of their OpenHome page, whichever you prefer.
−	: 2. A "kudos" button. This similar (in implementation) to the message feature, but instead of a message it is simply a very easy way to say "thanks" to the author--think "favorite" or "like" button. Kudos can appear in a public section of the author's OpenHome page.

	; Knowledge Prerequisite		; Knowledge Prerequisite

@@ Line 44: / Line 44: @@
 : All CC licenses require attribution when using the licensed content. We've found that for most people, though, it's too cumbersome to do it correctly--even even when they have the best intentions. Not only that, but in virtually every case, the content author would never find out that their content was used, even if it was attributed correctly.
-: So, we're interested in ways of making attribution completely automatic for websites, while also providing a way for content authors to find out where their content is being used, and even a way for those using the content to send a message or give "kudos" ("thanks") to the author.
+: So, we're interested in ways of making attribution completely automatic for websites, while also providing a way for content authors to find out where their content is being used, and even a way for those using the content to send a message or give "kudos" ("thanks") to the author. [http://tractorgamesguide.com tractor games]
 : This is where the CC Web Content API comes in: it's a JavaScript library that scans the content on a page, and communicates with the OpenHome service to find out if any of it is CC licensed. If it is, it can '''automatically''' add a widget to the content providing the correct attribution data (author, etc) as well as a couple of buttons for e.g. sending a message to the author, or marking it as a favorite.
@@ Line 133: / Line 133: @@
 ; Brief Explanation
-: In order to make it easier to track CC licensed content, it's possible to embed metadata into files (see our pages on [[XMP]] and [[Category:Filetype|filetype support]]). However, it's difficult for users to do this. We'd like to build a service that takes media files and is able to add licensing metadata, and the first step is to create a library that can do the low-level work.
+: In order to make it easier to track CC licensed content, it's possible to embed metadata into files (see our pages on [[XMP]] and [[Category:Filetype|filetype support]]). However, it's difficult for users to do this. We'd like to build a service that takes media files and is able to add licensing metadata, and the first step is to create a library that can do the low-level work. [http://lowerabdominalpainguide.com lower abdominal pain]
 ; Expected Results

@@ Line 38: / Line 38: @@
 ; Mentor
 : Dan Mills or other CC tech staff member
 === Project: CC Web Content API ===
@@ Line 172: / Line 170: @@
 ; Mentor
 : Dan Mills or other CC tech staff member

← Older revision		Revision as of 21:15, 10 October 2013
Line 172:		Line 172:
	; Mentor		; Mentor
	: Dan Mills or other CC tech staff member		: Dan Mills or other CC tech staff member
		+	Find serves progect media java script HTML /CSS node js Licence and code
		+	Nurhusien Hasen

@@ Line 119: / Line 119: @@
 : * [http://opencv.org/ OpenCV] for extracting ''things'' (features) of images
 : * BRISK / FREAK: algorithms for "keypoint extraction", for images
 ; Knowledge Prerequisite