Web service: Difference between revisions
Jump to navigation
Jump to search
m (using an external editor) |
m (using an external editor) |
||
| Line 2: | Line 2: | ||
== Definition == | == Definition == | ||
According to [http://en.wikipedia.org/wiki/Web_service Wikipedia] (retrieved 19: | According to [http://en.wikipedia.org/wiki/Web_service Wikipedia] (retrieved 19:47, 23 April 2007 (MEST)), the W3C defines a Web service as a software system designed to support interoperable Machine to Machine interaction over a network. Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services. | ||
== Web services stack == | == Web services stack == | ||
Things do get complicated, e.g. here is a probably wrong example webservice "stack" made up from the very little I know | Things do get complicated, e.g. here is a probably wrong example webservice "stack" made up from the very little I know. - [[User:Daniel K. Schneider|Daniel K. Schneider]]. | ||
* [http://www.w3.org/TR/SOAP/ Simple Object Access Protocol (SOAP) 1.1], W3C note. "SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses". Note DKS: This is generally the lowest Service Layer (just on top of HTTP) and tells how to describe messages that are sent or received. | * [http://www.w3.org/TR/SOAP/ Simple Object Access Protocol (SOAP) 1.1], W3C note. "SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses". Note DKS: This is generally the lowest Service Layer (just on top of HTTP) and tells how to describe messages that are sent or received. | ||
| Line 19: | Line 17: | ||
* [http://www.oasis-open.org/committees/wsrp/ WSRP (Web Services for Remote Portals)]<nowiki>: XML and Web services standard that will allow the plug-n-play of visual, user-facing Web services with portals or other intermediary Web applications. (Oasis led initiative)</nowiki> | * [http://www.oasis-open.org/committees/wsrp/ WSRP (Web Services for Remote Portals)]<nowiki>: XML and Web services standard that will allow the plug-n-play of visual, user-facing Web services with portals or other intermediary Web applications. (Oasis led initiative)</nowiki> | ||
* [http://ebxml.org/ ebXML Messaging Service Specification ] (OASIS led) provides a secure method for exchanging electronic business transactions using the Internet. (This is a rather big project with several sub-specifications). See D. Mertz [http://www-106.ibm.com/developerworks/xml/library/x-ebxml/ "Understanding ebXML"] at developerworks/IBM. | * [http://ebxml.org/ ebXML Messaging Service Specification ] (OASIS led) provides a secure method for exchanging electronic business transactions using the Internet. (This is a rather big project with several sub-specifications). See D. Mertz [http://www-106.ibm.com/developerworks/xml/library/x-ebxml/ "Understanding ebXML"] at developerworks/IBM. | ||
== Webservices in education == | |||
=== Rehak et al. model === | |||
{{quotation | The era of monolithic Learning Technology Systems is over. Rather than building large, closed systems, the current focus is on flexible architectures that provide interoperability of components and learning content, and that rely on open standards for information exchange and component integration. The Learning Systems Architecture Lab has developed the concept of a Learning Services Architecture and the Learning Services Stack as a framework for developing the next generation of learning technology systems. We're in the process of developing learning services using Web services and Web services technologies.}} (http://lsal.org/, retrieved 19:47, 23 April 2007 (MEST)). | |||
( HTTP -> ) SOAP -> UDDI -> WSDL | WSIF ? -> WSFL ? -> -> ebXML? | WSIL ? -> WSRP? -> Portal | |||
== Players == | == Players == | ||
There are many players in this field | : There are many players in this field | ||
* The [http://www.w3.org/2002/ws/Activity Web Services Activity Statement and ]the [http://www.w3.org/2002/ws/ Web Services Activity] give an overview of the W3's idea on application to application communication (web services). See also: [http://www.w3.org/TR/ws-desc-reqs/ Web Services Description Requirements] and [http://www.w3.org/TR/ws-gloss/ the Web Services Glossary]. | * The [http://www.w3.org/2002/ws/Activity Web Services Activity Statement and ]the [http://www.w3.org/2002/ws/ Web Services Activity] give an overview of the W3's idea on application to application communication (web services). See also: [http://www.w3.org/TR/ws-desc-reqs/ Web Services Description Requirements] and [http://www.w3.org/TR/ws-gloss/ the Web Services Glossary]. | ||
| Line 28: | Line 38: | ||
* [http://msdn.microsoft.com/webservices/understanding/whatsnext/default.aspx "What's Next: The Future of Web Services"] from Microsoft | * [http://msdn.microsoft.com/webservices/understanding/whatsnext/default.aspx "What's Next: The Future of Web Services"] from Microsoft | ||
* [http://www.xmethods.com/ XMethods] has a long list of publicly available web services , implementations, tutorials, etc. | * [http://www.xmethods.com/ XMethods] has a long list of publicly available web services , implementations, tutorials, etc. | ||
; In educational technology | |||
* [http://lsal.org/ Learning Systems Architecture Lab] | |||
== Links == | == Links == | ||
| Line 33: | Line 46: | ||
; Standards and recommendations | ; Standards and recommendations | ||
[http://www.w3.org/TR/ws-arch/ Web Services Architecture] (W3C Working Group Note 11 February 2004) | * [http://www.w3.org/TR/ws-arch/ Web Services Architecture] (W3C Working Group Note 11 February 2004) | ||
; For education | |||
* Dig around [http://lsal.org/ lsal.org] | |||
* The infamous learning services stack diagram [[http://lsal.org/lsal/diagramlibrary/stackarchitecture/stack.pdf PDF] PDF] | |||
; Other | ; Other | ||
| Line 44: | Line 61: | ||
== References == | == References == | ||
* Blackmon, William H. and Daniel R. Rehak (2003). Customized Learning: A Web Services Approach HTML, Proceedings: Ed-Media 2003, June 2003. [http://141.225.40.64/lsal/expertise/papers/conference/edmedia2003/customized20030625.html HTML] - [http://141.225.40.64/lsal/expertise/papers/conference/edmedia2003/process20030625.pdf PDF] (available from http://lsal.org/lsal/expertise/papers/). | |||
* Wilson, Scott; Kerry Blinco and Daniel Rehak (2004). An e-Learning Framework: A Summary, [http://www.imsglobal.org/altilab/ alt-i-lab 2004:Advancing Learning Technology Interoperability], [http://141.225.40.64/lsal/expertise/papers/notes/serviceframeworks/elf20040720/elfsummary-20040720.pdf PDF] | |||
[[Category: technologies]] | [[Category: technologies]] | ||
[[Category: XML]] | [[Category: XML]] | ||
Revision as of 19:47, 23 April 2007
Definition
According to Wikipedia (retrieved 19:47, 23 April 2007 (MEST)), the W3C defines a Web service as a software system designed to support interoperable Machine to Machine interaction over a network. Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services.
Web services stack
Things do get complicated, e.g. here is a probably wrong example webservice "stack" made up from the very little I know. - Daniel K. Schneider.
- Simple Object Access Protocol (SOAP) 1.1, W3C note. "SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses". Note DKS: This is generally the lowest Service Layer (just on top of HTTP) and tells how to describe messages that are sent or received.
- Web Services Description Language (WSDL), W3C Note. WSDL is an XML format for describing network services as a set of endpoints (methodes/calls) operating on messages containing either document-oriented or procedure-oriented information.
- WSFL (Web Services Flow Language) article from IBM. WSFL is an XML language (compatible with SOAP, UDDI & WSDL) for the description of the overall process logic of Web Services. See also [Business processes and workflow in the Web services world and ]Cover Pages about his
- Apache references to the WSIF (Web Services Invocation Framework) . This is a description of APIs to invoke Web Services described in WSDL. (Can, but does not need to be built on top of SOAP).
- WSIL (Web Services Inspection Language) WS-Inspection specification provides an XML format for assisting in the inspection of a site for available services and a set of rules for how inspection related information should be made available for consumption (IBM/Microsoft)
- UDDI (Universal Description, Discovery and Integration) enables organizations to (I) discover each other by a directory of service providers and services, and (II) find out what services are available
- WSRP (Web Services for Remote Portals): XML and Web services standard that will allow the plug-n-play of visual, user-facing Web services with portals or other intermediary Web applications. (Oasis led initiative)
- ebXML Messaging Service Specification (OASIS led) provides a secure method for exchanging electronic business transactions using the Internet. (This is a rather big project with several sub-specifications). See D. Mertz "Understanding ebXML" at developerworks/IBM.
Webservices in education
Rehak et al. model
“The era of monolithic Learning Technology Systems is over. Rather than building large, closed systems, the current focus is on flexible architectures that provide interoperability of components and learning content, and that rely on open standards for information exchange and component integration. The Learning Systems Architecture Lab has developed the concept of a Learning Services Architecture and the Learning Services Stack as a framework for developing the next generation of learning technology systems. We're in the process of developing learning services using Web services and Web services technologies.” (http://lsal.org/, retrieved 19:47, 23 April 2007 (MEST)).
( HTTP -> ) SOAP -> UDDI -> WSDL | WSIF ? -> WSFL ? -> -> ebXML? | WSIL ? -> WSRP? -> Portal
Players
- There are many players in this field
- The Web Services Activity Statement and the Web Services Activity give an overview of the W3's idea on application to application communication (web services). See also: Web Services Description Requirements and the Web Services Glossary.
- Oasis is an other organization working on xml-based e-business standards
- "What's Next: The Future of Web Services" from Microsoft
- XMethods has a long list of publicly available web services , implementations, tutorials, etc.
- In educational technology
Links
- Standards and recommendations
- Web Services Architecture (W3C Working Group Note 11 February 2004)
- For education
- Other
- Build a Web Service Analyzer using XSLT (400 KB>, Ammai.com tutorial
- Sun's XML page has a lot of information concerning concerning Java-based webservices. (3/2003)
- Why Use SOAP? Choosing Between SOAP and Application-Specific XML for Your Web Services by Frank Sommers, March 17, 2003 (artima.com)
References
- Blackmon, William H. and Daniel R. Rehak (2003). Customized Learning: A Web Services Approach HTML, Proceedings: Ed-Media 2003, June 2003. HTML - PDF (available from http://lsal.org/lsal/expertise/papers/).
- Wilson, Scott; Kerry Blinco and Daniel Rehak (2004). An e-Learning Framework: A Summary, alt-i-lab 2004:Advancing Learning Technology Interoperability, PDF