FIFR@FAST

From FutureInternetWiki

Jump to: navigation, search

This page describes how FAST, as an Affiliated Project, relates to the Future Internet Functional Requirements (FIFR).

Contents

[edit] Project Information

Project Name: FAST; Service Front Ends (SFE) Open Alliance

Project Homepage: http://fast.morfeo-project.org; http://sfe.morfeo-project.org

Contact Person: Juanjo Hierro

[edit] Statement

The SFE Open Alliance has been conceived by industrial and academic organizations that declare to share a concrete vision on how the Service Front-end access layer infrastructure for the future Internet of Services can be implemented and together commit to spend resources to:

  • Produce concrete open specifications of components in the Reference Architecture they envision, taking an active role in the NEXOF-RA process or similar processes worldwide that may be instrumental for the adoption of their envisioned Reference Architecture.
  • Integrate results of projects they run and agree to link to the Open Alliance, with the goal of producing a complete and coherent set of software components that work as reference implementation for each part of the envisioned Reference Architecture.

Currently, the FAST, Opuce, in-Context, EzWeb and MyMobileWeb projects have endorsed the SFE Open Alliance initiative. Other projects are in conversations to join it. Components produced within an Open Alliance have a lifecycle beyond those of the private or publicly funded projects supporting research and development activities during a given period of time. Members commit to follow a joint Roadmap that drives evolution of components in the Reference Architecture or the addition of new ones.

Regarding its vision, the SFE Open Alliance embraces the following principles:

  • End-users have to be fully empowered, so they are able to setup their own web access-point to content and application services by means of picking and assembling web resources (aka, gadgets) available on the Internet ("LEGO" philosophy).
  • Active participation of end-users has to be enabled, allowing them to create gadgets as well as share and exchange both knowledge and gadgets with others and learn together, thus accelerating the adoption of innovations and productivity improvements.
  • Interaction must be adapted and relevant to context, giving the term "context" the widest possible meaning, in a way that comprises both user context (knowledge, profile, preferences, language, information about social networks the user belongs to, etc.) and delivery context (static and dynamic characteristics of the device used for access, geographical and time location, connection bandwidth, etc.). Dynamic context variability and user mobility must also be taken into consideration.
  • Access to sustainable business marketplace of services is supported enabling services from different providers to be bundled together with the necessary economic trading in place, supporting different pricing and revenue models


[edit] Related Future Internet Functional Requirements

[edit] Visionary

1. Device and Access technology
a. Device independent internet access
c. Seamless ubiquitous access
e. Payment
f. Portals
i. Device adaptability (if this means that content/applications will be adapted to access device)
j. user, terminal and session mobility
m. Abstraction of user interface
o. Emotion oriented user interfaces
  Comment: 'We plan to provide context-aware adaptation and emotional aspects could be partially represented as part of 
  context.'
3. Context awareness
d. Intelligent environments
e. Navigation
  Comment: 'Understanding it as navigation during interaction, e.g., context-aware assisted web browsing'
g. Easy to use


4. Assistive technology
a. Active personal assistance based on context information
5. Semantic development
a. Semantic modelling of personal services
b. Semantic modelling of Environmental Effects
d. Learning & adaptation
e. Semantic level based on real services
f. Service modelling
g. Support for service semantics and composition


7. Service Orchestration

  Comment: 'Note that we distinguish between orchestration/composition at the front-end and orchestration/composition at the
  backend.   We address orchestration/composition performed by endusers at the front-end (user-generated applications, using 
  mashup techniques) as well as the design of visual tools enabling users to configure orchestration/composition of services 
  running at the backend (e.g., like those you can compose in Opuce or FAST, following different approaches.).   Out of the 
  scope are autonomic orchestration/composition at the backend, for example.'
a. Ad-hoc integration of systems serving different purposes
b. Service-On-Demand (coordination & registration of physical services) available on a large scale
c. Social interaction
d. Rent-a-service
e. Personalized services
f. Service trading
g. Business models
h. Legal aspects
i. Asset-based service composition
j. Service composition modelling


10. Content creation
a. Prosumer
c. Enhanced content

[edit] Incremental

1. Device and Access technology
b. Easiness of Use and Configuration
f. Integrated services into the device
h. Devices taking care about privacy of the user
j. Navigation
m. Extended interactivity with the device
n. Interoperability
o. Distributed intelligence
2. Context awareness
c. Content chosen depending on context
d. Interactions with the environment
e. Personalization
f. Situation modelling
3. Notification Services
b. Context-aware reminder
c. Offline transaction
4. Service Orchestration

  Comment: 'Note that we distinguish between orchestration/composition at the front-end and orchestration/composition at the
  backend.   We address orchestration/composition performed by endusers at the front-end (user-generated applications, using 
  mashup techniques) as well as the design of visual tools enabling users to configure orchestration/composition of services 
  running at the backend (e.g., like those you can compose in Opuce or FAST, following different approaches.).   Out of the 
  scope are autonomic orchestration/composition at the backend, for example.'
a. Service aggregation
b. Real-world service integration
c. Service Trading
d. Information grail
e. Integrated End-User service usage
5. Community development
a. Helper platforms
  Comment: 'If mashup platforms fit here'
d. Collaborative content development in communities
7. Content
a. Content creation (prosumer)
b. Composition
c. Adaptation
i. Recommendation systems
j. Representation of content
l. Automated content annotation
m. Intelligent delivery


8. Trust
c. Accountability
  Comment: 'As far as accountability of session parameters is concerned'
d. trust based on recommendation
e. SLAs
f. Governance structures, methods and tools
g. Payments
h. Chain of trust
  Comment: 'Items e-h do not specifically belong to Service Front Ends but we address all aspects which will ensure 
  integration of SFE components with marketplace support components'
9. Business models
a. Content owners

[edit] Additional Related URLs

EzWeb project (http://ezweb.morfeo-project.org); MyMobileWeb project (http://mymobileweb.morfeo-project.org); OPUCE (http://www.opuce.tid.es/); InContext (http://www.in-context.eu)

Personal tools