Free interoperability software for linux

Babel Interoperability Tool is a tool for mixing C, C++, Fortran77, Fortran90, Python, and Java in a single application. This is our cornerstone product, representing 90% of our effort. Babel is the foundation for a multilanguage scientific compoenent framework. We are often called "The Babel Team" because of this tools visibility.
Quorum: an online parliamentary system that enables the proposing, discussion, and voting on motions via the web. This software is used to accelerate standardization efforts for geographically disperse groups.
Alexandria: a component software repository. A next-generation Netlib that supports fuzzy searches and browsing APIs via dynamically generated Babel language bindings.
Gauntlet: a multi-language, multi-platform software testing framework. Can harvest results from multiple platforms via XML/email and browse session histories through the web.
Enhancements:
- This release completes the developers initial vision for Babel as a language interoperability tool and distributed computing platform.
- Specific bugs fixed include a.bug in backdoor initialization (C++ and F90/95), a Python reference counting bug, a potential 64-bit enum bug, and a bug in Fortran stubs for arrays of enumerated types.

Business::Travel::OTA is a Perl module with tools for handling OTA-compliant (Open Travel Alliance) messages.

SYNOPSIS

# This tests the "otaserver" with an OTA_PingRQ message
otaclient --ping --verbose

The Business::Travel::OTA module is the main module for the Business-Travel-OTA distribution in the OTA-Tools project. Your can see the project web site at SourceForge.

http://sourceforge.net/projects/ota-tools

The OTA-Tools project is a set of software tools useful for building, testing, and exercising web services (and other interfaces) for the travel industry which comply with the specifications of the Open Travel Alliance (OTA). You can see the OTA web site here.

http://www.opentravel.org

This project is initiated by members of the OTA, but it is not an official project of the OTA. It represents an opportunity for OTA members to collaborate on tools, test suites, and reference implementation software for the purposes of reducing the learning curve for newcomers and enhancing interoperability.

The Business-Travel-OTA distribution is a set of Perl modules and programs which demonstrate the creation, validation, transmission, processing, parsing, and manipulation of OTA messages. This software also implements reference client and server capabilities which can be adapted as necessary.

Darwin Calendar Server provides a CalDAV server.

The Darwin Calendar Server is a standards-compliant server that allows multiple users to collaboratively share calendaring information. It provides a shared location on the network to store schedules, and allows users to send each other and manage invitations.

In order to provide interoperability with multiple calendaring clients, the server implements the CalDAV protocol, which is an extension of WebDAV, which is in turn an extension of HTTP.

Bellagio is a sample implementation of OpenMAX IL for Linux.
It enables software developers and ISVs to familiarize themselves with the OpenMAX IL API and to develop their own OpenMAX multimedia and streaming media components for mobile devices, including codecs, video I/O, and audio mixers.
Included sample components comply with the OpenMAX base and interoperability profiles and can be tunnelled together.
Main features:
- a shared library with the IL core and a "reference" OpenMAX component
- a number of OpenMAX components which pass Khronos conformance tests
- a set of GStreamer plugins that use the IL API (not available yet)
Enhancements:
New video components:
- ffmpeg based MPEG4/H.264 decoder
- color converter component YUV -> RGB
- video renderer based on devFB
New audio component:
- audio file reader based on ffmpeg audio format
- volume component
Fixed known bugs:
- FFMPEG audio decoder now works on FC6 and other distributions with the latest ffmpeg release (0.4.9-0.35.20070204)
Known pending bugs:
- some ogg streams can not be decoded properly
- the tunneling between file reader, mp3 dec based on ffmpeg - alsa sink ends in a deadlock sometimes.
- This behavior has been detected some times using FC6 and UBUNTU, not with the FC4
Full list of components:
Audio:
- ogg decoder based on libvorbis (stand alone components, and multiple roles component)
- mp3 decoder based on mad decoder
- mp3 decoder based on ffmpeg (multiple roles component)
- volume component
- alsa audio sink
- ffmpeg audio file reader (to be used with mp3 ffmpeg decoder)
Video:
- MPEG4 decoder based on ffmpeg (multiple roles component)
- H.264 decoder based on ffmpeg (multiple roles component)
- Color converter based on ffmpeg
- video renderer based on devFB
- Major additions to the 0.2
- New port classes
The components are:
- multiple formats audio decoder component that supports mp3 and ogg audio formats
- alsa sink component
- all the other components are NOT compatible with the new architecture.
- They have been removed and will be ported to the new architecture in a further delivery

Image::MetaData::JPEG::TagLists contains a collection of tag tables for JPEG segments. Image::MetaData::JPEG::TagLists is an appendix to the main manual page of the Image::MetaData::JPEG module, which the reader should refer to for further details and the general scope.

Valid tags for Exif APP1 data

The Japan Electronics and Information Technology Industries Association (JEITA) set up a standard for an exchange format for digital still cameras pictures, known as Exif. This standard defines a structure for embedding meta-data in a JPEG picture, to be written in the APP1 segment. The generalities and the reference documents about this structure are introduced in the Structure appendix; this section and its subsections list the valid interoperability record tags as well as their format.

Canonical Exif 2.2 and TIFF 6.0 tags for IFD0 and IFD1

In general, IFD0 and IFD1 can host tags from the same set. These tags are divided in three categories: canonical, additional and registered to companies. The tags listed in the following table are to be considered canonical; they are described at length in the Exif standard document, and can be found both in the IFD0 and in the IFD1 (some of them, in fact, must be present in both directories).

The class column carries the tag class; possible values are: A (image data structure), B (offsets), C (image data characteristics), D (other tags) and P (pointers to other IFDs). The two following columns show tag hexadecimal codes and names. The type column specifies the (always unsigned) tag type: I (short or long), S (short), L (long), R (rational) and A (ASCII, always null terminated). The count column obviously carries the tag count (- for a variable count, either because it is a variable length string or because it depends on other tags).

