P4 Release Announcement - Revision history

JenniferVendetti at 22:55, May 20, 2011

2011-05-20T22:55:56Z

JenniferVendetti at 00:14, December 4, 2009

2009-12-04T00:14:31Z

JenniferVendetti at 23:41, June 16, 2009

2009-06-16T23:41:34Z

JenniferVendetti at 23:27, June 16, 2009

2009-06-16T23:27:23Z

JenniferVendetti: (checkpoint save)

2009-06-16T23:23:24Z

(checkpoint save)

JenniferVendetti: (checkpoint save)

2009-06-16T23:21:54Z

(checkpoint save)

JenniferVendetti: (checkpoint save)

2009-06-16T23:21:15Z

(checkpoint save)

JenniferVendetti: (checkpoint save)

2009-06-16T23:15:14Z

(checkpoint save)

JenniferVendetti: (checkpoint save)

2009-06-16T23:14:10Z

(checkpoint save)

JenniferVendetti: (checkpoint save)

2009-06-16T23:13:58Z

(checkpoint save)

@@ Line 21: / Line 21: @@
 <h2>Useful Links</h2>
-* [http://protege.stanford.edu/download/registered.html#p4 Download Protege 4.0] (new users, [http://protege.stanford.edu/download/register.html please register first])
+* [http://protege.cim3.net/download/old-releases/4.0/ Download Protege 4.0] (new users, [http://protege.stanford.edu/download/register.html please register first])
 * [[Protege4GettingStarted|Browse the "Getting Started Guide"]]
 * [[Protege4Features|See an overview of Protege 4.0 features]]

← Older revision		Revision as of 00:14, December 4, 2009
Line 1:		Line 1:
−	<span style="font-weight:bold; font-size:22px;">Protege 4.0 Release -- June 16, 2009</span>	+	<br /><span style="font-weight:bold; font-size:22px;">Protege 4.0 Release -- June 16, 2009</span>

	[[Image:P4-beta-screenshot.png\|thumb\|400px\|right\|Protege 4.0 Screenshot]]		[[Image:P4-beta-screenshot.png\|thumb\|400px\|right\|Protege 4.0 Screenshot]]

← Older revision		Revision as of 23:41, June 16, 2009
Line 8:		Line 8:

	__TOC__		__TOC__
		+
		+
		+	<h2>Release Highlights</h2>
		+	* Protege-OWL editor built on top of the open source [http://owlapi.sourceforge.net/ OWL API]
		+	* Support for OWL 2
		+	* Direct, in-memory connection to Pellet and FaCT++ reasoners
		+	* Support for editing multiple ontologies
		+	* Creation, import, and export of user configurable tabs
		+
		+	... and much more! Please refer to our overview of the [[Protege4Features\|Protege 4.0 feature set]].

← Older revision		Revision as of 23:27, June 16, 2009
Line 27:		Line 27:
	In May and June we branched Protege 4.0 and migrated to version 3 of the OWL API. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help write some migration guides for plug-in developers.		In May and June we branched Protege 4.0 and migrated to version 3 of the OWL API. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help write some migration guides for plug-in developers.

−	As a user, if you are desperate to take advantage of some of the late entry OWL 2 features that didn't make it into Protege 4.0, e.g., keys, (and you are good at backing up your work) there will ~~shortly~~ be a 4.1 alpha release available for download.	+	As a user, if you are desperate to take advantage of some of the late entry OWL 2 features that didn't make it into Protege 4.0, e.g., keys, (and you are good at backing up your work) there will be a 4.1 alpha release available for download shortly.

← Older revision		Revision as of 23:23, June 16, 2009
Line 25:		Line 25:
	In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.		In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.

−	In May and June we branched Protege 4.0 and migrated to version 3 of the OWL API. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help write some migration guides for plug-in developers. As a user, if you are desperate to ~~use~~ some of the late entry OWL 2 features that ~~have not made~~ it ~~in to~~ Protege 4.0 (~~such as keys)~~ and you are good at backing up your work there will shortly be a ~~pre-~~alpha release available for ~~people to~~ download.	+	In May and June we branched Protege 4.0 and migrated to version 3 of the OWL API. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help write some migration guides for plug-in developers.
		+
		+	As a user, if you are desperate to take advantage of some of the late entry OWL 2 features that didn't make it into Protege 4.0, e.g., keys, (and you are good at backing up your work) there will shortly be a 4.1 alpha release available for download.

← Older revision		Revision as of 23:21, June 16, 2009
Line 25:		Line 25:
	In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.		In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.

−	In May and June we branched Protege 4.0 and migrated to version 3 of the OWL API. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help ~~develop~~ some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.	+	In May and June we branched Protege 4.0 and migrated to version 3 of the OWL API. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help write some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.

← Older revision		Revision as of 23:15, June 16, 2009
Line 25:		Line 25:
	In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.		In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.

−	~~During~~ May and June, we branched Protege 4.0 and migrated ~~to the newest~~ version of the OWL API ~~(version 3)~~. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help develop some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.	+	In May and June we branched Protege 4.0 and migrated version 3 of the OWL API. After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help develop some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.

← Older revision		Revision as of 23:14, June 16, 2009
Line 25:		Line 25:
	In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.		In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.

−	During May and June, branched Protege 4.0 and migrated to the newest version of the OWL API (version 3). After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help develop some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.	+	During May and June, we branched Protege 4.0 and migrated to the newest version of the OWL API (version 3). After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help develop some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.

← Older revision		Revision as of 23:13, June 16, 2009
Line 25:		Line 25:
	In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.		In order to keep Protege 4.0 as stable as possible for users and contributors over the last year, a lot of work has been happening in the background on the [http://owlapi.sourceforge.net/ OWL API] to follow the specification as it changes over time. Some of the modifications to the language have inevitably been backwards incompatible - mostly vocabulary but also some structural changes. We have done our best to keep Protege 4.0 as isolated from these changes as possible and decided to release based on version 2 of the OWL API so that existing plug-ins, user interface, and ontologies are stable and compatible.

−	During May and June, ~~a branch of~~ Protege 4.0 ~~was~~ migrated to the newest version of the OWL API (version 3) ~~and is now stabilizing~~.	+	During May and June, branched Protege 4.0 and migrated to the newest version of the OWL API (version 3). After the [http://protege.stanford.edu/conference/2009/index.html Protege Conference], this branch will become the main development trunk where we plan to continue implementation of new features. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help develop some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.
−	After the Protege ~~conference~~, this branch ~~(Protege 4.1)~~ will become the main development trunk ~~and all~~ new features ~~will be developed on the new platform~~. There are still likely to be some shifts in the code over the next few months, but we would like developers to have a look and let us know how you think we are doing. In the meantime, all plug-ins from CO-ODE will be migrated to the updated platform and we will use this process to help develop some migration guides for plug-in developers. As a user, if you are desperate to use some of the late entry OWL 2 features that have not made it in to Protege 4.0 (such as keys) and you are good at backing up your work there will shortly be a pre-alpha release available for people to download.