FIFR@SOA4ALL
From FutureInternetWiki
This page describes how SOA4ALL, as an Affiliated Project, relates to the Future Internet Functional Requirements (FIFR).
Contents |
[edit] Project Information
Project Name: SOA4ALL (Service-Oriented Architectures for All)
Project Homepage: http://www.soa4all.org
Contact Person:
Architecture Diagram
[edit] Statement
[edit] Related Future Internet Functional Requirements
[edit] Visionary
- 1. Device and Access technology
- f. Portals
Comment(WP1): 'The SOA4All Studio provides a first step towards a portal for the global service delivery platform, for now only Web services are addressed, however, by extending SOA4All technology towards XaaS, the portal provides means for much more ubiquitous access to resources.'
- 2. Network technology
- c. Availability of network services
Comment(WP1): 'The SOA4All runtime provides technology independent access to distributed services. The bus takes also care of routing messages, sharing information, and finding alternatives if necessary.'
- f. translating semantic names into routable entities
Comment(WP1): 'The many facets of processing semantic descriptions of services is the main purpose the SOA4All project. The objective of SOA4All is to allow users to invoke real services via the processing of semantic descriptions.'
- g. Naming and addressing
Comment(WP1): 'SOA4All applies traditional Web service technology to address services.'
- i. Storing and accessing (security)
Comment(WP1): 'Security is managed at the level of the SOA4All Studio via authentication services. The storage of services and other semantic artefacts are installed on top of semantic spaces. Semantic spaces deliver a coordination middleware and distributed shared memory, as integrated element of the bus.'
- 3. Context awareness
- d. Intelligent environments
Comment(WP1): 'The distributed service bus becomes to some degree an intelligent environment by delivering a monitoring platform that allows the capturing of context information about composite process, exectutable services and their QoS, as well as monitoring data directly collected from the bus infrastructure (the distributed nodes that jointly provide the global SOA4All Runtime infrastructure).' 'Comment(WP3): 'We will formalise the capturing of context such that services can utilise the contextual information of service consumers.'
- g. Easy to use
Comment(WP2): 'The SOA4All Studio will gather and utilise information about users and services in order to better support the interaction with services. Among the features we will provide are adapted recommendations as well as service adaptation based on contextual information.'
- 4. Assitive technology
- a. Active personal assistance based on context information
Comment(WP1): 'The SOA4All Studio puts a lot of emphasize on recommendations in terms of service production and consumption.'
- 5. Semantic development
- a. Semantic modelling of personal services
Comment(WP1): 'Managing annotated services for discovery, selection, composition and execution is one of the main purposes of SOA4All. The extensive support for creating process and composing services allows for personalized service compositions at graphical level, formal levels and finally at execution level.'
- b. Semantic modelling of Environmental Effects
Comment(WP1): 'The SOA4All monitoring platform is shipped with ontological models for context and monitoring data.'
- e. Semantic level based on real services
Comment(WP1): 'SOA4All invests a lot of resources in languages and tools to describe real services at the semantic level. SOA4All a priori only works at the semantic level of real services.'
- f. Service modelling
Comment(WP1): 'Service modeling at the semantic level, and via compositions is the main purpose of SOA4All. Through the SOA4All Studio the production of semantic services and process (compositions) and the consumption of these services is delivered to "average" users.'
- g. Support for service semantics and composition
Comment(WP1): 'Very important in SOA4All, cf. the aforementioned characteristics of the project w.r.t. point 5 of the functional requirements.' Comment(WP2): 'We will provide means for modeling Web Services, RESTful services and compositions of those (processes and mashups) and assistance/recommendations for creating these annotations.' Comment(WP3): 'We will develop annotation languages that can be used to attach semantic information to syntactic descriptions of services, that facilitate many activities, including composition.'
- 6. Large-scale computing
- e. Data mining
Comment(WP1): 'Also data mining is not an objective of SOA4All, the semantic space infrastructure provides a fundamental means for storing, sharing and exchanging semantic artefacts. Semantic Space provide a blackboard-style platform for collaborative activities (problem-solving) on top of semantic data.'
- g. Virtualization cross-business boundaries
Comment(WP1): 'The distributed service bus takes care of virtualizing the "billions of services" and their semantic descriptions, also of related processes. The distributed service bus in that sense provides a first version of a global service cloud that virtualizes serivces, businesses and their boundaries.'
- 7. Service Orchestration
- a. Ad-hoc integration of systems serving different purposes
Comment(WP1): 'SOA4All efforts towards runtime compositions could be mentioned here.'
- b. Service-On-Demand (coordination & registration of physical services) available on a large scale
Comment(WP1): 'At the semantic level, this is a goal of SOA4All. Coordination via the processing of semantic descriptions in the bus by means of platform services. Registration by means of the creation of semantic descriptions and its storing in the service registry.'
- e. Personalized services
Comment(WP1): 'Subject to the studio'
- j. Service composition modelling
Comment(WP1): 'Cf. above: creation of semantic descriptions of processes via services, goals, constraints and the data and control flow models.' Comment(WP2): 'We will provide means for creating composite services. Social interactions will play an important role since we will create a portal whereby people can create, reuse and share services with other people seamlessly.'
- 9. Community development
- a. Use communities for real-life advantages & services
Comment(WP2): 'We will provide a portal that will create a community of users around services. This community is expected to expand the number of semantic annotations for services available as well as to enhance existing ones.'
- 10. Content creation
- a. Prosumer
Comment(WP1): 'SOA4All through the studio emphasizes the Web2.O aspects of creating, using and sharing services. Composing a new services consumes existing services and provides a new service.' Comment(WP2): 'We will provide a portal that will create a community of users around services. This community is based on the notion of service prosumer.'
- 12. Mixed reality world
- c. Personalised collaborative environments for social interaction, gaming and innovative business concepts.
Comment(WP1): 'The Web2.0 aspects of the studio provides first steps towards such environments.'
- 13. Dynamic content centric networks
- a. Content-centric infrastructures
Comment(WP1): 'The semantic spaces could be seen as a content-centric infrastructure.'
[edit] Incremental
- 1. Device & access technology
- o. Distributed intelligence
Comment(WP1): 'Semantic space provide a system and device independent infrastructure for shared, and hence inherently distributed mangement of semantic data (intelligence). Semantic spaces, as blackboard, provides the grounds for distributed intelligence.'
- 2. Context awareness
- a. Sensors collecting environment information
Comment(WP1): 'Probes that are integrated with the service bus collect environmental information in terms of service executions, service QoS and the bus infrastructure'
- e. Personalization
Comment(WP1): 'SOA4All studio' Comment(WP2): 'SOA4All studio will gather and utilise contextual information in order to better adapt to the user at hand when discovering services (recommendation), when annotating services (annotation recommendation) and when consuming services (user awareness)'
- 3. Notification Services
- d. Early warnings
Comment(WP2): 'SOA4All studio will provide an analysis platform which will trigger notifications concerning the execution of services when a situation of interest to the user has been detected'
- 4. Service Orchestration
- e. Integrated End-User service usage
Comment(WP2): 'SOA4All studio will provide an analysis platform which will trigger notifications concerning the execution of services when a situation of interest to the user has been detected'
- 5. Community Development
- e. Public Opinion
Comment(WP2): 'SOA4All will be made publicly available and will generate a community of users around services.'
- 6. Collaboration
- b. Secure data sharing
Comment(WP1): 'SOA4All through the spaces offers so far insecure data sharing.
- 7. Content
- a. Content creation (prosumer)
Comment(WP2): 'We will provide a portal that will create a community of users around services. This community is expected to expand the number of semantic annotations for services available as well as to enhance existing ones. This community is based on the notion of service prosumer.'
- c. Adaptation
Comment(WP2): 'SOA4All studio will gather and utilise contextual information in order to better adapt to the user at hand when discovering services (recommendation), when annotating services (annotation recommendation) and when consuming services (user awareness)'
- e. Storage
Comment(WP1): 'Content of any sort in form of RDF statements can be persistently stored in distributed semantic spaces.'
- i. Recommendation systems
Comment(WP2): 'SOA4All will have a service recommendation system for suggesting services to users and an Annotations Recommendations system that will help users in creating semantic annotations to services.'
- k. Tools for content creation and manipulation
Comment(WP2): 'We will provide service annotation tools and a process/mashups editor.'
- l. Automated content annotation
Comment(WP2): 'We will use semi-automated support for service annotation.'
- 10. Service Infrastructure
- a. Virtualization
Comment(WP1): 'The SOA4All bus delivers a service cloud and hence virtualization.'
- b. Operating environments for virtual clouds
Comment(WP1): 'The bus together with the required platform services delivers the necessary operative environment for semantic services.'
- d. Lifecycle management of services.
Comment(WP2): 'SOA4All studio will provide a user-interface covering the life-cycle of services.'
- e. Formal definition of non-functional requirements.
Comment(WP1): 'Subject to the languages objectives of SOA4ALL.'
- g. WOA (SOA + Service Delivery Platforms)
Comment(WP1): 'The core principle of SOA4All: SOA at Web scale, SOA on the Web.'
- h. Modelling of services composition.
Comment(WP2): 'We will provide an editor for processes and mashups.'