The IFD0 and IFD1 columns specify the support level in the respective directory; each column comprises four letters, because both the primary image (IFD0) and the thumbnail (IFD1) can come in four varieties (uncompressed chunky, uncompressed planar, uncompressed YCC and JPEG compressed).

This module currently focuses only on JPEG pictures (not TIFF), so only the fourth letter of the IFD0 column is interesting, but note that the thumbnail of a JPEG image can be uncompressed. The support level codes stand for: M (mandatory), R (recommended), O (optional), N (not_recorded) and J (included in JPEG marker and so not recorded).

The thumbnail-only column shows a T for those records which cannot be set/changed by the user exception made during a thumbnail update action (and some of them are calculated automatically anyway). Note that, in some cases, it is possible to set a tag when its support level is N (e.g., the YCbCr stuff in IFD1): picture displaying programs should however simply ignore it. Some other tags, concerning offsets or thumbnail specific information, cannot be set by the module user (they are calculated automatically, more reliably): these are marked by calculated in the notes, or by a T in the thumbnail-only column.

Hexadecimal code count IFD0 IFD1 thumbnail-only
class | Tag name type | supp.supp.| notes
| | | | | | | | |
A 100 ImageWidth I 1 MMMJ MMMJ T (not JPEG) pixels/row
A 101 ImageLength I 1 MMMJ MMMJ T (not JPEG) num. rows
A 102 BitsPerSample S 3 MMMJ MMMJ T (not JPEG) 8,8,8
A 103 Compression S 1 MMMJ MMMM T 1(uncompr.) or 6(JPEG)
A 106 PhotometricInterpretation S 1 MMMN MMMJ 2(RGB) or 6(YCbCr)
D 10e ImageDescription A - RRRR OOOO (see note 1)
D 10f Make A - RRRR OOOO camera manufacturer
D 110 Model A - RRRR OOOO camera model
B 111 StripOffsets I - MMMN MMMN calculated
A 112 Orientation S 1 RRRR OOOO (see note 2)
A 115 SamplesPerPixel S 1 MMMJ MMMJ T (not JPEG) 3 compon.
B 116 RowsPerStrip I 1 MMMN MMMN T (not JPEG)
B 117 StripByteCounts I - MMMN MMMN T (not JPEG)
A 11a XResolution R 1 MMMM MMMM (see note 3)
A 11b YResolution R 1 MMMM MMMM (see note 3)
A 11c PlanarConfiguration S 1 OMOJ OMOJ (see note 4)
A 128 ResolutionUnit S 1 MMMM MMMM (see note 3)
C 12d TransferFunction S 768 RRRR OOOO (see note 5)
D 131 Software A - OOOO OOOO Exif software/firmware
D 132 DateTime A 20 RRRR OOOO (see note 6)
D 13b Artist A - OOOO OOOO owner/photogr./creator
C 13e WhitePoint R 2 OOOO OOOO (see note 5)
C 13f PrimaryChromaticities R 6 OOOO OOOO (see note 5)
B 201 JPEGInterchangeFormat L 1 NNNN NNNM calculated
B 202 JPEGInterchangeFormatLength L 1 NNNN NNNM T (only JPEG)
C 211 YCbCrCoefficients R 3 NNOO NNOO (see note 7)
A 212 YCbCrSubSampling S 2 NNMJ NNMJ (see note 7)
A 213 YCbCrPositioning S 1 NNMM NNOO (see note 7)
C 214 ReferenceBlackWhite R 6 OOOO OOOO (see note 8)
D 8298 Copyright A - OOOO OOOO of photogr./editor
P 8769 ExifOffset L 1 MMMM OOOO calculated
P 8825 GPSInfo L 1 OOOO OOOO calculated

OpenChange project intends to provide an implementation of Microsoft Exchange under Unix platforms.
Gnome Evolution is a powerful messaging client which offers several features but do not yet have native Exchange protocols support. This plugin extends Gnome Evolution, provides interoperability with Microsoft Exchange servers and aims to provide a messaging client with most of the common features Microsoft Outlook users are dealing with on a daily basis.
Main features:
- Exchange account setup
- Fetch emails
- Send emails
- Delete emails
- Fetch and send attachments
- Handle Message flags (attachments and importance)
- Display light mailbox folder hierarchy
Enhancements:
- This experimental release provides exchange account setup using the Evolution account wizard.
- It can fetch, send, and delete email messages with or without attachments. Message flags (attachment, importance, read/unread) are supported.
- A light mailbox folder hierarchy is provided.

Caffeine is a free high-performing interoperability solution between the Java platform and the .NET framework.
Caffeines key differentiator is that does not replace the Java Virtual Machine. Instead, your JVM of choice is hosted within the .NET runtime, ensuring that vendor-specific VM optimizations are preserved.
The specific objectives of Caffeine are:
- Run on any combination of .NET runtime (1.0+) and Java Virtual Machine (1.2+).
- Allow full reuse of any Java library from a .NET environment, working exclusively at the API level and avoiding bytecode translation of the actual implementation.
- Provide optimal performance, running the JVM and .NET under the same process and avoiding network or IPC costs.
Caffeine is open source, built for and by developers, and licensed under an MIT/X license that allows Caffeine to be used and/or embedded in commercial software.
Main features:
- Bindings of jobject, jarray, jvalue, jclass, jmethoid, jclassid, jfieldid.
- C# wrapper class generator toolchain from Java library.
- Public and protected classes and methods.
- Inner types, within classes and interfaces.
- Abstract classes and interfaces.
- Object casting.
- Arrays.
- Constants in interfaces.
- Basic temporary interoperability between System.String and java.lang.String.