I'm currently planning something similar for later this year and was
wondering if your request for questions and comments are more a sense
of gaining community feedback, or if the design is still in flux, i.e.,
is it pretty much a fixed entity or is there still room for change?
Murray Altheim <murray10 at altheim dot com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
> First, our goal is indeed to get community feedback as we want this
> API to be generic and useful outside of the specific project we need
> it for.
Wouldn't it make sense to move the protocol discussion to a neutral
mailing list like Infoloom ?
The implementation details can discussed here, though.
> (2) We plan to use Restlet (http://www.restlet.org/) to implement this
> RESTful Topic Maps API. How should we practically integrate our work
> with Ontopia? I suppose initially in the sandbox environment?
A while ago I was also involved with Restlet but now I've switched to
JAX-RS. Restlet provides a JAX-RS implementation as well (not sure if
it has matured in the meantime), so you want to use Restlet, you can
use its JAX-RS implementation and Restlet would just be one
implementation of many others.
Restlet is a proprietary API while JAX-RS provides more freedom: You
can use Apache Wink, RestEasy, Jersey etc...
Anyway, Restlet isn't a bad choice at all (a big plus is that it
provides native connectors which do not rely on Servlets), but I'd
I've just opened up a thread with some questions on the RESTful Topic
Maps API over on topicmapmail for those interested.