Difference between revisions of "WebProtegeRoadMap"
From Protege Wiki
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | = WebProtege Roadmap = | + | {{WP1-start}} |
| + | |||
| + | = 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. | 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 6: | Line 8: | ||
__TOC__ | __TOC__ | ||
| + | |||
| + | '''Go back to the [[WebProtege|WebProtege main page]].''' | ||
== Planned features == | == Planned features == | ||
| − | |||
# 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 '' | + | # 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 == | == Feature requests == | ||
| Line 17: | Line 21: | ||
''(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. |
| + | |||
| + | # Provide for searching for references to individuals. | ||
| + | |||
== Completed feature requests == | == Completed feature requests == | ||
| Line 26: | Line 33: | ||
<br /><br /> | <br /><br /> | ||
| − | [[Category:WebProtege documentation]] | + | # 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. | ||
| + | |||
| + | |||
| + | '''Go back to the [[WebProtege|WebProtege main page]].''' | ||
| + | |||
| + | [[Category:WebProtege 1.0 documentation]] | ||
Latest revision as of 17: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.
Contents
Go back to the 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)
- 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.
- Provide for searching for references to individuals.
Completed feature requests
(relocated from first or second sections, when items have been implemented)
- 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.
