[Ref-Links] S-Link-S Calculator 0.9 released

[Eric Hellman <eric@hellman.net>]

The first public release of S-Link-S Software has arrived!

S-Link-S Calculator is a free license for experimental and evaluation
purposes only, and is distributed with source code. This release is
directed at people with experience running java programs. To receive the
download address, please send e-mail with your contact information to
mailto:slinks@openly.com

The S-Link-S Template language has reached version 1.0, and should be
considered stable enough to use as a basis for development. The new version
of the spec is at http://www.openly.com/SLinkS/SLinkS.html

The new template DTD is at http://www.openly.com/SLinkS/slinks.dtd (do a
view source if you see nothing in your browser.)

Minor changes were made to the metadata sheme, which is still a ways from
being ready. The "resolution" property has been removed; the last changes
made to the template language subsumed this function.


S-Link-S Calculator


Release Notes
Version 0.9 June 3, 1999

This is the first public release of S-Link-S software, therefore you should
be aware of the possibility of digital insectivorae.

What is implemented:
Version 1.0 of the S-Link-S template language is thoroughly implemented,
with the following exceptions:
1. A DOi look-up to Wiley DOi's is provided as a demo in place of a real
DOi look-up. The lookup can be modified by changing DOi.xml
2. There's a digital signature stub, but no actual implementation. Digital
signatures will involve charges to linking targets requiring signed URL's.

What IS NOT implemented:
1. S-Link-S database client functions are not implemented. The S-Link-S
central database is not yet in operation.
2. There are no batch processing API's. There are no functions for parsing
bibliographic data out of a reference. Feedback about what's most important
is welcomed.

Notes:
1. The XML4J parser in validating mode is pretty fussy about having xml
with correct syntax. For production, I expect that a non-validating parser
will be preferable, however, non-validation requires that all entities be
defined in an internal DTD subset. (or at least we'll put in some better
parser exception handling. For development, the fussy parser is actually a
good thing.

2. There are some cosmetic cross platform issues associated with AWT.

More info at http://www.openly.com/SLinkS/Calculator/


Eric
Eric Hellman
Openly Informatics, Inc.
http://www.openly.com/           Tools for 21st Century Scholarly Publishing

------------------------------------------------------
Ref-Links maillist  -  Ref-Links@doi.org
http://www.doi.org/mailman/listinfo/ref-links