Difference between revisions of "Protege 4 beta announcement"
m |
(incremental save of new work) |
||
| Line 1: | Line 1: | ||
<span style="font-weight:bold; font-size:22px;">Protege 4.0 moves to beta -- August 22nd, 2008</span> | <span style="font-weight:bold; font-size:22px;">Protege 4.0 moves to beta -- August 22nd, 2008</span> | ||
| + | [[Image:P4-beta-screenshot.png|thumb|400px|right|Protege 4.0 Beta]] | ||
| − | Protege 4.0 has been in development in parallel with the Protege 3.x series for approximately 2.5 years. Initial alpha versions were developed by the [http://www.co-ode.org/about/ CO-ODE team] and it is now under active development by CO-ODE, [http://protege.stanford.edu/aboutus/aboutus.html Stanford's Protege team], and several other developers. A considerable amount of work has gone into stabilization of the current | + | |
| + | Protege 4.0 has been in development in parallel with the Protege 3.x series for approximately 2.5 years. Initial alpha versions were developed by the [http://www.co-ode.org/about/ CO-ODE team] and it is now under active development by CO-ODE, [http://protege.stanford.edu/aboutus/aboutus.html Stanford's Protege team], and several other developers. A considerable amount of work has gone into stabilization of the current application and we are very pleased to move the status from alpha to beta. | ||
| Line 24: | Line 26: | ||
<h2>Why are there two versions of Protege in beta (3.4 and 4.0)?</h2> | <h2>Why are there two versions of Protege in beta (3.4 and 4.0)?</h2> | ||
| − | Protege 3.4 | + | Our plans to deploy an official Protege 3.4 release are running a bit behind schedule... Originally, 3.4 was slated to be released in the summer of 2008, but it will now most likely be in early October. When released, Protege 3.4 will continue to be the foundation for Protege-Frames users and a robust platform for OWL 1.0. |
| − | For recommendations about which version of Protege to | + | For more detailed recommendations about which version of Protege might best meets your needs, please refer to our [[Protege4Migration|side-by-side comparison]]. |
<h2>Contribute</h2> | <h2>Contribute</h2> | ||
| − | If you would like to be more involved and help us with plug-ins, documentation, and fielding questions please | + | If you would like to be more involved and help us with plug-ins, documentation, and fielding questions please read our [[Protege4Contributing|guide to contributing]]. |
Revision as of 21:23, August 22, 2008
Protege 4.0 moves to beta -- August 22nd, 2008
Protege 4.0 has been in development in parallel with the Protege 3.x series for approximately 2.5 years. Initial alpha versions were developed by the CO-ODE team and it is now under active development by CO-ODE, Stanford's Protege team, and several other developers. A considerable amount of work has gone into stabilization of the current application and we are very pleased to move the status from alpha to beta.
Contents
Useful Links
- Download Protege 4.0 beta
- Browse the Getting Started Guide
- See an overview of Protege 4.0 features
- Read Protege 4.0 documentation
What's next?
We will be working during the next few weeks to update the main Protege website and Protege Wiki to clarify which documentation refers to version 4.0 beta versus previous versions of Protege.
We are very interested in your feedback on both the application and the documentation. You can contact us via the Protege 4 mailing list.
Also, please keep an eye on Protege 4 status section of this wiki.
Why are there two versions of Protege in beta (3.4 and 4.0)?
Our plans to deploy an official Protege 3.4 release are running a bit behind schedule... Originally, 3.4 was slated to be released in the summer of 2008, but it will now most likely be in early October. When released, Protege 3.4 will continue to be the foundation for Protege-Frames users and a robust platform for OWL 1.0.
For more detailed recommendations about which version of Protege might best meets your needs, please refer to our side-by-side comparison.
Contribute
If you would like to be more involved and help us with plug-ins, documentation, and fielding questions please read our guide to contributing.
