MIB Smithy is an application for SNMP and COPS developers, MIB and PIB designers, and Internet-draft authors. It provides a GUI-based environment for designing, editing, and compiling MIB and PIB modules according to the SMIv1, SMIv2, and COPS-PR-SPPI standards. It accelerates the development process by providing an easy-to-use GUI-based environment for developing the specifications without the syntax and formatting concerns of editing the modules by hand. It includes a number of built-in basic SNMP management tools, XML support, and (with MIB Smithy Professional) support for custom compiler output formats.
Groovy is an agile, dynamic language for the JVM which combines many features from languages like Python, Ruby, and Smalltalk and makes them available to Java developers using a Java-like syntax. It is designed to help get things done on the Java platform in a quicker, more concise, and fun way. It can be used as an alternative compiler to javac to generate standard Java bytecode to be used by any Java project or it can be used dynamically as an alternative language, such as for scripting Java objects, templating, or writing unit test cases.
MIB Smithy SDK is a dynamic extension to Tcl/Tk (8.4+) that allows development of custom scripts for controlling SNMP agents, manipulating SMI definitions, doing conversions, and more. It is based on the core of Muonics' MIB Smithy, and the SDK supports SMIv1 and SMIv2, as well as SNMPv1/v2c/v3 with HMAC-SHA-96 and HMAC-MD5-96 authentication and DES/CBC and AES128/CFB privacy. It also provides complete read-write access to all elements of SMI/MIB Module definitions, unlike similar extensions that provide only read access to a limited subset. The SDK allows multiple discrete SMI databases and SNMP sessions, and provides all of the built-in validation and error recovery capabilites of the full product, without the visual MIB development environment.
XSD is a W3C XML Schema to C++ translator. Provided with an XML instance specification (XML Schema), it generates C++ classes that represent the given vocabulary as well as parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with elements, attributes, and text in a direct representation of XML such as DOM or SAX. XSD features support for in-memory and stream-oriented processing models, comprehensive XML Schema feature coverage, easy integration, and more.
The GCC XML Tree Node Introspector project consists of a patch to the gcc compiler to output the internal compiler tree nodes in RDF/XML and programs to process that RDF/XML. The tree nodes are complex data structures which represent the source code inside the compiler. Through these tree nodes, users are able to extract information from their programs that would be otherwise very difficult to obtain. Modules exist to store these nodes in Redland RDF using a Berkley database. The long-term goal of the project is create a high-level API that will make the programmatic manipulation of programs easier than it is now.
ObjectBox is an o:XML compiler and interpreter written in Java. o:XML is a complete object oriented programming language, with features such as multiple inheritance, function overloading, recursive procedures, and much more. The syntax is straight-forward, intuitive XML. It also features an extensible expression language modelled on XPath. The ObjectBox is a complete implementation of the language and adds comprehensive Java Language Extensions, Database and Servlets support, Struts integration and more.
The Kawa Scheme System is a full Scheme implementation, completely written in Java. Scheme functions and files are automatically compiled into Java byte-codes. Kawa does some optimizations, and the compiled code runs at a reasonable speed. It provides the usual read-eval-print loop, as well as batch modes. The Kawa compilation framework is also useful for implementing other languages on top of JVM. There is active development of XQuery (the XML query language), and less active development of Emacs Lisp, Common Lisp, and EcmaScript.