Abstract
The emergence of web services technology has introduced a problem: how can we ensure that requests are successfully matched with advertisements when consumers and producers may use different terminology to describe the same service or the same terminology to describe different ones? Popular approaches to solving this problem are reviewed which involve the use of ontologies to improve the semantic content of the matchmaking process. When services are presentation-oriented rather than merely data-oriented, another layer of difficulty is introduced. The architecture of Web Services for Remote Portlets is discussed extensively, including the interaction cycle between the client and the producer to maintain state variables for each remote session of a portlet to provide sufficient background for readers. A comparison is made between the way concepts are implemented in two different portlet specifications – IBM Portlet API and JSR168 specification. Architecture is proposed to support the automated use of dynamic services for remote portlets, the motivation for which is the lack of expressivity of the current standards to represent the semantic requirements and capabilities of data and user-facing web services.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
