Partner Interface - Revision history

Sabrina Albea: /* Popup window launched from your website */

2014-05-15T09:19:02Z

‎Popup window launched from your website

Sabrina Albea: /* The remote license engine application */

2014-05-15T09:15:46Z

‎The remote license engine application

CC Wiki Bot: Undo revision 81888 by Jaxaza (talk)

2014-04-19T03:24:04Z

Undo revision 81888 by Jaxaza (talk)

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Jaxaza

2013-09-25T15:04:23Z

Reverted edits by Beritaharian (talk) to last revision by Jaxaza

Beritaharian at 09:33, 25 September 2013

2013-09-25T09:33:41Z

Jaxaza: /* Part 2: Processing and Storage of license information */

2013-08-22T03:09:34Z

‎Part 2: Processing and Storage of license information

Mike Linksvayer: Undo revision 55205 by Halobigred (talk)

2012-07-20T21:32:04Z

Undo revision 55205 by Halobigred (talk)

Mike Linksvayer: Reverted edits by BurnsideRinehart (talk) to last revision by Halobigred

2012-07-20T21:23:07Z

Reverted edits by BurnsideRinehart (talk) to last revision by Halobigred

BurnsideRinehart at 09:37, 16 July 2012

2012-07-16T09:37:05Z

Halobigred: /* Part 2: Processing and Storage of license information */

2012-02-10T06:16:45Z

‎Part 2: Processing and Storage of license information

@@ Line 84: / Line 84: @@
 * Launched via HTML control within your desktop application
-=== Popup window launched from your website ===
+[http://www.example.com link title]'''
 The most popular method of invoking the remote license engine is via a popup window. A user clicks something on a page that launches a small window containing the questions. After answering them, users proceed, the window closes, and the original page is updated to reflect their choice. Sites using this method will usually change a hidden form variable dynamically (using javascript) when the user finishes the license selection process.

@@ Line 18: / Line 18: @@
 Whether your software is a website or a downloadable application, the first step to integrating Creative Commons licenses is letting users select a license directly from your software. The process involves loading a simplified Creative Commons license interface from within a popup window, embedded into your website, or launched from an HTML window control in your application. URL variables are read into the page and are appended when complete, allowing data to be extracted from the process and passed through it.
-==== The remote license engine application ====
+==== The remote license engine ap=plication ====
 The heart of the process is running the remote license interface which is available at this URL:
@@ Line 30: / Line 30: @@
 '''partner (required):''' The name of your application or site, used for tracking usage at Creative Commons. Any descriptive name can be added here.
-'''exit_url (required):''' The return URL on your application that will load after a user selects a license and will contain appended variables in the URL that your software will need to read.
+'''exit_url (required):''' The return URL on your application that will lo ad af ter a user selects a license and will contain appended variables in the URL that your software w-ill need to read.
 '''additional requirement:'''

← Older revision		Revision as of 03:24, 19 April 2014
Line 124:		Line 124:
	If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.		If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.

−	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and storage options. [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]	+	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and storage options.

@@ Line 6: / Line 6: @@
 ''Integrating Creative Commons licenses into your web application''
-While Creative Commons offers a range of license choices and public domain options direct from its license page, if you have created an application or built a website that allow people to contribute works you may prefer to integrate the license engine directly into your site or application. This guide serves to explain all the steps necessary and options available for integrating Creative Commons into your software.  If you are integrating Creative Commons licenses with a non-web application, or would like more control over the user interface, the [[Creative Commons Web Services]] may be more appropriate and rewards to [http://www.liputan6.com/ berita hari ini] Liputan6.com
+While Creative Commons offers a range of license choices and public domain options direct from its license page, if you have created an application or built a website that allow people to contribute works you may prefer to integrate the license engine directly into your site or application. This guide serves to explain all the steps necessary and options available for integrating Creative Commons into your software.  If you are integrating Creative Commons licenses with a non-web application, or would like more control over the user interface, the [[Creative Commons Web Services]] may be more appropriate.
 This guide is generally split into three parts:

@@ Line 6: / Line 6: @@
 ''Integrating Creative Commons licenses into your web application''
-While Creative Commons offers a range of license choices and public domain options direct from its license page, if you have created an application or built a website that allow people to contribute works you may prefer to integrate the license engine directly into your site or application. This guide serves to explain all the steps necessary and options available for integrating Creative Commons into your software.  If you are integrating Creative Commons licenses with a non-web application, or would like more control over the user interface, the [[Creative Commons Web Services]] may be more appropriate.
+While Creative Commons offers a range of license choices and public domain options direct from its license page, if you have created an application or built a website that allow people to contribute works you may prefer to integrate the license engine directly into your site or application. This guide serves to explain all the steps necessary and options available for integrating Creative Commons into your software.  If you are integrating Creative Commons licenses with a non-web application, or would like more control over the user interface, the [[Creative Commons Web Services]] may be more appropriate and rewards to [http://www.liputan6.com/ berita hari ini] Liputan6.com
 This guide is generally split into three parts:

← Older revision		Revision as of 03:09, 22 August 2013
Line 124:		Line 124:
	If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.		If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.

−	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and storage options.	+	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and storage options. [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]

← Older revision		Revision as of 21:32, 20 July 2012
Line 124:		Line 124:
	If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.		If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.

−	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and ~~[http://www.rentittoday.com/storage-units-rentals~~ storage options].	+	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and storage options.

← Older revision		Revision as of 06:16, 10 February 2012
Line 124:		Line 124:
	If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.		If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.

−	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and storage options.	+	This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and [http://www.rentittoday.com/storage-units-rentals storage options].