OSBW Definition - Revision history

Johnmiedema: Replacing page with 'This page can be deleted'

2009-02-22T16:00:02Z

Replacing page with 'This page can be deleted'

Ch at 13:15, 6 February 2009

2009-02-06T13:15:32Z

Johnmiedema at 18:58, 12 January 2009

2009-01-12T18:58:25Z

Johnmiedema at 13:40, 12 January 2009

2009-01-12T13:40:20Z

Johnmiedema at 13:39, 12 January 2009

2009-01-12T13:39:46Z

Johnmiedema at 12:58, 12 January 2009

2009-01-12T12:58:50Z

Johnmiedema: New page: what are open source book widgets? what is the scope of applicable projects?

2009-01-08T00:37:15Z

New page: what are open source book widgets? what is the scope of applicable projects?

New page

what are open source book widgets? what is the scope of applicable projects?

@@ Line 1: / Line 1: @@
-[[Open_Source_Book_Widgets|OSBW Main Page]]
+This page can be deleted
-−
-The following provides a definition of open source book widgets. It is useful for defining the scope of the collaboration.
-−
-Book widgets are small programs that provide book related functions, e.g., show a book cover, link to book details, show book availability.
-−
-* Widget is a generic term for plugins, modules and other similar software components.
-−
-* Widgets often have a graphical interface, e.g., book cover image, links.
-−
-* They often reside on web pages and so are distributed across the web. This is an interesting feature, as it may affect search results for books.
-−
-* They often call one or more servers for their data., e.g., Amazon, Google, LibraryThing, Open Library, WorldCat.
-−
-* The programs tend to be specific to a platform, e.g., WordPress, Drupal, Firefox. Server platforms such as WordPress and Drupal require the website author to install the widget; all users can see the widget. Client platforms such as Firefox require the user to install the widget; only users who have installed the plugin can see the widget.
-−
-* Widgets are portable. They are easily embedded or modified in their target environment.
-−
-* Widgets may accept user input, e.g., configuration for a particular book data source or library.
-−
-* Widgets may be able to interact with each other to provide enhanced functionality.
-−
-* There are many book widgets available on the web, but many of them are closed source. The current collaboration is particularly interested in open source book widgets. There are many different open source licenses, but for the current purpose of collaboration, the more open the license the better. The [http://www.gnu.org/licenses/licenses.html#GPL GNU General Public License] is a good example of an open license.
-−
-[[Category:Open Source Book Widgets]]

← Older revision		Revision as of 13:15, 6 February 2009
Line 22:		Line 22:

	* There are many book widgets available on the web, but many of them are closed source. The current collaboration is particularly interested in open source book widgets. There are many different open source licenses, but for the current purpose of collaboration, the more open the license the better. The [http://www.gnu.org/licenses/licenses.html#GPL GNU General Public License] is a good example of an open license.		* There are many book widgets available on the web, but many of them are closed source. The current collaboration is particularly interested in open source book widgets. There are many different open source licenses, but for the current purpose of collaboration, the more open the license the better. The [http://www.gnu.org/licenses/licenses.html#GPL GNU General Public License] is a good example of an open license.
		+
		+	[[Category:Open Source Book Widgets]]

@@ Line 13: / Line 13: @@
 * They often call one or more servers for their data., e.g., Amazon, Google, LibraryThing, Open Library, WorldCat.
-* The programs tend to be specific to a platform, e.g., WordPress, Drupal, Firefox. Platforms such as WordPress and Drupal require the website author to install the widget; all users can see the widget. Platforms such as Firefox require the user to install the widget; only users who have installed the plugin can see the widget.
+* The programs tend to be specific to a platform, e.g., WordPress, Drupal, Firefox. Server platforms such as WordPress and Drupal require the website author to install the widget; all users can see the widget. Client platforms such as Firefox require the user to install the widget; only users who have installed the plugin can see the widget.
 * Widgets are portable. They are easily embedded or modified in their target environment.

@@ Line 1: / Line 1: @@
 [[Open_Source_Book_Widgets|OSBW Main Page]]
-The following provides a definition of open source book widgets. It is useful for defining the scope of the collaboration. Please feel invited to continue editing the definition.
+The following provides a definition of open source book widgets. It is useful for defining the scope of the collaboration.
 Book widgets are small programs that provide book related functions, e.g., show a book cover, link to book details, show book availability.

← Older revision		Revision as of 13:39, 12 January 2009
Line 1:		Line 1:
	[[Open_Source_Book_Widgets\|OSBW Main Page]]		[[Open_Source_Book_Widgets\|OSBW Main Page]]

−	~~what are~~ open source book widgets~~? what~~ is the scope of ~~applicable projects?~~	+	The following provides a definition of open source book widgets. It is useful for defining the scope of the collaboration. Please feel invited to continue editing the definition.
		+
		+	Book widgets are small programs that provide book related functions, e.g., show a book cover, link to book details, show book availability.
		+
		+	* Widget is a generic term for plugins, modules and other similar software components.
		+
		+	* Widgets often have a graphical interface, e.g., book cover image, links.
		+
		+	* They often reside on web pages and so are distributed across the web. This is an interesting feature, as it may affect search results for books.
		+
		+	* They often call one or more servers for their data., e.g., Amazon, Google, LibraryThing, Open Library, WorldCat.
		+
		+	* The programs tend to be specific to a platform, e.g., WordPress, Drupal, Firefox. Platforms such as WordPress and Drupal require the website author to install the widget; all users can see the widget. Platforms such as Firefox require the user to install the widget; only users who have installed the plugin can see the widget.
		+
		+	* Widgets are portable. They are easily embedded or modified in their target environment.
		+
		+	* Widgets may accept user input, e.g., configuration for a particular book data source or library.
		+
		+	* Widgets may be able to interact with each other to provide enhanced functionality.
		+
		+	* There are many book widgets available on the web, but many of them are closed source. The current collaboration is particularly interested in open source book widgets. There are many different open source licenses, but for the current purpose of collaboration, the more open the license the better. The [http://www.gnu.org/licenses/licenses.html#GPL GNU General Public License] is a good example of an open license.

← Older revision		Revision as of 12:58, 12 January 2009
Line 1:		Line 1:
		+	[[Open_Source_Book_Widgets\|OSBW Main Page]]
		+
	what are open source book widgets? what is the scope of applicable projects?		what are open source book widgets? what is the scope of applicable projects?