Difference between revisions of "WebProtegeRoadMap"

From Protege Wiki
Jump to: navigation, search
m
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= WebProtege Roadmap =
+
{{WP1-start}}
  
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.
+
= WebProtege 1.0 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|feature requests]]''' section.
  
  
Line 7: Line 9:
  
  
== WebProtege planned features ==
+
'''Go back to the [[WebProtege|WebProtege main page]].'''
 +
 
 +
== Planned features ==
 +
 
 +
# Finalize and document the plug-in infrastructure ''(under development)''
 +
# Port server-side code from the Protege 3 APIs to Protege 4 and the OWL-API - alpha SVN version already available. ''medium term''
 +
# Support collaboration for the OWL-API backend, so that WebProtege and a Protege 4 desktop client can ''talk'' to each other.
 +
 
 +
== Feature requests ==
 +
 
 +
''(please add your feature requests here)''
  
# 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'')
+
# Use HTTP links for entities (e.g., classes, properties, and individuals) to make navigation easier.
# Finalize and document the plugin infrastructure ('''under development''')
+
# Provide RESTFul services for accessing/browsing ontologies.
 +
# Implement some kind of paging tree control to make browsing large class trees faster.
  
 +
# Provide for searching for references to individuals.
  
== WebProtege feature request ==
 
  
''(feel free to add here your feature request)''
+
== Completed feature requests ==
  
# Use http links for entities (e.g. classes, properties, individuals) to make navigation easier.
+
''(relocated from first or second sections, when items have been implemented)''
 +
<br /><br />
  
# Provide RESTFul services for accessing/browsing the ontologies
+
# 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 (''part of WebProtege build 200'').
 +
# Provide for editing of instances. (''can use the property field portlet'')
 +
# Improve display of slots with multiple values on the Individuals tab. (''can use the property field portlet'')
 +
# Like the create new classes feature, allow users to create new properties & individuals.
  
  
== Already implemented features ==
+
'''Go back to the [[WebProtege|WebProtege main page]].'''
  
''(moved from first and second section, when an item has been implemented)''
+
[[Category:WebProtege 1.0 documentation]]

Latest revision as of 18:16, April 25, 2013

This page refers to an older version of WebProtege (release 1.0). Please follow the links from the main WebProtege wiki page to get to documentation for the latest WebProtege.


WebProtege 1.0 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.



Go back to the WebProtege main page.

Planned features

  1. Finalize and document the plug-in infrastructure (under development)
  2. Port server-side code from the Protege 3 APIs to Protege 4 and the OWL-API - alpha SVN version already available. medium term
  3. Support collaboration for the OWL-API backend, so that WebProtege and a Protege 4 desktop client can talk to each other.

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.
  1. Provide for searching for references to individuals.


Completed feature requests

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

  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 (part of WebProtege build 200).
  2. Provide for editing of instances. (can use the property field portlet)
  3. Improve display of slots with multiple values on the Individuals tab. (can use the property field portlet)
  4. Like the create new classes feature, allow users to create new properties & individuals.


Go back to the WebProtege main page.