Download JAR files tagged by defines with all dependencies

Module providing the webservice interface based on the Jetty embedded webserver and the FreeMarker template engine. Defines a simple format for providing textual annotations and produced output in HTML or JSON. This module has no dependencies to the other SCIE modules (except for the PDF text extractor) or the UIMA framework and thus can be used in any context, where text is annotated by an algorithm and should be presented to an end user.

Geomajas Graphics project. The graphics project defines a set of interfaces and controllers for editing graphical objects based on gwt-graphics. It can be used as a basis for annotations (based on SVG/VML elements) as well as to extend geometry editing with operations like dragging/resizing. Geomajas is a component framework for building rich Internet applications (RIA) with sophisticated capabilities for the display, analysis and management of geographic information. It is a building block that allows developers to add maps and other geographic data capabilities to their web applications.

Geomajas Graphics Editing plugin. The graphics editing plugin defines a set of interfaces and controllers for editing graphical objects in maps based on gwt-graphics. It can be used as a basis for annotations (based on SVG/VML elements) as well as to extend editing with operations like dragging/resizing. Geomajas is a component framework for building rich Internet applications (RIA) with sophisticated capabilities for the display, analysis and management of geographic information. It is a building block that allows developers to add maps and other geographic data capabilities to their web applications.

Geomajas Graphics Editing plugin. The graphics editing plugin defines a set of interfaces and controllers for editing graphical objects in maps based on gwt-graphics. It can be used as a basis for annotations (based on SVG/VML elements) as well as to extend editing with operations like dragging/resizing. Geomajas is a component framework for building rich Internet applications (RIA) with sophisticated capabilities for the display, analysis and management of geographic information. It is a building block that allows developers to add maps and other geographic data capabilities to their web applications.

As its name indicates, Core module gather all "kernel" functionalities that will be use by other modules. More precisely, this module defines the whole types used by PowerAPI to define its architecture. This module also defines the essential Clock class, responsible of the periodically sending of the Tick message, itself responsible of the process of the PowerAPI business part.

This bundle wraps Pi4j (http://pi4j.com) that wraps the native code Wiring Pi (http://wiringpi.com). It wraps these libraries to make them OSGi friendly and allow them to work together with the OSGi enRoute IoT circuit library (osgi.enroute.iot.circuit). The bundle will first use Pi4J to detect on what hardware it runs. If it runs on an appropriate type, it will register a component that can be configured with Metatype. The Metatype defines a full blown configuration template for all the Pi's functions. The GPIO's are registered as components for the circuit. Regardless of the success of the configuration, this bundle will also register a GpioController service, which is the main Pi4J class.

This module contains the sequence datastructure of the TCS Alignment Toolbox. It defines the possible value sets in the ValueType enum as well as the different KeywordSpecification classes, namely: 1.) StringKeywordSpecification for string type values. 2.) SymbolicKeywordSpecification for values from a discrete alphabet (also refer to the Alphabet class) 3.) VectorialKeywordSpecification for vectors of some length (or for scalars) A NodeSpecification is a vector of such KeywordSpecifications and defines the order of value sets. A node, then, is defined as a vector of values from these value sets (also refer to the Value interface as well as the StringValue, SymbolicValue and VectorialValue classes). Finally a sequence is defined as a list of such nodes.

This bundle wraps Pi4j (http://pi4j.com) that wraps the native code Wiring Pi (http://wiringpi.com). It wraps these libraries to make them OSGi friendly and allow them to work together with the OSGi enRoute IoT circuit library (osgi.enroute.iot.circuit). The bundle will first use Pi4J to detect on what hardware it runs. If it runs on an appropriate type, it will register a component that can be configured with Metatype. The Metatype defines a full blown configuration template for all the Pi's functions. The GPIO's are registered as components for the circuit. Regardless of the success of the configuration, this bundle will also register a GpioController service, which is the main Pi4J class.

Tinder is a Java based XMPP library, providing an implementation for XMPP stanzas and components. Tinders origins lie in code that's shared between Jive Software's Openfire and Whack implementations. The implementation that's provided in Tinder hasn't been written again from scratch. Instead, code has been moved from the original projects into Tinder, preserving al of the existing features and functionality. Most of the code that's now in Tinder is based on the org.xmpp package implementation that previously existed in Openfire and Whack. This is the code that defines classes such as Packet, JID, IQ, Component and their extensions. Additionally, some multi-purpose code (such as the DataForm and Result Set Management implementations have been moved to Tinder as well.

SEPIA provides implementations for various types of Petri nets. Along Place/Transition-nets, it supports Petri nets with distinguishable token colors and defines coloured workflow nets, where coloured tokens are interpreted as data elements used during process execution. To support information flow analysis of processes, SEPIA defines so-called IF-Nets, tailored for security-oriented workflow modeling which enable users to assign security-levels (HIGH, LOW) to transitions, data elements and persons/agents participating in the process execution.