Free structure fire response software for linux

XML::Structured is a simple conversion API from XML to perl structures and back.

SYNOPSIS

use XML::Structured;

$dtd = [
element =>
attribute1,
attribute2,
[],
element1,
[ element2 ],
[ element3 =>
...
],
[[ element4 =>
...
]],
];

$hashref = XMLin($dtd, $xmlstring);
$hashref = XMLinfile($dtd, $filename_or_glob);
$xmlstring = XMLout($dtd, $hashref);

The XML::Structured module provides a way to convert xml data into a predefined perl data structure and back to xml. Unlike with modules like XML::Simple it is an error if the xml data does not match the provided skeleton (the "dtd"). Another advantage is that the order of the attributes and elements is taken from the dtd when converting back to xml.

Reliable Response Notification provides guaranteed delivery of critical messages to a wide range of devices. The project guarantees that every emergency will have one, and only one, person responding and taking charge of the recovery.
For integrated services, like some network monitors, help-desk packages, and security suites, Reliable Response Notification allows the user to update records via their mobile devices. It is available as either a standalone server or as a hosted service.
Enhancements:
- The product supports three types of groups: broadcast, escalation and on-call.
- Many devices are supported, including email, SMS, text-to-speech, Jabber, GTalk, SameTime IM, and alphanumeric pagers.
- Integrations for a number of packages are available.
- There is an easy system to add new integrations as needed.

Structured Document Validator project implements a generalized method for validating both the structure and content of structured documents.

Any data format that can be deterministically divided into tags and data is classed as a structured document. This definition applies to a wide array of data formats, including XML, Java properties files, and delimited value files.

The application performs validations based on user-defined Structured Document Definitions (SDDs). It provides an environment for validation, SDD development, and document editing.

Net::Google::Response is a simple OOP-ish interface to the Google SOAP API search responses.

SYNOPSIS

my $service = Net::Google->new(key=>LOCAL_GOOGLE_KEY);
my $session = $service->search();

$session->query(qw(Perl modules));

# You are probably better off calling
# $session->results() but if you want
# the raw response object(s) here ya go :

my $responses = $session->response();
my $count = scalar(@$responses);

# $r is a Net::Google::Response object

foreach my $r (@$responses) {
print sprintf("%s : %sn",$r->searchQuery(),$r->estimatedTotalResults());
}

Provides a simple OOP-ish interface to the Google SOAP API for searching. This package is used by Net::Google.

The Net::Google::Response object is used to contain response information provided by the Google search service in response to a search query. The Response object allows the client program to easily access the data returned from a search.

Response data is accessed using methods with identical names to the elements of a search response (as documented in the Google Web APIs Reference, section 3). For instance, the first example in the SYNOPSIS section, above, would return the estimated number of total results for the query.

Response objects may contain other response objects, where an element would return an array of other elements. For instance, calling $response->resultElements() will return a reference to an array of Net::Google::Response objects, each one representing one result from the search.

The Response module will automatically provide methods for the search response, as described by the service WSDL file. The results format is described by the Google APIs documentation, to which you should refer for the most up-to-date information. As of the April 8th, 2002 release of the Google APIs, the methods below are provided for each search result.

Spamresponder provides a simple and radical spam filter using DNS validation and challenge/response.

Spamresponder is a very simple and radical spam filter, combining DNS validation with the challenge/response approach. It will go through all mail messages in /var/mail/$USER, looking for specific "trusted" strings in the header and body parts of the mail.

It will delete and send an automatic reply to messages which have no "trusted" strings inside them. Those replies will include one of the "trusted" strings, so the recipient just needs to reply to this confirmation message.

The MailFrom-address of an email containing a trusted string becomes a trusted string itself.

GraphViz::Data::Structure can visualise data structures.

SYNOPSIS

use GraphViz::Data::Structure;

my $gvds = GraphViz:Data::Structure->new($data_structure);
print $gvds->graph()->as_png;

This module makes it easy to visualise data structures, even recursive or circular ones.
It is provided as an alternative to GraphViz::Data::Grapher. Differences:

GraphViz::Data::Structure handles structures of arbitrary depth and complexity, automatically following links using a standard graph traversal algorithm.
GraphViz::Data::Grapher creates graphics of indiividual substructures (arrays, scalars, hashes) which keep the substructure type and data together; GraphViz::Data::Structure does this by shape alone.
GraphViz::Data::Structure encapsulates object info (if any) directly into the node being used to represent the class.
GraphViz::Data::Grapher colors its graphs; GraphViz::Data::Structure doesnt by default.
GraphViz::Data:Structure can parse out globs and CODE references (almost as well as the debugger does).

Net::Gopher::Response::XML is a Perl module Convert a Gopher/Gopher+ response to XML.

SYNOPSIS

use Net::Gopher;
use Net::Gopher::Response::XML;

...

$response->as_xml(File => menu.xml);

This module contains code to convert a response from a Gopher or Gopher+ Gopherspace to XML. This functionality was originally in the Net::Gopher core, but its features are seldom needed, and it was deemed by me, Will, to be unnecessary bloat.

The module has one method, as_xml(), which you can call on Net::Gopher::Response objects to generate XML. If you have existing code that expects Net::Gopher::Response to already have as_xml() in it, just add the use Net::Gopher::Response::XML to the top of the script as shown in the SYNOPSIS and it should work fine with both pre 1.05 and post 1.05 versions.