Difference between revisions of "WebProtegeRoadMap"
From Protege Wiki
m |
(→WebProtege feature request) |
||
| Line 19: | Line 19: | ||
# Use http links for entities (e.g. classes, properties, individuals) to make navigation easier. | # Use http links for entities (e.g. classes, properties, individuals) to make navigation easier. | ||
| − | |||
# Provide RESTFul services for accessing/browsing the ontologies | # Provide RESTFul services for accessing/browsing the ontologies | ||
| − | |||
== Already implemented features == | == Already implemented features == | ||
''(moved from first and second section, when an item has been implemented)'' | ''(moved from first and second section, when an item has been implemented)'' | ||
Revision as of 17:34, December 8, 2008
WebProtege Roadmap
This page contains a partially ordered list of items that are currently in development for WebProtege or that are planned. If you have any feature requests, please add them in the Feature Request section.
Contents
WebProtege planned features
- Storing user defined layouts on the server: e.g. storing the enabled tabs, ordering and size of portles in a tab, across different sessions. (under development, part of next release of WebProtege)
- Finalize and document the plugin infrastructure (under development)
- Port to Protege 4 and the OWL-API (planned for 1st quarter of 2009)
WebProtege feature request
(feel free to add here your feature request)
- Use http links for entities (e.g. classes, properties, individuals) to make navigation easier.
- Provide RESTFul services for accessing/browsing the ontologies
Already implemented features
(moved from first and second section, when an item has been implemented)
