Representational State Transfer - Revision history

Neteler: +cat

2008-02-04T06:58:36Z

+cat

Arnulf at 09:36, 24 December 2007

2007-12-24T09:36:37Z

Wiki-JoWalsh: /* Further Reading */

2007-11-09T08:46:24Z

Further Reading

Wiki-JoWalsh: /* Further Reading */

2007-11-09T08:45:40Z

Further Reading

Arnulf: /* Further Reading */

2007-09-03T19:20:24Z

Further Reading

Arnulf: /* Further Reading */

2007-09-02T10:21:31Z

Further Reading

Arnulf: added "RESTful Web Services" for further reading

2007-09-02T10:20:33Z

added "RESTful Web Services" for further reading

Arnulf: /* Testing and Experimenting */

2007-07-24T10:32:50Z

Testing and Experimenting

Arnulf: /* Testing and Experimenting */

2007-07-14T10:06:32Z

Testing and Experimenting

Arnulf: /* Testing and Experimenting */

2007-07-14T10:03:52Z

Testing and Experimenting

← Older revision		Revision as of 06:58, 4 February 2008
Line 31:		Line 31:
	=== Mapbender ===		=== Mapbender ===
	The Mapbender project was urged by some customers to look into implementing [[SOAP]] bindings for OGC standards because some industries communicated that this is the only way to implement security required for [[Digital Restrictions Management]] for geodata. During the [http://www.mapbender.org/index.php/Mapbender_Development_Sprint developer meeting in May 2007] it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST		The Mapbender project was urged by some customers to look into implementing [[SOAP]] bindings for OGC standards because some industries communicated that this is the only way to implement security required for [[Digital Restrictions Management]] for geodata. During the [http://www.mapbender.org/index.php/Mapbender_Development_Sprint developer meeting in May 2007] it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST
		+
		+	[[Category: Standards]]

@@ Line 1: / Line 1: @@
 Representational State Transfer is also known as ''REST'' and ''RESTful''.
-There is an ongoing discussion in the standards world whether or not to adopt [[SOAP]] or RESTful approaches as the unique truth to achieve interoperable happiness. OSGeo will probably not go either way but look at both and collect some useful information here on these pages.
+There is an ongoing discussion in the standards world whether to adopt [[SOAP]] as the unique interoperable binding. Because this decision might be detrimental to RESTful design approaches the discussion sometimes turns into a fight between SOAP '''or''' REST as if the two could be compared. But they cannot as one is a technology and the other a design approach. It is possible to implement RESTful services using SOAP bindings and the current version of the WSDL standard has explicitly been modified to allow for RESTful implementations.
 == Introduction ==

@@ Line 21: / Line 21: @@
 Commentary by OSGeo members:
-* http://crschmidt.net/blog/archives/275/what-rest-is-really-about/
+* http://crschmidt.net/blog/archives/275/what-rest-is-really-about/ - Chris Schmidt
-* http://geotips.blogspot.com/2007/08/rest-without-resources.html
+* http://geotips.blogspot.com/2007/08/rest-without-resources.html - Paul Ramsey
 == Testing and Experimenting ==

← Older revision		Revision as of 08:45, 9 November 2007
Line 18:		Line 18:

	Excellent introduction to the RESTful architecture. Must-read for web mapping developers.		Excellent introduction to the RESTful architecture. Must-read for web mapping developers.
		+
		+	Commentary by OSGeo members:
		+
		+	* http://crschmidt.net/blog/archives/275/what-rest-is-really-about/
		+	* http://geotips.blogspot.com/2007/08/rest-without-resources.html

	== Testing and Experimenting ==		== Testing and Experimenting ==

@@ Line 11: / Line 11: @@
 == Further Reading ==
 Leonard Richardson, Sam Ruby: RESTful Web Services, Sebastopol, 2007
 * ISBN 10: 0-596-52926-0

← Older revision		Revision as of 10:20, 2 September 2007
Line 9:		Line 9:

	''REST strictly refers to a collection of network architecture principles that outline how resources are defined and addressed. The term is often used in a looser sense to describe any simple interface that transmits domain-specific data over HTTP without an additional messaging layer such as [[SOAP]] or session tracking via HTTP cookies. These two meanings can conflict as well as overlap.''		''REST strictly refers to a collection of network architecture principles that outline how resources are defined and addressed. The term is often used in a looser sense to describe any simple interface that transmits domain-specific data over HTTP without an additional messaging layer such as [[SOAP]] or session tracking via HTTP cookies. These two meanings can conflict as well as overlap.''
		+
		+	== Further Reading ==
		+	Leonard Richardson, Sam Ruby: RESTful Web Services, Sebastopol, 2007
		+	* ISBN 10: 0-596-52926-0
		+	* ISBN 13: 9780596529260

	== Testing and Experimenting ==		== Testing and Experimenting ==

← Older revision		Revision as of 10:32, 24 July 2007
Line 11:		Line 11:

	== Testing and Experimenting ==		== Testing and Experimenting ==
		+
		+	=== FeatureServer ===
		+	http://featureserver.org/ with OpenLayers by MetaCarta
		+
		+	=== Mapbender ===
	The Mapbender project was urged by some customers to look into implementing [[SOAP]] bindings for OGC standards because some industries communicated that this is the only way to implement security required for [[Digital Restrictions Management]] for geodata. During the [http://www.mapbender.org/index.php/Mapbender_Development_Sprint developer meeting in May 2007] it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST		The Mapbender project was urged by some customers to look into implementing [[SOAP]] bindings for OGC standards because some industries communicated that this is the only way to implement security required for [[Digital Restrictions Management]] for geodata. During the [http://www.mapbender.org/index.php/Mapbender_Development_Sprint developer meeting in May 2007] it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST

← Older revision		Revision as of 10:06, 14 July 2007
Line 11:		Line 11:

	== Testing and Experimenting ==		== Testing and Experimenting ==
−	The Mapbender project was urged by some customers to look into implementing [[SOAP]] bindings for OGC standards because some industries communicated that this is the only way to implement security required for [[Digital Restrictions Management]] for geodata. During the developer meeting in May it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST	+	The Mapbender project was urged by some customers to look into implementing [[SOAP]] bindings for OGC standards because some industries communicated that this is the only way to implement security required for [[Digital Restrictions Management]] for geodata. During the [http://www.mapbender.org/index.php/Mapbender_Development_Sprint developer meeting in May 2007] it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST

← Older revision		Revision as of 10:03, 14 July 2007
Line 11:		Line 11:

	== Testing and Experimenting ==		== Testing and Experimenting ==
		+	The Mapbender project was urged by some customers to look into implementing [[SOAP]] bindings for OGC standards because some industries communicated that this is the only way to implement security required for [[Digital Restrictions Management]] for geodata. During the developer meeting in May it was discussed that this can be done once there is funding available and that the project should also look into RESTful approaches. Further information of any results will be made available on the project pages: http://www.mapbender.org/index.php/SOAP_vs_REST