| <!-- |
| This document is provided as a template along with some guidance for creating |
| your project proposal. This is just a template. Feel free to change it as |
| you see fit (add sections, remove section). We feel, however, that the |
| suggestions represented in this document represent the reasonable minimum |
| amount of information to move forward. |
| |
| Please keep the formatting in this document simple. Please do not edit |
| this document in Microsoft Word as it adds huge piles of markup that make |
| it difficult to restyle. |
| |
| More information is available here: |
| |
| http://wiki.eclipse.org/Development_Resources/HOWTO/Pre-Proposal_Phase |
| |
| Direct any questions about this template to emo@eclipse.org |
| --> |
| |
| <html> |
| <head> |
| |
| <!-- |
| Include the title here. We will parse it out of here and include it on the |
| rendered webpage. Do not duplicate the title within the text of your page. |
| --> |
| |
| <title>Ogee</title> |
| </head> |
| |
| <!-- |
| We make use of the 'classic' HTML Definition List (dl) tag to specify |
| committers. I know... you haven't seen this tag in a long while... |
| --> |
| |
| <style> |
| dt { |
| display: list-item; |
| list-style-position:outside; |
| list-style-image:url(/eclipse.org-common/themes/Phoenix/images/arrow.gif); |
| margin-left:16px; |
| } |
| dd { |
| margin-left:25px; |
| margin-bottom:5px; |
| } |
| </style> |
| |
| <body> |
| <p>The Ogee project is a proposed open source project under the <a |
| href="http://www.eclipse.org/projects/project_summary.php?projectid=technology">Technology Top Level Project</a>.</p> |
| |
| <!-- |
| The communication channel must be specified. Typically, this is the |
| "Proposals" forum. In general, you don't need to change this. |
| --> |
| <p>This proposal is in the Project Proposal Phase (as defined in the |
| Eclipse Development Process) and is written to declare its intent and |
| scope. We solicit additional participation and input from the Eclipse |
| community. Please send all feedback to the |
| <a href="http://www.eclipse.org/forums/eclipse.proposals">Eclipse Proposals</a> |
| Forum.</p> |
| |
| <h2>Background</h2> |
| |
| <!-- |
| Optionally provide the background that has lead you to creating this project. |
| --> |
| |
| <p>There is a vast amount of data available today and data is now being collected and stored at a rate never seen before. |
| The <a href="http://www.odata.org/">Open Data Protocol (OData)</a> is a Web protocol used for querying and updating data. |
| It provides a way to unlock your data and free it from silos that exist in applications today. |
| OData does this by applying and building upon Web technologies such as HTTP, |
| Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.</p> |
| |
| <p>As OData's influence and presence in the industry is raising |
| (OData is the data API for Microsoft Azure, SAP NetWeaver Gateway, eBay, Stackoverflow and more.), |
| there is a clear need for an integrated OData support in Eclipse both for producing and consuming services.</p> |
| |
| <h2>Scope</h2> |
| |
| <!-- |
| All projects must have a well-defined scope. Describe, concisely, what |
| is in-scope and (optionally) what is out-of-scope. An Eclipse project |
| cannot have an open-ended scope. |
| --> |
| <p>The main goal of Ogee project is to provide tools for developers who want to consume and produce data using the OData protocol.</p> |
| |
| <p>More specifically, Ogee allows developers to:</p> |
| <ul> |
| <li>Model new OData services</li> |
| <li>Visualize and explore existing OData services</li> |
| <li>Extend Ogee framework for:</li> |
| <ul> |
| <li>Consumption from other environments</li> |
| <li>Provisioning of OData services for different provider environments</li> |
| <li>Importing OData service models from different sources</li> |
| </ul> |
| </ul> |
| |
| <p>The architecture of the project is open and extensible through Eclipse extension points.</p> |
| |
| <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 environments, more consumption environments, ensuring interoperability |
| across various industry standards, and promoting OData by easing the development process.</p> |
| |
| <h2>Description</h2> |
| |
| <!-- |
| Describe the project here. Be concise, but provide enough information that |
| somebody who doesn't already know very much about your project idea or domain |
| has at least a fighting chance of understanding its purpose. |
| --> |
| <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. 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 exploit it</a></p> |
| |
| <!-- |
| <h2>Why Eclipse?</h2> |
| |
| <!-- |
| Answer these two questions: What value does this project bring to the Eclipse |
| community? What value do you expect to obtain from hosting your project at Eclipse? |
| |
| What value do you get by having your project at Eclipse over and above the value |
| of hosting at Eclipse Labs? |
| --> |
| |
| |
| <h2>Initial Contribution</h2> |
| |
| |
| <!-- |
| Projects are expected to arrive at Eclipse with existing code. |
| |
| Describe the existing code that will be contributed to the project. Please provide |
| a couple of paragraphs describing the code with modest detail, including important |
| information like code ownership (who holds the copyright?), and some consideration |
| of community that exists around the code. Include a listing of third-party libraries |
| and associated licenses. |
| --> |
| <p>The initial code contribution will come from SAP. |
| Since SAP has decided to adopt OData as a mean for provisioning its data |
| (<a href="http://scn.sap.com/community/netweaver-gateway">SAP NetWeaver Gateway</a>), |
| 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 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> |
| |
| <!-- |
| <h2>Legal Issues</h2> |
| |
| <!-- |
| Please describe any potential legal issues in this section. Does somebody else |
| own the trademark to the project name? Is there some issue that prevents you |
| from licensing the project under the Eclipse Public License? Are parts of the |
| code available under some other license? Are there any LGPL/GPL bits that you |
| absolutely require? |
| --> |
| |
| <h2>Committers</h2> |
| |
| <!-- |
| List any initial committers that should be provisioned along with the |
| new project. Include affiliation, but do not include email addresses at |
| this point. |
| --> |
| |
| <p>The following individuals are proposed as initial committers to the project:</p> |
| |
| <ul> |
| <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> |
| |
| <!-- |
| <dl> |
| <dt>Committer 1, Affiliation</dt> |
| <dd>Committer 1 is a committer on the *** project where he has made significant contributions over |
| many years. S/he will be contribute to the *** functionality in this new project.</dd> |
| <dt>Committer 2, Affiliation</dt> |
| <dd>Committer 2 has provided significant contributions to the existing code base. S/he will contribute |
| to the *** functionality in this new project. |
| </dd> |
| </dl> |
| --> |
| |
| <p>We welcome additional committers and contributions.</p> |
| |
| <!-- |
| Describe any initial contributions of code that will be brought to the |
| project. If there is no existing code, just remove this section. |
| --> |
| |
| <h2>Mentors</h2> |
| |
| <!-- |
| New Eclipse projects require a minimum of two mentors from the Architecture |
| Council. You need to identify two mentors before the project is created. The |
| proposal can be posted before this section is filled in (it's a little easier |
| to find a mentor when the proposal itself is public). |
| --> |
| |
| <p>The following Architecture Council members will mentor this |
| project:</p> |
| |
| <ul> |
| <li>Ed Merks</li> |
| <li>Naci Dai</li> |
| </ul> |
| |
| <h2>Interested Parties</h2> |
| |
| <!-- |
| Provide a list of individuals, organisations, companies, and other Eclipse |
| projects that are interested in this project. This list will provide some |
| insight into who your project's community will ultimately include. Where |
| possible, include affiliations. Do not include email addresses. |
| --> |
| |
| <p>The following individuals, organisations, companies and projects have |
| expressed interest in this project:</p> |
| |
| <ul> |
| <li>Somebody, Affiliation</li> |
| <li>Somebody else, Affiliation</li> |
| </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 |
| should be expected, when your first build will be ready, etc. Exact |
| dates are not required. |
| --> |
| |
| <h2>Changes to this Document</h2> |
| |
| <!-- |
| List any changes that have occurred in the document here. |
| You only need to document changes that have occurred after the document |
| has been posted live for the community to view and comment. |
| --> |
| |
| <table width="50%" border="1"> |
| <tr> |
| <th width="30%">Date</th> |
| <th>Change</th> |
| </tr> |
| <tr> |
| <td>28-April-2013</td> |
| <td>Document created</td> |
| </tr> |
| <tr> |
| <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> |