Matches in Ruben’s data for { ?s ?p ?o }
- s11761-018-0234-4 maker me.
- s11761-018-0234-4 title "Declarative Web Services Composition Using Proofs".
- s11761-018-0234-4 isPartOf service_oriented_computing_and_applications.
- s11761-018-0234-4 name "Declarative Web Services Composition Using Proofs".
- s11761-018-0234-4 label "Declarative Web Services Composition Using Proofs".
- s11761-018-0234-4 name "Declarative Web Services Composition Using Proofs".
- s11761-018-0234-4 topic service_composition.
- s11761-018-0234-4 topic Web_services.
- s11761-018-0234-4 topic interoperability.
- s11761-018-0234-4 topic Web_service.
- s11761-018-0234-4 topic proof.
- s11761-018-0234-4 topic Research.
- s11761-018-0234-4 topic World_Wide_Web.
- s11761-018-0234-4 subject service_composition.
- s11761-018-0234-4 subject Web_services.
- s11761-018-0234-4 subject interoperability.
- s11761-018-0234-4 subject Web_service.
- s11761-018-0234-4 subject proof.
- s11761-018-0234-4 subject Research.
- s11761-018-0234-4 subject World_Wide_Web.
- s11761-018-0234-4 authorList b0_b2184.
- s11761-018-0234-4 topic service_composition.
- s11761-018-0234-4 topic Web_services.
- s11761-018-0234-4 topic interoperability.
- s11761-018-0234-4 topic Web_service.
- s11761-018-0234-4 topic proof.
- s11761-018-0234-4 topic Research.
- s11761-018-0234-4 topic World_Wide_Web.
- s11761-018-0234-4 abstract "Over the last decade, Web services composition has become a thriving area of research and development endeavors for application integration and interoperability. Although Web services composition has been heavily investigated, several issues still need to be addressed. In this paper, we mainly discuss two major bottlenecks in the current process of modeling compositions. The first bottleneck is related to the level of expertise required to achieve a composition process. Typical procedural style of modeling, inspired by workflow/business process paradigm, do not provide the required abstractions. Therefore, they fail to support dynamic and self-managed compositions able to adapt to unpredictable changes. The second bottleneck in current service compositions concerns their life cycle and their management, also called their governance. In this context, we propose a declarative proof-based approach to Web service composition. Based on the three stages of pre-composition, abstraction, and composition, our solution provides an easy way to specify functional and non-functional requirements of composite services in a precise and declarative manner. It guides the user through the composition process while allowing detection and recovery of violations at both design and run-time using proofs and planning. Experiment results clearly show the added value of the proof-based solution as a viable strategy to improve the composition process.".
- s11761-018-0234-4 datePublished "2018".
- s11761-018-0234-4 mainEntityOfPage baccar_soca_2018.
- s11761-018-0234-4 sameAs s11761-018-0234-4.
- s11761-018-0234-4 isPrimaryTopicOf baccar_soca_2018.
- s11761-018-0234-4 page baccar_soca_2018.
- s11761-018-0234-4 number "371".
- s11761-018-0234-4 number "12".
- s11761-018-0234-4 number "3–4".
- s11761-018-0234-4 number "389".
- s11761-018-0234-4 volume "12".
- s11761-018-0234-4 locator "371".
- s11761-018-0234-4 locator "12".
- s11761-018-0234-4 locator "3–4".
- s11761-018-0234-4 locator "389".
- s11761-018-0234-4 volume "12".
- s11761-018-0234-4 position "12".
- s11761-018-0234-4 position "3–4".
- s11761-018-0234-4 volumeNumber "12".
- s11761-018-0234-4 endingPage "389".
- s11761-018-0234-4 startingPage "371".
- s11761-018-0234-4 pageEnd "389".
- s11761-018-0234-4 pageStart "371".
- s11761-018-0234-4 pageEnd "389".
- s11761-018-0234-4 pageStart "371".
- s11761-018-0234-4 issue "3–4".
- s11761-018-0234-4 issue "3–4".
- s11761-018-0234-4 issueNumber "3–4".
- j.future.2019.10.006 author me.
- j.future.2019.10.006 author tom_seymoens.
- j.future.2019.10.006 author me.
- j.future.2019.10.006 author me.
- j.future.2019.10.006 creator me.
- j.future.2019.10.006 creator tom_seymoens.
- j.future.2019.10.006 creator me.
- j.future.2019.10.006 creator me.
- j.future.2019.10.006 about publication.
- j.future.2019.10.006 about reuse.
- j.future.2019.10.006 about Metadata.
- j.future.2019.10.006 about Linked_Data.
- j.future.2019.10.006 author me.
- j.future.2019.10.006 author tom_seymoens.
- j.future.2019.10.006 author me.
- j.future.2019.10.006 author me.
- j.future.2019.10.006 coparticipatesWith me.
- j.future.2019.10.006 coparticipatesWith tom_seymoens.
- j.future.2019.10.006 coparticipatesWith me.
- j.future.2019.10.006 coparticipatesWith me.
- j.future.2019.10.006 type PublicationVolume.
- j.future.2019.10.006 type ScholarlyArticle.
- j.future.2019.10.006 type Article.
- j.future.2019.10.006 type Document.
- j.future.2019.10.006 type Q386724.
- j.future.2019.10.006 type CreativeWork.
- j.future.2019.10.006 type Document.
- j.future.2019.10.006 type Work.
- j.future.2019.10.006 type Document.
- j.future.2019.10.006 P50 me.
- j.future.2019.10.006 P50 tom_seymoens.
- j.future.2019.10.006 P50 me.
- j.future.2019.10.006 P50 me.
- j.future.2019.10.006 maker me.
- j.future.2019.10.006 maker tom_seymoens.
- j.future.2019.10.006 maker me.
- j.future.2019.10.006 maker me.
- j.future.2019.10.006 title "Implementation-independent Function Reuse".
- j.future.2019.10.006 isPartOf future_generation_computer_systems.
- j.future.2019.10.006 name "Implementation-independent Function Reuse".
- j.future.2019.10.006 label "Implementation-independent Function Reuse".
- j.future.2019.10.006 name "Implementation-independent Function Reuse".
- j.future.2019.10.006 topic publication.
- j.future.2019.10.006 topic reuse.