Free common data format 3.1 software for linux

XML::Atom is an Atom feed and API implementation.

SYNOPSIS

use XML::Atom;

Atom is a syndication, API, and archiving format for weblogs and other data. XML::Atom implements the feed format as well as a client for the API.

International Components for Unicode provides a Unicode implementation, with functions for formatting numbers, dates, times, and currencies (according to locale conventions, transliteration, and parsing text in those formats).
It provides flexible patterns for formatting messages, where the pattern determines the order of the variable parts of the messages, and the format for each of those variables. These patterns can be stored in resource files for translation to different languages. Included are more than 100 codepage converters for interaction with non-unicode systems.
Main features:
- Text: Unicode text handling, full character properties and character set conversions (500+ code pages)
- Analysis: Unicode regular expressions; full Unicode sets; character, word and line boundaries
- Comparison: language sensitive collation and searching
- Transformations: normalization, upper/lowercase, script transliterations (50+ pairs)
- Locales: comprehensive data (230+) & resource bundle architecture
- Complex Text Layout: Arabic, Hebrew, Indic and Thai
- Formatting and Parsing: multi-calendar and time zone,dates, times, numbers, currencies, messages
Enhancements:
- This is a major release, with new features, new APIs, and many bugfixes in data and code.
- ICU uses and supports Unicode 5.0, which is the latest major release of Unicode.
- CU uses and supports data from Common Locale Data Repository (CLDR) 1.4, which includes many improvements in quality and quantity of data.
- A charset detection framework was added, which provides heuristics for detecting the charset for unlabeled sequences of bytes.
- Other performance and feature enhancements were added.

Multi-Simulator Interface, in shrot MSI, is a simulation interconnection engine. In other words it is a program that connects simulations together by synchronizing their clocks and data. Multi-Simulation Interface serves the same purpose as HLA and supports most of HLAs functionality (and more).
The MSI is an HLA alternative. The major motivating factors in the design of the MSI are speed, interoperability, and ease of use.
The MSI was written as a cutting edge distributed simulation component to connect multiple instances of ATLs premiere simulation software, CSIM, and it can be used to interface any compatible simulations.
How does the MSI compare to HLA?
The MSI was originally created to be just a light weight HLA RTI. However, as it was written, limitations in HLA were discovered. The MSI is an improvement on both the design and implementation of HLA. Some highlights include:
A 1,536 to 1 reduction in size over the publicly available (until late 2002) HLA RTI.
At least one order of magnitude of bandwidth consumption less than the publicly available (until late 2002) HLA RTI.
The ability to subscribe to an object name in addition to a type.
Time synchronization that allows for proper causality when used with discrete event simulators.
Support for systems-of-systems (SoS) and hierarchically organized simulations.
Availability for many platforms.
MSI Concept - A Synchronized Data Broker
The concept behind MSI is the synchronized data broker. There are many connected software systems that posses state data that changes over the life of that system. In the case where these systems need to exchange this changing data with other systems and the other systems will exhibit the effects of this data on their own state, the synchronization of this data may need to be managed.
Historically the management of this data has been as simple as tagging it with the time of its release. If there is any conflict in the data the most recent version of the data is used. If the data is late an extrapolation can potentially be used. In SQL relational databases transactions and locking are used to ensure data integrity. Most data brokering services offer little or no sychronization, only delivery.
MSI Setup and Use
The MSI uses a XML stream through a direct socket connection for communications. This enables the MSI to be used from any programming language that can use sockets (C, C++, Java, Ada, Lisp, Perl, etc.). Also, the MSI was written with cross-platform libraries that make it portable to all the major OS platforms (Linux, Solaris, Mac OS X, Microsoft Windows, IRIX, HPUX, etc.).
The MSI is a single executable file and is distributed with example code for the simulator/federate side interface.
MSI Time Synchronization
The MSI time synchronizer can mix unconstrained with time constrained simulations. Each constrained simulation reports the time of the next event that will occur in that simulation/federate. This time may be artificially inflated to cause loose synchronization (less overhead but less guarantee of accuracy). The simulations/federates will advance to the announced time.
MSI Data Synchronization
The MSI implements a publish/subscribe data broker. The MSI is presently not validating, therefore it does not require a separate data format specification (like the HLA FOM). When data format validation is implemented, it will be an optional feature and not written in Lisp. This greatly reduces MSIs setup time. Also, not being locked to a predetermined data format allows for dynamic data types.
There are five commands associated with the MSI data broker: publish, subscribe, update, unsubscribe, destroy (destroy is not implemented yet). Simulations/federates may subscribe to object names in addition to object types. This allows simulations to subscribe to specific objects of a type without needing to receive updates of all objects of that type. The update command is both an incoming and outgoing command. When a simulation/federate receives an update command, it is expected to reflect the new values of that object.
The MSI has a very flexible publish and subscribe system. A federate may subscribe to an object type or an object name. In addition a federate may specify particular attributes of an object or object type. For example, if an object has attributes name, x, y, and z, a federate that only considers two dimensions may choose to subscribe only to name, x, and y.
The MSI also supports systems of systems and object hierarchy in simulations. A publishing federate may designate a parent object. Subscribers may then subscribe to the objects children.
MSI Messaging
The MSI allows simulations/federates to send messages (interactions in HLA) to each other. These messages can contain multiple attributes and be multicast to a specific group of simulations.
Recently Added Features
Removed external library dependencies to improve the portability and fragility of the MSI.
Added a better client library.
Improved documentation.
Enhancements:
- An XML parsing bug in the utilities library was fixed.
- The socket library was enhanced with more protocols, Win32 tricks, and the ability to key off of addresses as well as names.
- The --wait-for command line argument was added.
- Several internal bugs were fixed.
- More of the client library and the CSIM interface were flushed out.
- All standard functionality was tested.

