svn commit: r32 - trunk/www/index.html

donaldcameron at osgeo.org donaldcameron at osgeo.org
Fri Jul 14 15:59:17 EDT 2006


Author: donaldcameron
Date: 2006-07-14 19:59:17+0000
New Revision: 32

Modified:
   trunk/www/index.html

Log:
FDO2
July 2006 website release

Modified: trunk/www/index.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/index.html?view=diff&rev=32&p1=trunk/www/index.html&p2=trunk/www/index.html&r1=31&r2=32
==============================================================================
--- trunk/www/index.html	(original)
+++ trunk/www/index.html	2006-07-14 19:59:17+0000
@@ -1,61 +1,172 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+
 <html>
-  <head>
-    <title>Feature Data Objects</title>
-  </head>
-  <body>
-   <script type="text/javascript">
-      // This code removes the project page title and information. It may need to change when
-	  // the CEE platform is upgraded.
-   
-      function replaceLinks() {   
-         try {
-		 	var apphead = document.getElementById("apphead");
-			if (apphead != null) {
-				apphead.innerHTML = "";
-			}	
-            var projecthome = document.getElementById("projecthome");
-			if (projecthome != null) {
-				var tableCollection = projecthome.getElementsByTagName("table");
-				if (tableCollection[0] != null)	{
-					rowCount = tableCollection[0].rows.length;
-					for (i = 0; i < rowCount; i++) {
-						tableCollection[0].deleteRow(0);
-					}
-				}    
-			}  
-          } catch (e) {
-          }
-      }
-      window.onload=replaceLinks;
-   </script> 
-   
-  <h1>Feature Data Objects - Project Home</h1>
-  Welcome to the home of Feature Data Objects.
-  <p>FDO Open Source is a new Data Objects API that was originally developed by Autodesk and contributed to the Open Source Geospatial Foundation. Learn more, get involved or download the software today. There are several ways to participate either as a <a href="user.html">user</a> or <a href="developer.html">contributor</a>. Your participation is welcome!</p>
-  <div class="h2"><h2>Description</h2>
-  <p>Feature Data Objects (FDO) is an API for manipulating, defining, and analyzing geospatial information regardless of where it is stored. FDO uses a provider-based model for supporting a variety of geospatial data sources, where each provider typically supports a particular data format or data store.</p>
-  <p>At this point Feature Data Objects is being offered as a preview for use with MapGuide Open Source. The links below  allow you to download a full copy of the source code with FDO providers for ESRI SHP and a new format created for MapGuide called the Spatial Database Format (SDF). FDO will become a full open-source project in the coming months, so stay tuned to this page for more information, additional providers, and the launch of FDO as an active open source project. </p>
-  <p>Feature Data Objects is free, open source software licensed under the <a href="lgpl.html">LGPL</a>.</p>
-  </div>
-  <div class="h2">
-  <h2>Announcements</h2>
-  <p>[Coming Soon]</p>
-  </div>
-  <div class="h2">
-  <h2>Releases</h2>
-  <p><a href="downloads.html">Downloads</a></p>
-  <p><a href="documentation.html">Documentation</a></p>
-  </div>
-  <div class="h2"><h2>Essentials</h2>
-  <p><a href="about.html">About</a></p>
-  <p><a href="faq.html">FAQ</a></p>
-  <p>Features [Coming Soon]</p>
-  <p>Requirements [Coming Soon]</p>
-  <p>Getting Started [Coming Soon]</p>
-  </div>
-  <div class="h2"><h2>Get Involved</h2>
-  <p><a href="user.html">As a User</a></p>
-  <p><a href="developer.html">As a Contributor</a></p>
-  </div>
-  </body>
+<head>
+  <title>Feature Data Objects Open Source</title>
+  <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+</head>
+
+<body>
+  <script type="text/javascript">
+  // This code removes the project page title and information. It may need to change when
+  // the CEE platform is upgraded.
+  function replaceLinks() {
+     try {
+       var apphead = document.getElementById("apphead");
+       if (apphead != null) {
+          apphead.innerHTML = "";
+       }
+       var projecthome = document.getElementById("projecthome");
+       if (projecthome != null) {
+         var tableCollection = projecthome.getElementsByTagName("table");
+         if (tableCollection[0] != null) {
+           rowCount = tableCollection[0].rows.length;
+           for (i = 0; i < rowCount; i++) {
+              tableCollection[0].deleteRow(0);
+           }
+         }    
+       }  
+     } catch (e) {
+     }
+   }
+   window.onload=replaceLinks;
+  </script>
+
+  <table>
+    <tr>
+      <td align="left" valign="top" width="70%">
+        <div class="h2">
+		  <h2>Feature Data Objects Open Source - Project Home</h2>
+		  <p>
+			The Feature Data Objects API
+			provides a generic, command-based interface to a number of back-end data source
+			technologies for storing, retrieving, updating, and analyzing
+			GIS (Geographic Information System) data.
+			</p>
+			<p>
+			FDO Geometry is based on the
+			<a href="http://portal.opengeospatial.org/files/?artifact_id=829">OpenGIS Simple Features Implementation Specification for SQL</a>
+			(version 1.1, document 99-049),
+			but is extended to include z and measure dimensions and circular arcs.
+			The FDO XML format for schema is based on the
+			<a href="http://portal.opengeospatial.org/files/?artifact_id=1034">Open GIS Consortium Geography Markup Language</a> (version 2.1.1, document 02-009).
+			The schema model is object-based using classes and properties and is
+			independent of any physical storage format.
+			</p>
+			<p>
+			FDO provides a model for extending
+			its interface to additional data source technologies.
+			The generic API is extensible, and it is possible to add
+			custom commands to a particular provider. A provider
+			is a specific implementation of the FDO API that provides access
+			to data stored in a particular data source technology. For example,
+			the OSGeo FDO Provider for MySQL provides access to GIS data stored in
+			a MySQL database, and the OSGeo FDO Provider for SHP provides access to
+			GIS data stored in a SHP file.
+			The extent to which a provider implements the FDO API is limited
+			by the native capabilities of the underlying data source technology.
+			</p>
+			<p>
+			A client application creates a connection to a provider and then uses
+			the connection object to create command objects for FDO actions
+			such as Select.
+			The client uses the command object to set the command parameters
+			with the option of leaving some parameters with default values.
+			Where appropriate such as in the case of Select, execution of the
+			command returns a reader object containing the results of the command.
+			</p>
+			<p>
+			A client application can use the FDO Capabilities API to determine
+			what services a particular provider offers.
+			For example, the OSGeo FDO Provider for SDF supports the insertion of
+			data, and the OSGeo FDO Provider for WMS does not.
+			</p>
+			<p>
+			The storage of FDO feature data can be modeled as a containment hierarchy.
+			</p>
+			<ul>
+				<li>
+				A data source may contain one or more data stores.
+				</li>
+				<li>
+				A data store may contain one or more feature schemas and one or more spatial contexts.
+				</li>
+				<li>
+				A feature schema may contain one or more features classes.
+				</li>
+				<li>
+				A feature class contains a feature geometry, optionally one or more
+				non-feature geometry properties, and optionally other types of properties.
+				</li>
+			</ul>
+        </div>
+
+        <div class="h2">
+		   <h2>Developer Spotlight</h2>
+			<p>TBD</p>	 
+        </div>
+
+        <div class="h2">
+			<h2>This Week in FDO</h2>
+			<p>TBD</p>
+        </div>
+      </td>
+
+      <td valign="top" halign="left" width="55%">
+        <table>
+          <tr>
+            <td>
+              <div class="h2">
+					<h2>Announcements</h2>
+					<p>TBD</p>
+              </div>
+            </td>
+          </tr>
+
+          <tr>
+            <td align="left" valign="top">
+              <div class="h2">
+				 <h2>Essentials</h2>
+					<a href="history.html">History</a><br>
+					<a href="productsUsingFdo.html">Products Using FDO</a><br>
+					<a href="featureDescriptions.html">Feature Descriptions</a><br>
+               <a href="OSProviderOverviews.html">Open Source Provider Overviews</a><br>
+					<a href="OSFeatureMatrix.html">Open Source Feature Matrix</a><br>
+					<!--
+					<a href="enterpriseProviderOverviews.html">Enterprise Provider Overviews</a><br>
+					<a href="enterpriseFeatureMatrix.html">Enterprise Feature Matrix</a><br>
+					-->
+					<a href="roadMap.html">Road Map</a><br>
+					<a href="systemRequirements.html">Requirements</a><br>
+					<a href="gettingStarted.html">Getting Started</a><br>
+               <a href="faq.html">FAQ</a><br>
+					<a href="HOWTOWriteAProvider.html">HOWTO: Write a Provider</a><br>
+					<a href="licenceAndGovernance.html">Licence and Governance</a><br>
+					<a href="glossary.html">Glossary</a>
+              </div
+            </td>
+          </tr>
+
+          <tr>
+            <td align="left" valign="top">
+              <div class="h2">
+					<h2>Releases</h2>
+					<h3>FDO Open Source Beta</h3>
+                <a href="downloads.html">Downloads</a><br>
+					 <a href="documentation.html">Documentation</a><br>
+              </div>
+
+              <div class="h2">
+					<h2>Get Involved</h2>
+					<a href="getUsersInvolved.html">As a User</a><br>
+					<a href="getContributorsInvolved.html">As a Contributor</a><br>
+					<a href="getDevelopersInvolved.html">As a Developer</a><br>
+              </div>
+            </td>
+          </tr>
+        </table>
+      </td>
+    </tr>
+  </table>
+</body>
 </html>




More information about the Fdo-commits mailing list