Mash-o-pedia
Assembly
Batch Job
Browser-side Assembly
Data Source
Data Stream
DHTML
ETL
Flash
JSON
Mashup
Output Interface
Part
Part API
Server-side Assembly
Simple DB
SOA
Subassembly
Web Clipping
Web Service
Webtop
Widget
XML
MashableLogic’s term to describe a collection of parts wired together in the Mashup
Editor. Assemblies may represent browser Widgets, server-side Web Services and
Batch Jobs, or other high-level entities like Data Sources and Output Interfaces.
Assemblies may be composed of nested assemblies, called Subassemblies.
A mashup scheduled to run on the server at specified intervals. Batch Job mashups
are useful for bulk data processing, for performing tasks that need to occur at specific
times, and can also be used to self-validate the integrity of other mashups in the
system by checking data sources and triggering alerts.
A visual assembly that runs in the browser, using either the Adobe Flash or native
browser JavaScript (DHTML) runtimes. Browser-side assemblies may consume
server-side assemblies such as web services to provide data. This distributes
processing, such that the server can be used to process large amounts of data, prune
it, and make it accessible to browser-side assemblies, generally resulting in improved
browser performance.
MashableLogic’s term to describe an assembly that publishes data in a format for
consumption by one or more compatible Output Interfaces. Data Sources are listed in
their own top-level category in the catalog and can be drag-dropped onto compatible
Output Interface widgets in the webtop, which render the data emitted by the Data
Source.
MashableLogic’s term to describe a single XML data structure contained within a wire
in the Mashup Editor. Each wire in the Mashup Editor may contain zero, one, or more
than one data streams.
Dynamic Hypertext Markup Language. Describes a collection of native browser
technologies used to create animated websites and widgets. Unlike competing
mashup technologies, MashableLogic can create browser-based widgets that use
either the Adobe Flash or browser-native JavaScript DHTML.
Stands for Extract, Transform, and Load. Used to describe operations performed on
data, as in extracting it from a source system, transforming it to meet business needs,
and loading it into a target system.
Flash is a browser plugin from Adobe Systems that powers rich, animated websites
and widgets with audio and video. Unlike competing mashup technologies,
MashableLogic can create browser-based widgets that use either the Adobe Flash or
browser-native JavaScript DHTML.
JavaScript Object Notation. A standard way to pass data to the browser that does not
require intermediate parsing.
A mashup consumes data from multiple sources, performs operations upon the data,
and outputs the data. Mashups are typically lightweight solutions built on an ad-hoc
basis to solve problems at hand, quickly. MashableLogic’s technology makes it
possible to build services not normally considered to be mashups, like web services
and batch jobs, in addition to browser-based widgets.
MashableLogic’s term to describe a visual widget that knows how to render data
published by one or more Data Sources. Examples of Output Interfaces include
charts (i.e. pie, line, bar) and maps. Data Sources can be dragged from the webtop
catalog and dropped onto compatible Output Interfaces for rendering the published
data.
MashableLogic’s term to describe the entities wired together in the Mashup Editor to
form Assemblies. Parts are defined using XML and JavaScript. Parts that execute on
the server can optionally choose to invoke Java libraries. Programmers can extend
the system by developing their own parts, using MashableLogic’s Part API and the
built-in Integrated Development Environment (IDE) contained within the Mashup
Editor.
MashableLogic’s Application Programming Interface provides common services for all
parts in the system. Services include the basic data operations for accessing input
data into the part, operating upon that data, and setting the output data from the part.
Services also include a Simple DB, widget-to-widget communication, webtop alerts,
and others.
Server-side assemblies are non-visual and execute entirely on the server. Examples
of server-side assemblies include web services, batch jobs, and news feeds. Parts
that comprise a server-side assembly have the ability to invoke Java libraries, to
further extend the system’s capabilities.
MashableLogic’s server-side database storage space that mashups can utilize. The
Part API exposes methods for parts to access the database using key groups, key
names, value names, and data values. Simple DB storage can be either private to a
single widget instance, or public across many widget instances, keyed on the part
developer’s unique Developer ID.
Service-Oriented Architecture. SOA is an attempt to provide a set of principles or
governing concepts that are used during the phases of systems development and
integration. Such architecture attempts to package functionality as interoperable
services within the context of the various business domains that use it.
MashableLogic’s term to describe a nested Assembly. Subassemblies can
themselves contain other nested subassemblies. Subassemblies are useful to reduce
the complexity of wiring diagrams in the Mashup Editor and also form the basis for
building abstraction layers of re-usable mashup components. Subassemblies can be
parameterized, using parameters that roll-up to outer containing assemblies or
subassemblies.
A rectangular area of a web page that has been turned into a widget.
A type of mashup that runs entirely on the server. Web services can be invoked from
browser-side assemblies or from external systems. External systems can invoke web
services via REST. Web services may accept parameters on the URL used to invoke
them. Web services typically return their results as either XML or JSON data.
Shorthand for web-based desktop. MashableLogic provides a feature-rich webtop
that can be used by end users to consume widgets. MashableLogic’s webtop
provides features not typically provided by other competing enterprise mashup
products, like:
- Integrated Alerts
- Drag-drop widget interactions
- Widget-to-widget communication and control
- Extensive personalization
- Plus much more
A widget is a small, focused web application that typically provides very discreet
functionality. MashableLogic differentiates widgets from assemblies. An assembly
represents the Mashup Editor wiring diagram. A widget is a configured assembly that
is saved into the webtop catalog with settings. For example, a news feed reader is an
assembly. A news feed reader that has been configured to read the CNN news feed
and saved into the catalog is a widget.
Extended Markup Language. XML is an industry-standard syntax for representing
data in a structured, hierarchical format.