openDICOM.NET software implements a new approach towards DICOM (Digital Imaging and Communications in Medicine) libraries. DICOM is a worldwide standard in Medical IT and is provided by the National Electrical Manufacturers Assocation (NEMA). This standard specifies the way medical images and meta data like study or patient related data is stored and communicated over different digital medias. Thus, DICOM is a binary protocol and data format.

The openDICOM# Class Libary, main part of the openDICOM.NET project, provides an API to DICOM in C# for Mono and the .NET Framework. It is a completely new implementation of DICOM. In contrast to other similar libraries the intention of this implementation is to provide a clean classification with support of unidirectional DICOM data streaming. Another implemented goal is the support of DICOM as XML. This is not standard conform but very use- and powerful within software development, storage and manipulation. Currently, full read support of DICOM output stream and full write support to XML is supposed to be provided. The entire DICOM content can be accessed as sequence or as tree of class instances. Latter is the default representation of DICOM content by the library.

The openDICOM.NET Utils are a collection of console tools for working with the needed data dictionaries in different data formats (binary and textual), query of ACR-NEMA (prior DICOM standard) and DICOM files and transcoding them into image formats like JPEG and XML files. These utils are written in C# for Mono and the .NET Framework and are using the openDICOM# API for processing.

Last but not least, the openDICOM.NET Navigator recapitulates the openDICOM.NET Utils in form of a GTK# GUI. It provides different views with focus on DICOM data sets and visualization. Connectivity to GIMP is also given for image processing purpose as well as the possibility to run through multi-frame images like a movie.

DBD::AnyData is a DBI access to XML, CSV and other formats.

SYNOPSIS

use DBI;
my $dbh = DBI->connect(dbi:AnyData(RaiseError=>1):);
$dbh->func( trains, CSV, /users/joe/cars.csv, ad_catalog);
$dbh->func( bikes, XML, [$xml_str], ad_import);
$dbh->func( cars, DBI, $mysql_dbh, ad_import);
#
# ... DBI/SQL methods to access/modify the tables cars,bikes,trains
#
print $dbh->func( cars, HTMLtable, ad_export);

or

use DBI;
my $dbh = DBI->connect(dbi:AnyData(RaiseError=>1):);
$dbh->func( Pipe, data.pipe, XML, data.xml, ad_convert);

or

(many combinations of a dozen other data formats, see below)

The DBD::AnyData module provides a DBI/SQL interface to data in many formats and from many sources.

Currently supported formats include general format flatfiles (CSV, Fixed Length, Tab or Pipe "delimited", etc.), specific formats (passwd files, web logs, etc.), a variety of other kinds of formats (XML, Mp3, HTML tables), and, for some operations, any DBI accessible database. The number of supported formats will continue to grow rapidly since there is an open API making it easy for any author to create additional format parsers which can be plugged in to AnyData.

Data in these various formats can come from local files, from remote files, or from perl data structures such as strings and arrays.

Regardless of the format or source of the data, it may be accessed and/or modified using all standard DBI methods and a subset of SQL syntax.

In addition to standard database access to files, the module also supports in-memory tables which allow you to create temporary views; to combine data from a number of sources; to quickly prototype database systems; and to display or save the data in any of the supported formats (e.g. to display data in a CSV file as an HTML table).

These in-memory tables can be created from any combination of DBI databases or files of any format. They may also be created from perl data structures which means its possible to quickly prototype a database system without any file access or rdbms backend.