<?xml version="1.0" encoding="utf-8" ?> | |
<!-- | |
<copyright> | |
Copyright (c) 2012-2014 SAP SE. | |
All rights reserved. This program and the accompanying materials | |
are made available under the terms of the Eclipse Public License v1.0 | |
which accompanies this distribution, and is available at | |
http://www.eclipse.org/legal/epl-v10.html | |
Contributors: | |
SAP SE - initial API and implementation and/or initial documentation | |
</copyright> | |
--> | |
<introContent> | |
<extensionContent id="org.eclipse.ogee.intro.overview" | |
style="css/overview.css" alt-style="css/swt.properties" name="Ogee Workbench" | |
path="overview/@"> | |
<group style-id="content-group" id="workbench-group-ogee1" | |
importance="high"> | |
<img src="/res/images/ODataLogo-32.gif" /> | |
<link label="Ogee" url="Ogee.html" id="org.eclipse.ogee" | |
style-id="content-link"> | |
<text>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 meta-data document. | |
</text> | |
</link> | |
</group> | |
</extensionContent> | |
<extensionContent id="org.eclipse.ogee.intro.whatsnew" | |
style="css/overview.css" alt-style="css/swt.properties" name="Ogee Workbench" | |
path="whatsnew/@"> | |
<group style-id="content-group" id="workbench-group-ogee2" | |
importance="high"> | |
<img src="/res/images/ODataLogo-32.gif" /> | |
<link label="Ogee" url="Ogee.html" id="org.eclipse.ogee" | |
style-id="content-link"> | |
<text>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 meta-data document. | |
</text> | |
</link> | |
</group> | |
</extensionContent> | |
</introContent> |