Content Creation Applications - Revision history

Nathan Yergler: Redirecting to Developer Challenges

2008-03-04T18:58:17Z

Redirecting to Developer Challenges

Pj at 14:12, 18 October 2007

2007-10-18T14:12:58Z

Nathan Yergler at 18:50, 21 September 2007

2007-09-21T18:50:52Z

Mike Linksvayer: /* Build licensing into web content applications */

2006-08-02T19:32:10Z

‎Build licensing into web content applications

Jon Phillips: /* Open source application support for XMP and Creative Commons license info */

2006-05-02T18:01:20Z

‎Open source application support for XMP and Creative Commons license info

Jon Phillips at 17:59, 2 May 2006

2006-05-02T17:59:54Z

Jon Phillips at 05:13, 1 May 2006

2006-05-01T05:13:00Z

Jon Phillips at 22:25, 30 April 2006

2006-04-30T22:25:48Z

Jon Phillips: /* Open source application support for XMP and Creative Commons license info */

2006-04-30T21:32:57Z

‎Open source application support for XMP and Creative Commons license info

Jon Phillips: /* Build Creative Commons licensing into more content creation applications */

2006-04-30T21:32:26Z

‎Build Creative Commons licensing into more content creation applications

← Older revision		Revision as of 18:58, 4 March 2008
Line 1:		Line 1:
−	[[~~Category:~~Developer Challenges]]	+	#REDIRECT [[Developer Challenges]]
−	~~[[Category:Developer]]~~
−	~~[[Category:Technology]]~~
−	~~{{incomplete}}~~
−	~~{{SMW}}~~
−
−	~~== [[GUI for web content creation application generating HTML pages with RDF linking Creative Commons contents]] ==~~
−
−	A GUI for web content creation application to build a single HTML page with float panel linking Creative Commons contents from all CC reporitories. The author can browse previews of all the contents searching by tags.
−	~~The HTML generated code contains all the microformats data (RDF) for attribution and licenses of all the authors of the contents used.~~
−
−	~~== [[Build Creative Commons licensing into more content creation applications]] ==~~
−
−	We have a [[Applications Using CC\|list of existing applications]] that allow users to choose a Creative Commons license for content created within the applications. Any application in which a user creates "content" is a candidate, from multimedia authoring systems to weblog publishing software. We've made it easy to offer Creative Commons licenses to users (See [[Choose License\|Choose License Page]]. Please see [[Build Creative Commons licensing into more content creation applications]].
−
−	~~== [[Build licensing into web content applications]] ==~~
−
−	The moment of content creation is the sweet spot for CC assignment. Imagine if the top 10 authoring tools (blogs, wikis, cmses, etc) all shipped with proper CC support... even if a small fraction of site administrators enabled this feature, the ammount of content which would be assigned CC licenses a decade from now would be staggering. Pick a project - [http://opensourcecms.org opensourcecms] ([[WpLicense\|wordpress]], nuke, cmses, [http://drupal.org/node/17497 drupal], [http://plone.org/products/plone/roadmap/136 Plone], etc.). Please see [[Build licensing into web content applications]].
−
−	~~== [[GUI for embedding license claims in files and generating claim verification RDF]] ==~~
−
−	We have a [http://cctools.sourceforge.net/ command line tool] that embeds license claims in [[MP3]] and [[OGG]] files and generates claim verification for these files according to our [[Embedded Metadata\|license metadata embedding guidelines]]. We need a GUI version of this tool (or versions, for different platforms). The most basic implementation would allow a user to choose a file, enter some information (at least copyright holder, license chosen, and URL of the page that will verify the embedded claim), embed the claim in the file, and display verification RDF for copy&paste into the verification web page. More sophisticated implementations might help a user manage their tagged files or interface with specific web publishing systems to make publishing verification metadata transparent. Please see the detail page: [[GUI for embedding license claims in files and generating claim verification RDF]].

@@ Line 4: / Line 4: @@
 {{incomplete}}
 {{SMW}}
 == [[Build Creative Commons licensing into more content creation applications]] ==

@@ Line 3: / Line 3: @@
 [[Category:Technology]]
 {{incomplete}}
 == [[Build Creative Commons licensing into more content creation applications]] ==

@@ Line 10: / Line 10: @@
 == [[Build licensing into web content applications]] ==
-The moment of content creation is the sweet spot for CC assignment. Imagine if the top 10 authoring tools (blogs, wikis, cmses, etc) all shipped with proper CC support... even if a small fraction of site administrators enabled this feature, the ammount of content which would be assigned CC licenses a decade from now would be staggering. Pick a project - [http://opensourcecms.org opensourcecms] (wordpress, *nuke*, cmses, drupal, [http://plone.org/products/plone/roadmap/136 Plone], etc.). Please see [[Build licensing into web content applications]].
+The moment of content creation is the sweet spot for CC assignment. Imagine if the top 10 authoring tools (blogs, wikis, cmses, etc) all shipped with proper CC support... even if a small fraction of site administrators enabled this feature, the ammount of content which would be assigned CC licenses a decade from now would be staggering. Pick a project - [http://opensourcecms.org opensourcecms] ([[WpLicense|wordpress]], *nuke*, cmses, [http://drupal.org/node/17497 drupal], [http://plone.org/products/plone/roadmap/136 Plone], etc.). Please see [[Build licensing into web content applications]].
 == [[GUI for embedding license claims in files and generating claim verification RDF]] ==
 We have a [http://cctools.sourceforge.net/ command line tool] that embeds license claims in [[MP3]] and [[OGG]] files and generates claim verification for these files according to our [[Embedded Metadata|license metadata embedding guidelines]]. We need a GUI version of this tool (or versions, for different platforms). The most basic implementation would allow a user to choose a file, enter some information (at least copyright holder, license chosen, and URL of the page that will verify the embedded claim), embed the claim in the file, and display verification RDF for copy&paste into the verification web page. More sophisticated implementations might help a user manage their tagged files or interface with specific web publishing systems to make publishing verification metadata transparent. Please see the detail page: [[GUI for embedding license claims in files and generating claim verification RDF]].

@@ Line 12: / Line 12: @@
 The moment of content creation is the sweet spot for CC assignment. Imagine if the top 10 authoring tools (blogs, wikis, cmses, etc) all shipped with proper CC support... even if a small fraction of site administrators enabled this feature, the ammount of content which would be assigned CC licenses a decade from now would be staggering. Pick a project - [http://opensourcecms.org opensourcecms] (wordpress, *nuke*, cmses, drupal, [http://plone.org/products/plone/roadmap/136 Plone], etc.). Please see [[Build licensing into web content applications]].
-== [[Open source application support for XMP and Creative Commons license info]] ==
 == [[GUI for embedding license claims in files and generating claim verification RDF]] ==
 We have a [http://cctools.sourceforge.net/ command line tool] that embeds license claims in [[MP3]] and [[OGG]] files and generates claim verification for these files according to our [[Embedded Metadata|license metadata embedding guidelines]]. We need a GUI version of this tool (or versions, for different platforms). The most basic implementation would allow a user to choose a file, enter some information (at least copyright holder, license chosen, and URL of the page that will verify the embedded claim), embed the claim in the file, and display verification RDF for copy&paste into the verification web page. More sophisticated implementations might help a user manage their tagged files or interface with specific web publishing systems to make publishing verification metadata transparent. Please see the detail page: [[GUI for embedding license claims in files and generating claim verification RDF]].

@@ Line 6: / Line 6: @@
 == [[Build Creative Commons licensing into more content creation applications]] ==
-We have a [[Applications Using CC|list of existing applications]] that allow users to choose a Creative Commons license for content created within the applications. Any application in which a user creates "content" is a candidate, from multimedia authoring systems to weblog publishing software. We've made it easy to offer Creative Commons licenses to users via our [http://creativecommons.org/technology/developerdocs satellite licensing interface]. Please see [[Build Creative Commons licensing into more content creation applications]].
+We have a [[Applications Using CC|list of existing applications]] that allow users to choose a Creative Commons license for content created within the applications. Any application in which a user creates "content" is a candidate, from multimedia authoring systems to weblog publishing software. We've made it easy to offer Creative Commons licenses to users (See [[Choose License|Choose License Page]]. Please see [[Build Creative Commons licensing into more content creation applications]].
 == [[Build licensing into web content applications]] ==

@@ Line 1: / Line 1: @@
-[[Category:Tech Challenges]]
+[[Category:Developer Challenges]]
 [[Category:Developer]]
 [[Category:Technology]]

← Older revision		Revision as of 22:25, 30 April 2006
Line 13:		Line 13:

	== [[Open source application support for XMP and Creative Commons license info]] ==		== [[Open source application support for XMP and Creative Commons license info]] ==
		+
		+	== [[GUI for embedding license claims in files and generating claim verification RDF]] ==
		+
		+	We have a [http://cctools.sourceforge.net/ command line tool] that embeds license claims in [[MP3]] and [[OGG]] files and generates claim verification for these files according to our [[Embedded Metadata\|license metadata embedding guidelines]]. We need a GUI version of this tool (or versions, for different platforms). The most basic implementation would allow a user to choose a file, enter some information (at least copyright holder, license chosen, and URL of the page that will verify the embedded claim), embed the claim in the file, and display verification RDF for copy&paste into the verification web page. More sophisticated implementations might help a user manage their tagged files or interface with specific web publishing systems to make publishing verification metadata transparent. Please see the detail page: [[GUI for embedding license claims in files and generating claim verification RDF]].

← Older revision		Revision as of 21:32, 30 April 2006
Line 12:		Line 12:
	The moment of content creation is the sweet spot for CC assignment. Imagine if the top 10 authoring tools (blogs, wikis, cmses, etc) all shipped with proper CC support... even if a small fraction of site administrators enabled this feature, the ammount of content which would be assigned CC licenses a decade from now would be staggering. Pick a project - [http://opensourcecms.org opensourcecms] (wordpress, nuke, cmses, drupal, [http://plone.org/products/plone/roadmap/136 Plone], etc.). Please see [[Build licensing into web content applications]].		The moment of content creation is the sweet spot for CC assignment. Imagine if the top 10 authoring tools (blogs, wikis, cmses, etc) all shipped with proper CC support... even if a small fraction of site administrators enabled this feature, the ammount of content which would be assigned CC licenses a decade from now would be staggering. Pick a project - [http://opensourcecms.org opensourcecms] (wordpress, nuke, cmses, drupal, [http://plone.org/products/plone/roadmap/136 Plone], etc.). Please see [[Build licensing into web content applications]].

−	== Open source application support for XMP and Creative Commons license info ==	+	== [[Open source application support for XMP and Creative Commons license info]] ==
−
−	~~=== Implementations ===~~
−
−	* [[XMP]] ~~is an open, RDF-based format that can embed metadata in PDF files. Currently only [[XMP Help\|Adobe applications~~]~~] support such embedding. Similar [[XMP]] and Creative Commons support should be added to [http://www.openoffice.org/ Open Office] and other open source document creation applications.~~
−
−	* Maarten Sneep has created a [http://www.math.utah.edu/tex-archive/macros/latex/contrib/xmpincl/ macro] for embedding XMP in files created by pdflatex.
−
−	=== ~~TODO~~ ===
−
−	* Retire and split between embedding and content creation apps