Difference between revisions of "WebProtegeRoadMap"

From Protege Wiki
Jump to: navigation, search
(added feature request from ron schultz)
Line 9: Line 9:
 
== Planned features ==
 
== 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'')
+
# 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)''
 
# Finalize and document the plug-in infrastructure ''(under development)''
# Port to Protege 4 and the OWL-API ''(planned for 1st quarter of 2009)''
+
# Port server-side code from the Protege 3 APIs to Protege 4 and the OWL-API.
 +
 
  
 
== Feature requests ==
 
== Feature requests ==
Line 17: Line 18:
 
''(please add your feature requests here)''
 
''(please add your feature requests here)''
  
# Use HTTP links for entities (e.g., classes, properties, and individuals) to make navigation easier
+
# Use HTTP links for entities (e.g., classes, properties, and individuals) to make navigation easier.
# 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.
 +
# Improve display of slots with multiple values on the Individuals tab.
 +
 
  
 
== Completed feature requests ==
 
== Completed feature requests ==

Revision as of 16:33, January 5, 2009

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.



Planned features

  1. 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).
  2. Finalize and document the plug-in infrastructure (under development)
  3. Port server-side code from the Protege 3 APIs to Protege 4 and the OWL-API.


Feature requests

(please add your feature requests here)

  1. Use HTTP links for entities (e.g., classes, properties, and individuals) to make navigation easier.
  2. Provide RESTFul services for accessing/browsing ontologies.
  3. Implement some kind of paging tree control to make browsing large class trees faster.
  4. Improve display of slots with multiple values on the Individuals tab.


Completed feature requests

(relocated from first or second sections, when items have been implemented)