OSBW Statement of Interests - Revision history

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

2009-02-22T15:59:21Z

Replacing page with 'This page can be deleted'

Ch at 13:16, 6 February 2009

2009-02-06T13:16:34Z

Johnmiedema at 13:52, 12 January 2009

2009-01-12T13:52:31Z

Johnmiedema at 12:57, 12 January 2009

2009-01-12T12:57:34Z

Johnmiedema at 12:56, 12 January 2009

2009-01-12T12:56:13Z

Johnmiedema: New page: Statement of Interests - wide open list of things that interest people

2009-01-08T00:33:38Z

New page: Statement of Interests - wide open list of things that interest people

New page

Statement of Interests - wide open list of things that interest people

@@ Line 1: / Line 1: @@
-[[Open_Source_Book_Widgets|OSBW Main Page]]
+This page can be deleted
-−
-A number of people have expressed an interest in collaborating on open source book widgets. It makes sense to pool resources, but doing so takes a bit of coordination. An easy place to start is to collect a list of general interests in open source book widgets.
-−
-Please provide a short statement of your interest in open source book widgets. What brought you here? What would you like to see come out of this? Any ideas about where collaboration is needed in particular?
-−
-=== Independent/Alternative Sources ===
-−
-There are many book widgets available on the web, but they mostly use commercial data sources like Amazon which are hardly representative of the independent and alternative materials available on the web. There is a professional library issue in providing access to these materials. --[[User:Johnmiedema|Johnmiedema]] 05:52, 12 January 2009 (PST)
-−
-=== Shared Modules ===
-−
-Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. The OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. --[[User:Johnmiedema|Johnmiedema]] 05:52, 12 January 2009 (PST)
-−
-[[Category:Open Source Book Widgets]]

← Older revision		Revision as of 13:16, 6 February 2009
Line 12:		Line 12:

	Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. The OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. --[[User:Johnmiedema\|Johnmiedema]] 05:52, 12 January 2009 (PST)		Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. The OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. --[[User:Johnmiedema\|Johnmiedema]] 05:52, 12 January 2009 (PST)
		+
		+	[[Category:Open Source Book Widgets]]

@@ Line 4: / Line 4: @@
 Please provide a short statement of your interest in open source book widgets. What brought you here? What would you like to see come out of this? Any ideas about where collaboration is needed in particular?
 === Shared Modules ===
-Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. The OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. John Miedema
+Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. The OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. --[[User:Johnmiedema|Johnmiedema]] 05:52, 12 January 2009 (PST)

@@ Line 3: / Line 3: @@
 A number of people have expressed an interest in collaborating on open source book widgets. It makes sense to pool resources, but doing so takes a bit of coordination. An easy place to start is to collect a list of general interests in open source book widgets.
-Please provide a short statement of your interest in open source book widgets. What brought you here? What would you like to see come out of this? Any ideas about where collaboration is needed in particular? Please include your name with your statement.
+Please provide a short statement of your interest in open source book widgets. What brought you here? What would you like to see come out of this? Any ideas about where collaboration is needed in particular?
 === Shared Modules ===
-Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. My OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. John Miedema
+Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. The OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. John Miedema

← Older revision		Revision as of 12:56, 12 January 2009
Line 1:		Line 1:
−	~~Statement~~ of ~~Interests - wide~~ open list of things that ~~interest people~~	+	[[Open_Source_Book_Widgets\|OSBW Main Page]]
		+
		+	A number of people have expressed an interest in collaborating on open source book widgets. It makes sense to pool resources, but doing so takes a bit of coordination. An easy place to start is to collect a list of general interests in open source book widgets.
		+
		+	Please provide a short statement of your interest in open source book widgets. What brought you here? What would you like to see come out of this? Any ideas about where collaboration is needed in particular? Please include your name with your statement.
		+
		+	=== Shared Modules ===
		+
		+	Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. My OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. John Miedema