-
Notifications
You must be signed in to change notification settings - Fork 191
Request Definition
The request definition module is a web application that allows end-users to visually model their OpenIoT-based services using a node-based WYSIWYG (What-You-See-Is-What-You-Get) UI (User Interface). Modelled service graphs are grouped into “applications” (OAMOs). These applications are able to group a collection of different services (OSMOs) which comprises/describes a real life application (i.e. weather reports). This enables end-users to manage (describe/register/edit/update) different (unrelated) applications from a single point. All modelled services are stored by the OpenIoT Scheduler and are automatically loaded when a user accesses the web application.
[
](Documentation/images/request-definition/01-ui-overview.png)
The Figure above illustrates the main application interface components:
- The menu bar provides commands for creating new applications or for opening existing applications for editing. Once an application has been opened for editing, its name will appear on the top right of the menu bar.
- The central pane serves as the workspace area for modelling services.
- The node toolbox (left pane) contains the list of nodes that can be dragged into the workspace. Nodes are grouped by functionality.
- The properties pane (right pane) provides access to any selected node's properties.
- The console pane (bottom pane) provides workspace validation information (problems/warnings) as well as a debug preview of the generated SPARQL code for the designed service.
- Documentation
- Home
- Architecture
- Scheduler
- Service Delivery & Utility Manager
- Data Platform (LSM)
- X-GSN
- Mobile Sensors Management
- Optimizations
- Security
- User Interfaces
- OpenIoT Commons & Properties
- Standalone Platform Testing tools
- X-GSN Sensor Simulators
- Deliverables
- Glossary and Terminology
- Demos