Release 2.1.1 was the first stable release of the PIA. We intend to keep incompatible changes to the tag language and configuration files to a minimum after this point, so as to provide a stable base on which to build applications. We do expect to add new language features and new applications -- these include, in the former category, support for XML Namespaces, and in the latter, a complete small-office form-handling package.
Subscribe to PIA-announce@RiSource.org to be notified of new releases. Copies of the PIA can be obtained from our web site, http//www.RiSource.org/PIA.
sourceforge.net/projects/cpia/
, with a project home page at
cpia.sourceforge.net
.
rsv.ricoh.com
now belong to the manufacturing subsidiary of the company where the PIA
team works: Ricoh Innovations, Inc. The corresponding domain is
rii.ricoh.com
.
/Apps/
added. Unlike /Agents/
, which primarily
contains agents meant to run under a desktop PIA proxy,
/Apps/
contains code for what amount to stand-alone
applications.
It must be noted that Woad is not complete yet; this is essentially a preview release. However, it still works pretty well as a source-code browser for the PIA and other web-based applications.
jar
files in CLASSPATH:
/usr/local/JSDK2.0/lib/jsdk.jar
for operation with
Apache-JServ.
/usr/local/java/lib/activation.jar
/usr/local/java/lib/mail.jar
org.risource.dom.ToDocument
is untested, but at least it
compiles.
tsdoc
tagset has been improved, and is now the default
tagset for viewing tagset files through the browser (makes sense,
doesn't it?).
HEADER.html
files have been updated and their
top-level headings improved to give a smoother tree-browsing experience.
Release 2.1.1 is the first stable release of the PIA (Platform for Information Applications). Several non-trivial applications have been implemented using the PIA, and at Release 2.1 it is considered ``ready for prime time''.
From this point, we expect that any changes made to the PIA, and especially to the tag language, will take the form of incremental improvements: we intend for 2.1.1 to provide a stable base for applications. We expect that any changes in the tag language after this point will be made in such a way as not to affect existing applications.
It is possible that noticable changes may be made in the tree structure of the documentation and sample applications. Given the PIA's flexible site-structuring mechanism, any such changes should be easy to work around.
There are a few ``issues'' with 2.1.1, mainly functionality which we hoped would be present.
javadoc
-generated class documentation are broken,
especially in the API manual.
op="operation"
attributes for all tags
(e.g. <test>, <numeric>, <logical>) that
implement multiple operations. The old operation-name
attributes are still available for use in documents parsed using
a legacy, HTML parser.
tsdoc
tagset.
.ts
file.
Release 2.0 was the previous release series.
Release 2.0.9 was, essentially, the ``beta'' version of 2.1 -- it is unlikely that anything other than bug fixes will have been done in the interim. If you have been using earlier versions of the PIA, you should at least look at the changes introduced since 2.0.6; 2.0.7 and to a lesser extent 2.0.8 introduced significant changes.