Difference between revisions of "Peregrine Architecture Specification"
From BioAssist
m (added Peregrine Application Layers) |
m (added memory info) |
||
| Line 32: | Line 32: | ||
| + | | + | ||
| + | | + | ||
| − | | | + | | depends on underlying |
|- | |- | ||
|align="left"| Can read compressed data | |align="left"| Can read compressed data | ||
| − | | | + | | not relevant |
| – | | – | ||
| + | | + | ||
| − | | | + | | depends on underlying |
| + | |- | ||
| + | |align="left"| Needs additional memory | ||
| + | | – | ||
| + | | + | ||
| + | | – | ||
| + | | – | ||
|} | |} | ||
Revision as of 17:43, 17 March 2010
Contents
Peregrine API
The collaboration between interfaces and some of implementation packages are displayed on this diagram:
Implementation details
- OntologyDB is using Spring JDBC library.
- PeregrineWS is build using Spring-WS technology.
Ontology backends
| Features | DBOntologyImpl[1] | SingleFileOntologyImpl[2] | FileFlyweightProcessingOntologyImpl [3] | CompoundOntologyImpl[4] |
|---|---|---|---|---|
| Is modifiable ontology | + | – | – | + |
| Is flyweight processing ontology | + | + | + | – |
| Can handle UTF-8 data | + | + | + | depends on underlying |
| Can read compressed data | not relevant | – | + | depends on underlying |
| Needs additional memory | – | + | – | – |
Typical flows
Please, check details about indexing process to discover more about how Peregrine searches for concepts and disambiguation steps to learn more about concept disambiguation.
Peregrine Subprojects & Packaging
Peregrine Application Layers
