Difference between revisions of "WebProtegeRoadMap"
From Protege Wiki
(minor edits and added this to webprotege doc category) |
|||
| Line 12: | Line 12: | ||
# Finalize and document the plug-in infrastructure ''(under development)'' | # Finalize and document the plug-in infrastructure ''(under development)'' | ||
# Port to Protege 4 and the OWL-API ''(planned for 1st quarter of 2009)'' | # Port to Protege 4 and the OWL-API ''(planned for 1st quarter of 2009)'' | ||
| − | |||
== Feature requests == | == Feature requests == | ||
| Line 21: | Line 20: | ||
# Provide RESTFul services for accessing/browsing ontologies | # Provide RESTFul services for accessing/browsing ontologies | ||
# Implement some kind of paging tree control to make browsing large class trees faster | # Implement some kind of paging tree control to make browsing large class trees faster | ||
| − | |||
== Completed feature requests == | == Completed feature requests == | ||
''(relocated from first or second sections, when items have been implemented)'' | ''(relocated from first or second sections, when items have been implemented)'' | ||
| + | <br /><br /> | ||
[[Category:WebProtege documentation]] | [[Category:WebProtege documentation]] | ||
Revision as of 16:48, December 8, 2008
WebProtege Roadmap
This page contains a partially ordered list of items that are currently under development and/or included in future development plans for WebProtege. If you have feature requests, please add them to the feature requests section.
Contents
Planned features
- Storing user defined layouts on the server, e.g., storing the list of enabled tabs, ordering and size of portlets in a tab, etc., across different sessions. (under development, will be in the next release)
- Finalize and document the plug-in infrastructure (under development)
- Port to Protege 4 and the OWL-API (planned for 1st quarter of 2009)
Feature requests
(please add your feature requests here)
- Use HTTP links for entities (e.g., classes, properties, and individuals) to make navigation easier
- Provide RESTFul services for accessing/browsing ontologies
- Implement some kind of paging tree control to make browsing large class trees faster
Completed feature requests
(relocated from first or second sections, when items have been implemented)
