-
Notifications
You must be signed in to change notification settings - Fork 5
Home
Carlos Rueda edited this page Jan 12, 2015
·
14 revisions
Comparison between current "ont" and new "orr-ont":
(this is preliminary, not exhaustive, and possibly not completely accurate, but should give a good sense of the work being done and planned)
| Aspect | ont | orr-ont |
|---|---|---|
| Request for latest version | Converts from the versioned form | Immediately returned |
| Output formats | RDF/XML, N3 | RDF/XML, N3, JSON-LD |
| Request in other format | Conversion always made | Conversion only once then cached |
| Ontology versions stored in | Versioned form | Un-versioned form |
| "self-hosted" dispatch | Supported | Supported |
| Organization (authority) support | Very minimal | Better supported (1) |
| Permissions | Minimal | Significantly improved |
| Main dependencies, database | BioPortal, MySQL | MongoDB |
| Language/dispatch mechanism | Java / Servlet | Scala / Scalatra |
(1) Organizations are explicitly modeled in orr-ont. All ontology submissions are associated with corresponding organizations. An organization has set of members, and only members can register ontologies for that organization.
In general, because of the new and simplified mechanisms in orr-ont, a number of benefits are expected:
- Easier installation because of reduced number of important dependencies
- Better performance (possibly very significant)