eConstruct infrastructure
Short description of the server side stuff of eConstruct: taxonomyserver, catalogueserver.
The EConstructProject defined a central set of applications that formed a central set of services for persons/programs using bcxml. It was defined in april 2001 by CelsonLima, Bruno Fies (both CSTB) and myself and Joost Fleuren (both TU Delft).
It's known under several names (Resource DB (current official one, I believe), Resource DB server, Resource server, econstruct framework, etc.). I absolutely hate the un-clear name "resource DB", so stubbornly I call it eConstruct infrastructure...
In current terminology it consists of three parts:
- TaxonomyServer - the part that contains one or more taxonomies and provides some WebServices (read: SOAP) to other programs (and other parts of the EConstructInfrastructure)
- SupplierCatalogueServer - stores catalogues and searches in them
- ResourceDBFrontend - The webpages around both servers, entry point for humans.
2004 comments: Apart from a little demo-ing with the catalogue server, only the taxonomy server still sees a little bit of active use. Mind, it's still pretty OK to show the taxonomyserver running live, for instance in Greek (ok, "greeklish", the taxonomy couldn't handle the greek characters).
Jeff Stephens uses an updated (much speedier) version (called "definitionserver") to easily browse through a British classification system. (That is, once I fix the thing: some error on newer tomcats).
