[408175] [proposal] technology.ogee
Updated proposal per email request.
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=408175
diff --git a/technology.ogee/proposal.html b/technology.ogee/proposal.html
index 32574a3..1820455 100644
--- a/technology.ogee/proposal.html
+++ b/technology.ogee/proposal.html
@@ -89,7 +89,6 @@
<ul>
<li>Model new OData services</li>
<li>Visualize and explore existing OData services</li>
- <li>Consume existing OData services from Java SE environment</li>
<li>Extend Ogee framework for:</li>
<ul>
<li>Consumption from other environments</li>
@@ -100,9 +99,9 @@
<p>The architecture of the project is open and extensible through Eclipse extension points.</p>
- <p>Ogee lowers the barrier for developers that want to produce and consume data, by bringing the OData advantages to the fingertips of Eclipse developers.
+ <p>Ogee lowers the barrier for developers who want to produce and consume data, by bringing the OData advantages to the fingertips of Eclipse developers.
It enables the community to contribute to this project by:
- extending our contribution with more provider environemtns, more consumption environments, ensuring interoperability
+ extending our contribution with more provider environments, more consumption environments, ensuring interoperability
across various industry standards, and promoting OData by easing the development process.</p>
<h2>Description</h2>
@@ -115,12 +114,11 @@
<p>Ogee provides Eclipse-based developer tools for the provisioning and
consumption of OData services regardless of the service provisioning platform and service consuming
technology. It comprises a graphical OData Model Editor for the creation of OData models that
- define the data structure required and service consumption toolkits that allow you to create and
- design the applications with which you can consume the data retrieved from your OData producer.</p>
+ define the data structure required. The models can then be exported as service metadata document. </p>
<p>More details can be found in the EclipseCon presentation:
<a href="http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/OData%20unleashed!_0.pdf">
- OData Unleashed! Let's learn how to explot it</a></p>
+ OData Unleashed! Let's learn how to exploit it</a></p>
<!--
<h2>Why Eclipse?</h2>
@@ -136,6 +134,7 @@
<h2>Initial Contribution</h2>
+
<!--
Projects are expected to arrive at Eclipse with existing code.
@@ -151,8 +150,8 @@
there was also a decision to invest in a complimentary tool for developers. This tool was developed as an Eclipse plug-in and it allows
developers to create and consume services with SAP NetWeaver Gateway. As the product evolved, we realized
(also from feedback we got from partners and customers) that the tool we built can be used for creation and consumption of any
-OData service (not only services on SAP NetWeaver Gateway). In addition, OData will be standardized at
-<a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata">OASIS</a> this year.
+OData service (not only services on SAP NetWeaver Gateway). In addition, OData is standardized at
+<a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata">OASIS</a>.
For these reasons, we believe that the demand for OData development in Eclipse will grow and hence we would like
to contribute an OData Development Tool for Eclipse based on the product we built internally at SAP.</p>
@@ -178,12 +177,12 @@
<p>The following individuals are proposed as initial committers to the project:</p>
<ul>
-<li>Boris Tsirulnik, SAP (project lead)</li>
-<li>Stanislav Lvovsky, SAP</li>
-<li>Ravit Sela, SAP</li>
-<li>Michal Keidar, SAP</li>
-<li>Dany Shapiro, SAP</li>
-<li>Gal Roter, SAP</li>
+<li>Klaus Deissner, SAP (project lead)</li>
+<li>Om Band, SAP</li>
+<li>Sounak Basu, SAP</li>
+<li>Suparna Deb, SAP</li>
+<li>Elizabeth Riemann, SAP</li>
+<li>Ashish Singh, SAP</li>
</ul>
<!--
@@ -240,7 +239,16 @@
</ul>
<h2>Project Scheduling</h2>
-
+<table width="50%" border="1">
+ <tr>
+ <th width="30%">When</th>
+ <th>What</th>
+ </tr>
+ <tr>
+ <td>Early Q1, 2014</td>
+ <td>Initial contribution</td>
+ </tr>
+</table>
<!--
Describe, in rough terms, what the basic scheduling of the project will
be. You might, for example, include an indication of when an initial contribution
@@ -256,9 +264,9 @@
has been posted live for the community to view and comment.
-->
-<table>
+<table width="50%" border="1">
<tr>
- <th>Date</th>
+ <th width="30%">Date</th>
<th>Change</th>
</tr>
<tr>
@@ -269,6 +277,15 @@
<td>10-May-2013</td>
<td>First update</td>
</tr>
+ <tr>
+ <td rowspan="2" valign="top">19-December-2013</td>
+ <td>New list of committers Adjusted description to scope of initial contribution</td>
+ </tr>
+ <tr>
+ <td>Adjusted description to scope of initial contribution</td>
+ </tr>
+
+
</table>
</body>
</html>
\ No newline at end of file
