svn commit: r28 - trunk/www
donaldcameron at osgeo.org
donaldcameron at osgeo.org
Fri Jul 14 15:11:30 EDT 2006
Author: donaldcameron
Date: 2006-07-14 19:11:30+0000
New Revision: 28
Added:
trunk/www/HOWTOWriteAProvider.html
trunk/www/OSFeatureMatrix.html
trunk/www/OSProviderOverviews.html
trunk/www/faq_licence.html
trunk/www/featureDescriptions.html
trunk/www/getContributorsInvolved.html
trunk/www/getDevelopersInvolved.html
trunk/www/getUsersInvolved.html
trunk/www/gettingStarted.html
trunk/www/glossary.html
trunk/www/history.html
trunk/www/licenceAndGovernance.html
trunk/www/roadMap.html
trunk/www/systemRequirements.html
Log:
FDO2
addition of new files for the July 21/06 website release
Added: trunk/www/HOWTOWriteAProvider.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/HOWTOWriteAProvider.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/HOWTOWriteAProvider.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,12 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - HOWTO: Write a Provider</title>
+</head>
+<body>
+<h1>FDO Open Source - HOWTO: Write a Provider</h1>
+<p>TBD</p>
+</body>
+</html>
Added: trunk/www/OSFeatureMatrix.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/OSFeatureMatrix.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/OSFeatureMatrix.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,269 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Feature Matrix</title>
+</head>
+<body>
+ <h1>FDO Open Source - Feature Matrix</h1>
+<p>
+The features are described on the <a href="featureDescriptions.html">feature description</a> page.
+</p>
+ <table border="1" rules="all">
+ <thead>
+ <tr>
+ <th>Feature</th>
+ <th>ArcSDE</th>
+ <th>MySQL</th>
+ <th>ODBC</th>
+ <th>SDF</th>
+ <th>SHP</th>
+ <th>WFS</th>
+ <th>WMS</th>
+ </tr>
+ </thead>
+ <tbody align="center">
+ <tr>
+ <td colspan="8"><strong>Commands</strong></td>
+ </tr>
+ <tr>
+ <td>Connection</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td><strong>o</strong></td> <!-- WFS -->
+ <td><strong>o</strong></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Datastore</td>
+ <td></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Describe Schema</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td><strong>o</strong></td> <!-- WFS -->
+ <td><strong>o</strong></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Apply Schema</td>
+ <td></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Spatial Context</td>
+ <td></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Select</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td><strong>o</strong></td> <!-- WFS -->
+ <td><strong>o</strong></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Select Aggregates</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Insert</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Update</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Delete</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>SQL Command</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Transactions</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Locking</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Long Transactions</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td colspan="8"><strong>Schema Capabilities</strong></td>
+ </tr>
+ <tr>
+ <td>Schema Overrides</td>
+ <td></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Foreign Schemas</td>
+ <td></td> <!-- ArcSDE -->
+ <td></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Associations</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Data Property Constraints</td>
+ <td></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Inheritance</td>
+ <td></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td><strong>o</strong></td> <!-- WFS -->
+ <td><strong>o</strong></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Object Properties</td>
+ <td></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td><strong>o</strong></td> <!-- WFS -->
+ <td></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td colspan="8"><strong>Setup and Tools</strong></td>
+ </tr>
+ <tr>
+ <td>Feature Schema Serialization</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td><strong>o</strong></td> <!-- WFS -->
+ <td><strong>o</strong></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>Feature Data Serialization</td>
+ <td><strong>o</strong></td> <!-- ArcSDE -->
+ <td><strong>o</strong></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td><strong>o</strong></td> <!-- SDF -->
+ <td><strong>o</strong></td> <!-- SHP -->
+ <td><strong>o</strong></td> <!-- WFS -->
+ <td><strong>o</strong></td> <!-- WMS -->
+ </tr>
+ <tr>
+ <td>XML Configuration</td>
+ <td></td> <!-- ArcSDE -->
+ <td></td> <!-- MySQL -->
+ <td><strong>o</strong></td> <!-- ODBC -->
+ <td></td> <!-- SDF -->
+ <td></td> <!-- SHP -->
+ <td></td> <!-- WFS -->
+ <td><strong>o</strong></td> <!-- WMS -->
+ </tr>
+ </tbody>
+ </table>
+</body>
+</html>
Added: trunk/www/OSProviderOverviews.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/OSProviderOverviews.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/OSProviderOverviews.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,49 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Provider Overviews</title>
+</head>
+<body>
+<h1>FDO Open Source - Provider Overviews</h1>
+<table border="1" rules="all">
+<thead>
+<tr>
+ <th>Provider</th>
+ <th>Description</th>
+</tr>
+</thead>
+<tbody>
+ <tr>
+ <td>OSGeo FDO Provider for ArcSDE</td>
+ <td>Read/write access to feature data in an ESRI ArcSDE-based data store (that is, with an underlying Oracle or SQL Server database). Supports describing schema, and inserting, selecting, updating, and deleting feature data in existing schemas; does not support creating or deleting schemas.</td>
+ </tr>
+ <tr>
+ <td>OSGeo FDO Provider for MySQL</td>
+ <td>Read/write access to feature data in a MySQL-based data store. Supports spatial data types and spatial query operations. Custom API can gather information, transmit exceptions, list data stores, and create connection objects. MySQL architecture supports various storage engines, characteristics, and capabilities.</td>
+ </tr>
+ <tr>
+ <td>OSGeo FDO Provider for SDF</td>
+ <td>Read-write access to feature data in an SDF-based data store. Autodesk’s geospatial file format, SDF, supports multiple features/attributes, provides high performance for large data sets, and interoperability with other Autodesk products. Supports spatial indexing and is a valid alternative to database storage. Note that this release of the SDF provider supports version 3.0 of the SDF file format.</td>
+ </tr>
+ <tr>
+ <td>OSGeo FDO Provider for SHP</td>
+ <td>Read/write access to existing spatial and attribute data in an ESRI SHP-based data store, which consists of separate shape files for geometry, index, and attributes. Each SHP file and its associated DBF file is treated as a feature class with a single geometry property. This is a valid alternative to database storage but does not support locking.</td>
+ </tr>
+ <tr>
+ <td>OSGeo FDO Provider for ODBC</td>
+ <td>Read/write to feature data in a ODBC-based data store. Supports XYZ feature objects and can define feature classes for any relational database table with X, Y, and optionally, Z columns; does not support creating or deleting schema. Object locations are stored in separate properties in the object definition.</td>
+ </tr>
+ <tr>
+ <td>OSGeo FDO Provider for WFS</td>
+ <td>Read-only access to feature data in an OGC WFS-based data store. Supports a client/server environment and retrieves geospatial data encoded in GML from one or more Web Feature Services sites. Client/server communication is encoded in XML with the exception of feature geometries, which are encoded in GML. Note that there is no public API documentation for this provider; all WFS functionality is accessible through the base ProductName API.</td>
+ </tr>
+ <tr>
+ <td>OSGeo FDO Provider for WMS</td>
+ <td>Read-only to feature data in an OGC WMS-based data store. Web Map Service (WMS) produces maps of spatially referenced data dynamically from geographic information, which are generally rendered in PNG, GIF, or JPEG, or as vector-based Scalable Vector Graphics (SVG) or Web Computer Graphics Metafile (WebCGM) formats</td>
+ </tr>
+</tbody>
+</table>
+</body>
+</html>
Added: trunk/www/faq_licence.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/faq_licence.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/faq_licence.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,134 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - Licensing FAQ</title>
+</head>
+
+<body>
+<h1>FDO Open Source - License FAQ</h1>
+<ol>
+ <li><a href="#1">What open source license covers FDO Open Source?</a> </li>
+ <li><a href="#2">Why are you using the LGPL?</a> </li>
+ <li><a href="#3">What does the LGPL allow me to do with FDO Open Source?</a>
+ </li>
+ <li><a href="#4">Can I use FDO Open Source to create my own proprietary
+ applications?</a> </li>
+ <li><a href="#5">How does the LGPL benefit me as a developer or end-user of
+ FDO Open Source?</a> </li>
+ <li><a href="#6">May I take a portion of the FDO Open Source code and use
+ it to extend and improve another application?</a> </li>
+ <li><a href="#7">What are the terms of using the third party software that is included within FDO Open Source?</a> </li>
+ <li><a href="#8">Do FDO Open Source users or developers need to pay a license fee because FDO Open Source uses Berkeley DB and XQuery?</a> </li>
+ <li><a href="#9">Autodesk contributed the original code for FDO Open Source.
+ Can Autodesk ever take it back?</a> </li>
+ <li><a href="#10">What if I want to contribute my code to the FDO Open Source
+ project?</a></li>
+</ol>
+<hr />
+<dl>
+ <dt><a name="1" id="1">1.</a> What open source license covers FDO Open
+ Source? </dt>
+ <dd>FDO Open Source is licensed under the <a href="lgpl.html">LGPL</a>
+ (GNU Lesser General Public License). This license complies with the open source
+ definition set forth by the <a href="http://www.opensource.org/">Open Source
+ Initiative</a> and is on the Open Source Initiative’s list of approved
+ open source licenses. </dd>
+ <dt><a name="2" id="2">2.</a> Why are you using the LGPL? </dt>
+ <dd>We have chosen the LGPL for a number of reasons, the most important of which
+ is that we believe the LGPL strikes the best balance between two important
+ yet often competing goals. The LGPL gives FDO Open Source users the assurance
+ that any modifications or enhancements to the source code will remain open
+ and freely available. At the same time, the LGPL allows commercial vendors
+ to build and distribute proprietary applications and systems using FDO
+ Open Source without any requirement that their commercial products also be
+ licensed as open source. We believe that offering an open yet “business-friendly”
+ license is necessary to promote the widespread adoption of FDO Open Source,
+ and this is precisely why we chose the LGPL. </dd>
+ <dt><a name="3" id="3">3.</a> What does the LGPL allow me to do with FDO
+ Open Source? </dt>
+ <dd>The LGPL allows you to use FDO Open Source software on a standalone
+ basis or as a component of your applications, provided that if you link your
+ proprietary software to FDO Open Source, you do so using dynamic linking.
+ You may make unlimited copies of FDO Open Source and distribute unlimited
+ copies of the software without payment of any royalties or license fees. And,
+ as with any open source license, you are free to make enhancements and modifications
+ to FDO Open Source. The LGPL does not require you to share the source
+ code of your enhancements unless you distribute changed versions of FDO
+ Open Source to third parties. However, if you distribute your changed versions
+ to others, you must make the changed source code available to parties to whom
+ you distribute your changed versions under the LGPL. </dd>
+ <dt><a name="4" id="4">4.</a> Can I use FDO Open Source to create my own
+ proprietary applications? </dt>
+ <dd>Yes. Unlike the GNU General Public License (GPL), the LGPL does not force
+ you to open source your application just because you integrate it with code
+ from FDO Open Source. If your application merely links dynamically to
+ FDO Open Source software at runtime, and does not include a changed version
+ of FDO Open Source, you have created what the license refers to as a
+ “work that uses the library” and you need only comply with the
+ requirements in Section 6 of the LGPL. Broadly speaking, this section requires
+ you simply to give notice that your application contains LGPL code and pass
+ along a copy of the license and a copyright notice for FDO Open Source.
+ </dd>
+ <dd>Only if you modify the FDO Open Source software itself have you created
+ what the LGPL refers to as a “work based on the library”, in which
+ case your application would have to be licensed as open source under the LGPL.
+ The bottom line is that you never have to disclose proprietary source code
+ that links to FDO Open Source if you don’t want to. </dd>
+ <dt><a name="5" id="5">5.</a> How does the LGPL benefit me as a developer or
+ end-user of FDO Open Source? </dt>
+ <dd>Apart from the clear advantages of making available free and open source
+ code for development and maintenance purposes, the LGPL gives FDO Open
+ Source users the assurance that any modifications or enhancements to the source
+ code will also remain open and freely available. Under the LGPL, anyone that
+ makes enhancements to the FDO Open Source source code is required to
+ reciprocate by making those changes available when the code is redistributed.
+ Some open source licenses such as the MIT or BSD licenses do not contain this
+ reciprocity obligation. The result is that although the software initially
+ distributed under those licenses is open source, modified versions of that
+ software are not required to be open source. Companies can take this software
+ and create closed proprietary versions, or create “forks”, which
+ can result in incompatible versions of FDO Open Source being distributed
+ by different vendors. </dd>
+ <dd>The LGPL makes it far less likely that FDO Open Source will be forked
+ into incompatible versions, because no one can prevent changes from being
+ distributed freely within the community. The LGPL thus helps to promote a
+ single worldwide standard for FDO Open Source that is available to everyone
+ for free. </dd>
+ <dt><a name="6" id="6">6.</a> May I take a portion of the FDO Open Source
+ code and use it to extend and improve another application? </dt>
+ <dd>Yes. You may freely modify, extend, and improve the FDO Open Source
+ source code, either for use with FDO Open Source itself or in connection
+ with another software application, as long as your extensions integrate with
+ FDO Open Source through dynamic linking. Of course, if you distribute
+ the modifications you must comply with the LGPL’s requirement that the
+ changed source code be made freely available. </dd>
+ <dt><a name="7" id="7">7.</a> What are the terms of using the third party software
+ that is included within FDO Open Source? </dt>
+ <dd>FDO Open Source relies on a number of third party modules that are included in the source code distribution. Many of these modules are made available under either the LGPL or under permissive, non-reciprocal open source licenses such as the MIT, BSD or Apache licenses. The exception to this is the Berkeley DB XML database and XQuery query engine, which are used by FDO Open Source for data storage and querying and which are described in more detail below. We have no legal authority over third party modules used in FDO Open Source. You should carefully read the license requirements for each of these modules and contact the respective authors for any clarification on allowed uses and requirements. For a complete listing and associated license requirements of the third party software included in the FDO Open Source distribution, see the “license.htm” file included in the source code.</a>
+ </dd>
+
+ <dt><a name="8" id="8">8.</a>Do FDO Open Source users or developers need to pay a license fee because FDO Open Source uses Berkeley DB and XQuery?</dt>
+ <dd>No. These software products are both included in the FDO Open Source distribution, but they are licensed under the Sleepycat Public License. This is a free software license which permits you to use the software at no cost. The Sleepycat license does, however, impose certain terms on licensees who distribute applications that use Berkeley DB XML and/or XQuery. One of these terms is a requirement that the source code of your application that uses Berkeley DB XML and/or XQuery be included in the distribution, and that the source code be "freely redistributable under reasonable conditions." Thus, so long as you make the source code of your application available under an open source license, there is no need to purchase a commercial license to the software. And if you do not distribute your FDO Open Source-based application to third parties but instead only deploy it internally, this requirement does not apply to you. The Sleepycat Public License is described in more detail at <a href="http://www.sleepycat.com/company/licensing.html">http://www.sleepycat.com/company/licensing.html</a>.
+ </dd>
+
+ <dt><a name="9" id="9">9.</a> Autodesk contributed the original code for FDO
+ Open Source. Can Autodesk ever take it back? </dt>
+ <dd>No. Once code is released under the LGPL, it cannot be withdrawn. Autodesk
+ is firmly committed to the FDO Open Source project and has no plans to
+ return to a closed development model for this product. Like other developers
+ working on the FDO Open Source project, Autodesk expects to contribute
+ further enhancements to the code base that will be licensed under the LGPL.
+ </dd>
+
+ <dt><a name="10" id="10">10.</a> What if I want to contribute my code to the FDO
+ Open Source project? </dt>
+ <dd>The governance model currently being formulated by the Open Source Geospatial Foundation
+ members will define how code will be added to Foundation software projects,
+ and what contributor agreement will be required. The Foundation will emulate
+ other successful open source projects utilizing an active meritocracy model.
+ </dd>
+</dl>
+</body>
+</html>
+
Added: trunk/www/featureDescriptions.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/featureDescriptions.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/featureDescriptions.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,137 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Feature Descriptions</title>
+</head>
+<body>
+ <h1>FDO Open Source - Feature Descriptions</h1>
+ <p>This page describes the features referenced in the feature matrix pages.</p>
+<table border="1" rules="all">
+<thead>
+<tr>
+ <th>Feature</th>
+ <th>Description</th>
+</tr>
+</thead>
+<tbody>
+ <tr>
+ <td colspan="2"><strong>Commands</strong></td>
+ </tr>
+ <tr>
+ <td>Connection</td>
+ <td>Connect to a data store.</td>
+ </tr>
+ <tr>
+ <td>Capabilities</td>
+ <td>Obtain information programmatically about the features that a provider supports and does not support.</td>
+ </tr>
+ <tr>
+ <td>Datastore</td>
+ <td>Create, destroy, and list data stores.</td>
+ </tr>
+ <tr>
+ <td>Describe Schema</td>
+ <td>Get a feature schema from a data store.</td>
+ </tr>
+ <tr>
+ <td>Apply Schema</td>
+ <td>Create a feature schema in a data store.</td>
+ </tr>
+ <tr>
+ <td>Spatial Context</td>
+ <td>Manage the properties required for the storage and manipulation of geometric data.</td>
+ </tr>
+ <tr>
+ <td>Select</td>
+ <td>Use the FDO filter and expression language to select a set of features from a data store.</td>
+ </tr>
+ <tr>
+ <td>Select Aggregates</td>
+ <td>Selects groups of features from the data store and applies filters to each of the groups.</td>
+ </tr>
+ <tr>
+ <td>Insert</td>
+ <td>Create an instantiation of a feature schema class and add it to the data store.</td>
+ </tr>
+ <tr>
+ <td>Update</td>
+ <td>Modify a feature in the data store.</td>
+ </tr>
+ <tr>
+ <td>Delete</td>
+ <td>Delete a feature from the data store.</td>
+ </tr>
+ <tr>
+ <td>SQL Command</td>
+ <td>Supports the execution of a SQL statement against an underlying RDBMS. Two execute methods are provided to distinguish between statements that return table data versus those that execute non query type operations. </td>
+ </tr>
+ <tr>
+ <td>Transactions</td>
+ <td>Supports transaction processing (begin, commit, rollback).</td>
+ </tr>
+ <tr>
+ <td>Locking</td>
+ <td>Persistent and transaction locks are supported. A persistent lock is applied, if a user requires exclusive access to an object for an extended period of time (for example, for multiple sessions). In contrast, a transaction lock is applied if exclusive access to an object is required for the duration of a transaction only. Such a transaction could cover the time required to change an object.</td>
+ </tr>
+ <tr>
+ <td>Long Transactions</td>
+ <td>Group conditional changes to one or more objects. A root long transaction represents permanent data. A descendent of a root long transaction represents revisions to objects where the revisions do not involve permanent changes to those objects.</td>
+ </tr>
+ <tr>
+ <td colspan="2"><strong>Schema Capabilities</strong></td>
+ </tr>
+ <tr>
+ <td>Schema Overrides</td>
+ <td>This allows FDO applications to customize the mappings between Feature (logical) Schemas and the Physical Schema of the Provider DataStore. Schema Mappings will be customized through Schema Override sets. Each Feature Schema may have a number of associated sets, one per FDO Provider that the Feature Schema might be applied against.</td>
+ </tr>
+ <tr>
+ <td>Foreign Schemas</td>
+ <td>Access data stored in schemas created by third-party applications. </td>
+ </tr>
+ <tr>
+ <td>Associations</td>
+ <td>Describes a relationship between classes. The association has properties that describe the linkage between the classes being associated. The linkage can be one-to-one or many-to-many.</td>
+ </tr>
+ <tr>
+ <td>Data Property Constraints</td>
+ <td>Specify that a property or list of properties taken together have unique values for all objects of that class in a datastore. A unique constraint that is based on a list of two or more properties is called a composite unique constraint. This constraint type applies to all data property types except for Boolean, BLOB, and CLOB. A Boolean property can be included if it is part of a composite unique constraint.</td>
+ </tr>
+ <tr>
+ <td>Inheritance</td>
+ <td>Supports feature class hierarchies.</td>
+ </tr>
+ <tr>
+ <td>Object Properties</td>
+ <td>Supports class properties whose type is a class.</td>
+ </tr>
+ <tr>
+ <td colspan="2"><strong>Setup and Tools</strong></td>
+ </tr>
+ <tr>
+ <td>Feature Schema Serialization</td>
+ <td>Read and write Feature Schema, Schema Overrides and Spatial Context information using an OGC GML format.</td>
+ </tr>
+ <tr>
+ <td>Feature Data Serialization</td>
+ <td>Read and write feature data using an OGC GML format.</td>
+ </tr>
+ <tr>
+ <td>XML Configuration</td>
+ <td>Supports provider-specific configuration. For the Raster provider, the parameters are logical schema, schema overrides, and spatial context. For the WMS provider, the only parameter is logical schema. For the ODBC provider, the parameters are</td>
+ </tr>
+ <!--
+ <tr>
+ <td>User Admin Tool</td>
+ <td>Add, drop, grant privileges to, and remove privileges from, a user.</td>
+ </tr>
+ <tr>
+ <td>Bulk Copy</td>
+ <td>Used to copy data from one FDO data store to another FDO data store.</td>
+ </tr>
+ -->
+</tbody>
+</table>
+</body>
+</html>
Added: trunk/www/getContributorsInvolved.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/getContributorsInvolved.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/getContributorsInvolved.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,12 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Get Contributors Involved</title>
+</head>
+<body>
+<h1>FDO Open Source - Get Contributors Involved</h1>
+<p>TBD</p>
+</body>
+</html>
Added: trunk/www/getDevelopersInvolved.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/getDevelopersInvolved.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/getDevelopersInvolved.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,12 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Get Developers Involved</title>
+</head>
+<body>
+ <h1>FDO Open Source - Get Developers Involved</h1>
+<p>TBD</p>
+</body>
+</html>
Added: trunk/www/getUsersInvolved.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/getUsersInvolved.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/getUsersInvolved.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,12 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Get Users Involved</title>
+</head>
+<body>
+<h1>FDO Open Source - Get Users Involved</h1>
+<p>TBD</p>
+</body>
+</html>
Added: trunk/www/gettingStarted.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/gettingStarted.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/gettingStarted.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,260 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Getting Started</title>
+</head>
+<body>
+<h1>FDO Open Source - Getting Started</h1>
+<h2>Get the Source and Build the Binaries</h2>
+<p>This is described in the build <a href="documentation.html">documentation</a>.</p>
+<p>The FDO installation path on Linux is fixed. It is /usr/local/fdo-<version>.</p>
+<p>The FDO installation path on Windows is configurable using a command-line argument to the build script.</p>
+<h2>Setup the Application Development Environment</h2>
+ <p>
+ Check out the settings in the solution (.sln) and project (.vcproj) files
+ found in the FDO source folders on Windows and in the
+ makefile.am and configure.in files found in the FDO source directories
+ on Linux.
+ <h3>Windows</h3>
+ <p>The assumption is that you are using Visual Studio 2005.</p>
+ <p>
+ Use the installation path to set up the environment so that headers
+ and libraries can be located at compile time,
+ and shared objects can be located at runtime.
+ </p>
+ <p>
+ Use the build path to set up the environment so that the debugger can locate
+ program database files (symbol tables) and source files at runtime.
+ <p>
+ You can make the various files visible by either setting solution or
+ project properties or by setting Visual Studio tool options or by
+ setting an environment variable (PATH).
+ </p>
+ <p>
+ The first step for the properties method is to select the solution
+ or project in the Solution Explorer, right-click to its pop-up menu
+ and select Properties. The result is that the properties dialog is
+ displayed. If the project properties dialog is displayed,
+ the second step is to expand 'Configuration Properties' in the
+ properties dialog contents pane.
+ </p>
+ <p>
+ The first step for the tool options method is to select 'Options...'
+ from the Tools menu in the main menubar.
+ The result is that the options dialog is displayed.
+ </p>
+ <h4>Headers</h4>
+ <p>
+ In the project properties dialog contents pane expand 'Configuration Properties'
+ and then 'C/C++'. Select 'General' and edit 'Additional Include
+ Directories'.
+ </p>
+ <p>
+ In the options dialog contents pane expand 'Projects and Solutions' and
+ then 'VC++ Directories'. Select 'Include files' from the spinbox labeled
+ 'Show directories for:'. Follow the procedure for adding a directory.
+ </p>
+ <h4>Libraries</h4>
+ <p>
+ In the project properties dialog contents pane expand 'Configuration Properties'
+ and then 'Linker'. Select 'General' and edit 'Additional Library
+ Directories'.
+ </p>
+ <p>
+ In the options dialog contents pane expand 'Projects and Solutions' and
+ then 'VC++ Directories'. Select 'Library files' from the spinbox labeled
+ 'Show directories for:'. Follow the procedure for adding a directory.
+ </p>
+ <h4>Dynamically Linked Libraries</h4>
+ <p>
+ In the options dialog contents pane expand 'Projects and Solutions' and
+ then 'VC++ Directories'. Select 'Executables' from the spinbox labeled
+ 'Show directories for:'. Follow the procedure for adding a directory.
+ </p>
+ <p>
+ Use XP to set the PATH environment variable.
+ </p>
+ <h4>Source Files</h4>
+ <p>
+ In the solution properties dialog contents pane expand
+ 'Common Properties'.
+ Select 'Debug Source Files'. Follow the procedure for adding a directory.
+ </p>
+ <p>
+ In the options dialog contents pane expand 'Projects and Solutions' and
+ then 'VC++ Directories'. Select 'Source files' from the spinbox labeled
+ 'Show directories for:'. Follow the procedure for adding a directory.
+ </p>
+ <h4>Symbol Table Files (Program Database Files)</h4>
+ <p>
+ In the options dialog contents pane expand 'Debugging' and
+ then 'Symbols'. Follow the procedure for adding a directory.
+ </p>
+ <h3>Linux</h3>
+ <p>Set LD_LIBRARY_PATH.</p>
+<h2>Access the API Reference Documentation</h2>
+<p>
+ The API reference documentation has been created by using doxygen to
+ process comments in the header files. When doxygen generates the html
+ files, it distributes them across a generated file structure to allow
+ for quicker access. This prevents direct linking to the class html files.
+</p>
+<p>
+ When you are asked to read FDO class reference documentation, load the
+ <a href="docs/FDO_API/index.html">FDO C++ API Reference Home Page</a>,
+ click the Classes tab in the right-hand pane and click on the class name.
+</p>
+<h2>Write the Code to Connect to a Provider</h2>
+<p>Do the following:</p>
+<ol>
+ <li></li>
+ <li>Get the list of installed providers</li>
+ <li>Create a connection manager</li>
+ <li>Create a connection</li>
+ <li>Get the connection state</li>
+ <li>Get the connection properties</li>
+ <li>Get values for the connection properties</li>
+ <li>Set the connection properties</li>
+ <li>Open a connection<li>
+ <li>Open a pending connection</li>
+</ol>
+<h3>Create a Provider Registry</h3>
+ <p>
+ The provider registry tells you what providers are installed.
+ </p>
+ <p>
+ Read about the GetProviderRegistry method in the
+ <strong>FdoFeatureAccessManager</strong> class reference.
+ </p>
+<h3>Get the List of Installed Providers</h3>
+ <p>
+ Read about the GetProviders method in the
+ <strong>FdoProviderRegistry</strong> class reference.
+ This method returns the contents of the providers.xml file found in the
+ <install>/bin folder on Windows and
+ in the /usr/local/fdo-<version>/lib directory on Linux.
+ </p>
+ <p>
+ When you create the connection, you will use one of the strings returned
+ by this method as an argument.
+ </p>
+<h3>Create a Connection Manager</h3>
+ <p>
+ The connection manager creates connections.
+ </p>
+ <p>
+ Read about the GetConnectionManager method in the
+ <strong>FdoFeatureAccessManager</strong> class reference.
+ </p>
+<h3>Create a Connection</h3>
+ <p>
+ Read about the CreateConnection method in the
+ <strong>FdoConnectionManager</strong> class reference.
+ </p>
+<h3>Get the Connection State</h3>
+ <p>
+ At this point the state of the connection is closed.
+ </p>
+ <p>
+ Read about the GetConnectionState method in the
+ <strong>FdoIConnection</strong> class reference.
+ </p>
+<h3>Get the Connection Properties</h3>
+ <p>
+ First you get the connection information. Read about the
+ GetConnectionInfo method in the <strong>FdoIConnection</strong>
+ class reference.
+ </p>
+ <p>
+ Then you get the connection properties. Read about the
+ GetConnectionProperties method in the <strong>FdoIConnectionInfo</strong>
+ class reference.
+ This method returns a connection property dictionary.
+ </p>
+ <p>
+ Read about the methods used to access the information in the connection
+ properties dictionary in the <strong>FdoIPropertyDictionary</strong>
+ class reference.
+ Using these methods you can find out the names of the properties,
+ whether they are optional or mandatory, whether they have default values,
+ their type, whether they are enumerable and, if enumerable, what the set
+ of enumerated values is.
+ </p>
+<h3>Get Values for the Connection Properties</h3>
+ <p>
+ The types of properties used in connections include:
+ </p>
+ <ul>
+ <li>user names</li>
+ <li>passwords</li>
+ <li>file path names</li>
+ <li>URLs</li>
+ <li>symbolic host names</li>
+ <li>service identifiers</li>
+ <li>data store names</li>
+ </ul>
+ <p>
+ Each provider has its own unique set of connection properties.
+ The connection properties for the various providers
+ are described in
+ <a href="docs/FET_TheEssentialFDO.pdf">The Essential FDO (PDF)</a>.
+ </p>
+<h3>Set the Connection Properties</h3>
+ <p>
+ Read about the methods used to access the information in the connection
+ properties dictionary in the <strong>FdoIPropertyDictionary</strong>
+ class reference.
+ </p>
+<h3>Open a Connection</h3>
+ <p>
+ Read about the Open method in the <strong>FdoIConnection</strong> class
+ reference.
+ </p>
+<h3>Open a Pending Connection</h3>
+ <p>
+ Each of the RDBMS-based providers has a connection property, which is there
+ to contain the name of a data store. The data store property is initially
+ not required in order to make a connection. If the property is not set,
+ then the resulting connection, if successful, is in a pending state.
+ </p>
+ <p>
+ As a result of the initial connection operation, the data store property is
+ populated with the names of the data stores in the RDBMS, and its optionality
+ attribute is changed to a value of required.
+ </p>
+ <p>
+ Use the EnumeratePropertyValues method on the
+ <strong>FdoIPropertyDictionary</strong> object
+ to read the set of data store names and set the data store property
+ in the dictionary object to one of those names.
+ Then call the Open method on the <strong>FdoIConnection</strong> object
+ again. This will result in a fully open connection.
+ </p>
+ <p>
+ You can connect to an ArcSDE provider using a pending connection, you will
+ find that there is only ever one name in the set of data store names
+ returned as a result of the initial connection.
+ </p>
+<h2>Next Steps</h2>
+<h3>ArcSDE Provider</h3>
+<p>
+You use this provider to connect to an ArcSDE server, which is, in turn,
+connected to an Oracle or SQL Server data source.
+</p>
+<p>The next step is to determine the number and composition of feature schema
+in the data store so that you can execute data maintenance (insert, update,
+and delete) and query (select) commands.</p>
+<h3>MySQL Provider</h3>
+<p>The next steps are to create a data store and a user, and after that,
+create a feature schema and execute data maintenance and query commands.
+</p>
+<h3>SDF, SHP and ODBC Providers</h3>
+<p>The next steps are to create a feature schema and execute data
+maintenance and query commands.
+<h3>WFS and WMS Providers</h3>
+<p>The next steps are to determine the composition of the feature schema and
+execute query commands.</p>
+</body>
+</html>
Added: trunk/www/glossary.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/glossary.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/glossary.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,51 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Glossary</title>
+</head>
+<body>
+<h1>FDO Open Source - Glossary</h1>
+<dl>
+ <dt>Feature Schema</dt>
+ <dd>
+ A set of classes and their corresponding properties and relationships.
+ Each Feature Schema typically contains the classes for a specific domain,
+ for example, Electrical Schema, Gas Schema, etc..
+ The Feature Schema defines its classes in an FDO provider-independent form.
+ </dd>
+ <dt>GML</dt
+ <dd>OGC’s Geography Markup Language. An XML format for geographic data.</dd>
+ <dt>Schema</dt>
+ <dd>
+ In RDBMS terms, a Schema is a collection of tables, indexes, views, etc.
+ in a database. Feature and RDBMS schemas do not correspond 1:1.
+ A Feature Schema may be stored in different RDBMS schemas
+ and an RDBMS schema might be composed of multiple logical schemas.
+ </dd>
+ <dt>OGC</dt>
+ <dd>Open Gis Consortium</dd>
+ <dt>Schema Mapping</dt>
+ <dd>
+ A set of hints that determine how Feature Schemas are stored
+ in an FDO data store.
+ The contents of Schema Mappings vary depending on the FDO Provider type.
+ </dd>
+ <dt>Tolerance</dt>
+ <dd>
+ Used to determine when two points are close enough to be considered to be
+ equivalent in certain spatial tests. In FDOL, the tolerance value is used
+ as a radius around a position rather than as a distance along an axis.
+ In the majority of cases, the distance between the points is compared
+ to the tolerance using the 'less than' predicate. If the X and Y tolerances
+ are both 0.05, the point B (1.0, 1.0) is considered to be equivalent to
+ point A (0.96, 0.96) and point C (1.04, 1.04), but is not considered to be
+ equivalent to point D (0.96, 0.94) or point E (1.04, 1.06). The
+ relationship is not transitive. That is, point A is not equivalent to
+ point C. Repeated applications of the <strong>isEquivalentTo</strong>
+ predicate to the same data always yields the same result.
+ </dd>
+</dl>
+</body>
+</html>
Added: trunk/www/history.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/history.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/history.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,85 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - History</title>
+</head>
+<body>
+<h1>FDO Open Source - History</h1>
+<h2>Origins</h2>
+<p>
+ Autodesk needed a technology that could provide a way to access
+ many different geospatial data sources through a common mechanism.
+ The data sources included a variety of geospatial databases and file
+ formats. It had to be flexible to meet the needs of many client
+ applications.
+</p>
+<p>
+ The initial requirements included the following
+</p>
+<ul>
+ <li>
+ Provides an object based feature model of geospatial data
+ that is generic and independent of any particular native implementation.
+ <li>
+ <li>
+ Supports, as a minimum, the OGC Simple Feature specification geometry types.
+ </li>
+ <li>
+ Defines a logical model that maps to commonly used physical implementations
+ such as Oracle Spatial and SHP files.
+ </li>
+ <li>
+ Defines an FDO Provider as an implementation of the FDO API for a
+ particular data source.
+ Each data source has its corresponding FDO provider.
+ </li>
+ <li>
+ Defines a capabilities API to allow clients to determine specific
+ capabilities of a particular provider and thus respond correctly no what
+ provider they are connected to.
+ </li>
+ <li>
+ Allows new commands and schema additions to be easily added over time to
+ the generic APPI and allows custom commands to be added to a particular
+ provider. The capabilities API allows a client to discover the custom commands.
+ </li>
+</ul>
+<h2>Before Open Source</h2>
+<p>
+ The first version of FDO was shipped with the Autodesk Map 2005 product
+ in the spring of 2004. It included providers for Oracle and SDF.
+ Version 2.0 added the ArcSDE provider, and
+ version 3.0 added providers for MySQL, SQL Server, ODBC, SHP, Raster,
+ OGC WFS, and OGC WMS.
+</p>
+<p>
+ See the <a href="productsUsingFdo.html">Products Using FDO</a> page for the
+ full list of FDO releases.
+</p>
+<h2>FDO Goes Open Source</h2>
+<p>
+ The release of FDO as open source coincided with the release of
+ <a href="http://mapguide.osgeo.org/about.html#history">MapGuide</a> as open source in 2006.
+ It included the SDF, SHP, MySQL, ArcSDE, ODBC, OGC WFS,
+ and OGC WMS providers.
+</p>
+<p>
+Here is an excerpt from the <a href="http://images.autodesk.com/adsk/files/MapGuide_Open_Source_FAQ(2).pdf">MapGuide Open Source FAQ</a> on the question of why Autodesk made MapGuide Open Source. The same reasons apply in the case of FDO.</p>
+<p>
+"Our developers and customers have been demanding:</p>
+<ul>
+ <li>Faster innovation of our web mapping solutions</li>
+ <li>More frequent software releases</li>
+ <li>Lower cost of entry and ownership</li>
+</ul>
+<p>
+ Autodesk wants to help make map serving technologies more readily
+ available for widespread adoption.
+ Our conclusion was that joining and supporting the existing open
+ geospatial community and open sourcing our next-generation
+ web mapping platform was the best approach."
+</p>
+</body>
+</html>
Added: trunk/www/licenceAndGovernance.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/licenceAndGovernance.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/licenceAndGovernance.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,22 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Licence and Governance</title>
+</head>
+<body>
+<h1>FDO Open Source- Licence and Governance</h1>
+<h2>Licence</h2>
+<p>FDO is licensed under the <a href="lgpl.html">LGPL</a> (GNU Lesser General Public License). Our <a href="faq_licence.html">License FAQ</a> provides more information on our license and on our policies regarding the application of the license</p>
+<h2>Governance</h2>
+<p>FDO Open Source is part of the Open Source Geospatial Foundation and as such follows the governance structure of the foundation.</p>
+<h3>Organization and Roles</h3>
+<ul>
+ <li>Project Steering Committee - The Project Steering Committee (PSC) is responsible for the overall management of the FDO Open Source project. The PSC determines when releases will be made available, what enhancements and defects will go into a particular release, and who the Project Developers are. The PSC is also responsible for providing the Open Source Geospatial Foundation board with regular status reports.</li>
+ <li>Project Developers - A Project Developer has full commit access to the trunk of the source tree. Project Developers can directly make changes to the source base of the development branch, from which the nightly builds are made. Project Developers review and accept code submitted by Project Contributors.</li>
+ <li>Project Contributors - A Project Contributor is a developer who contributes patches, code, and/or documentation through the Project Tracker tool. Project Contributors do not have Subversion check-in access. Integration of a developers' contributions is at the discretion of the Project Owner and individuals in the Project Developer role. This is typically an iterative, communicative process.</li>
+ <li>Users - Users are the project’s reason for being. They are the individuals that use and develop applications on the FDO Open Source platform.</li>
+</ul>
+</body>
+</html>
Added: trunk/www/roadMap.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/roadMap.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/roadMap.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,12 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - Road Map</title>
+</head>
+<body>
+<h1>FDO Open Source - Road Map</h1>
+<p>TBD</p>
+</body>
+</html>
Added: trunk/www/systemRequirements.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/systemRequirements.html?view=auto&rev=28
==============================================================================
--- (empty file)
+++ trunk/www/systemRequirements.html 2006-07-14 19:11:30+0000
@@ -0,0 +1,117 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link href="styles/projectcontent.css" rel="stylesheet" type="text/css">
+ <title>FDO Open Source - System Requirements</title>
+</head>
+<body>
+<h1>FDO Open Source- System Requirements</h1>
+<p>This page lists the software packages required to get, build, and operate FDO on Windows XP and on Linux x86.
+</p>
+<h2>Packages</h2>
+<table border="1" rules="all">
+ <thead>
+ <tr>
+ <th>Package</th>
+ <th>OS</th>
+ <th>Requirement</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>bison 1.875/sed 4.1.4</td>
+ <td>both</td>
+ <td>Regenerate filter and expression parser if grammar changes</td>
+ </tr>
+ <tr>
+ <td>doxygen 1.4.6/graphviz 2.8</td>
+ <td>both</td>
+ <td>Generate API reference documentation, if desired</td>
+ </tr>
+ <tr>
+ <td>HTML Help 1.4 SDK</td>
+ <td>XP</td>
+ <td>Generate API reference documentation in .chm format, if desired</td>
+ </tr>
+ <tr>
+ <td>.NET Framework version 2.0</td>
+ <td>XP</td>
+ <td>Build</td>
+ </tr>
+ <tr>
+ <td>Visual Studio 2005</td>
+ <td>XP</td>
+ <td>Build</td>
+ </tr>
+ <tr>
+ <td>autoconf, automake, make</td>
+ <td>Linux</td>
+ <td>Build</td>
+ </tr>
+ <tr>
+ <td>Subversion</td>
+ <td>Both</td>
+ <td>Update source</td>
+ </tr>
+ <tr>
+ <td>ArcSDE 9.1 client</td>
+ <td>Both</td>
+ <td>ArcSDE provider</td>
+ </tr>
+ <tr>
+ <td>MySQL 5.0</td>
+ <td>Both</td>
+ <td>MySQL provider</td>
+ </tr>
+ </tbody>
+ </table>
+<h2>Disk Space</h2>
+<table border="1" rules="all">
+ <thead>
+ <tr>
+ <th>Software Category</th>
+ <th>Windows (MB)</th>
+ <th>Linux (MB)</th>
+ <tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Repository client</td>
+ <td>16</td>
+ <td>6</td>
+ </tr>
+ <tr>
+ <td>Build tools</td>
+ <td>1842</td>
+ <td>12</td>
+ </tr>
+ <tr>
+ <td>RDBMS clients</td>
+ <td>113</td>
+ <td>115</td>
+ </tr>
+ <tr>
+ <td>FDO source pre-build</td>
+ <td>928</td>
+ <td>928</td>
+ </tr>
+ <tr>
+ <td>FDO post-build (release and debug)</td>
+ <td>5649</td>
+ <td>1755</td>
+ </tr>
+ <tr>
+ <td>FDO install release version</td>
+ <td>178</td>
+ <td>173</td>
+ </tr>
+ <tr>
+ <td>FDO install debug version</td>
+ <td>193</td>
+ <td>241</td>
+ </tr>
+ </tbody>
+ </table>
+</body>
+</html>
More information about the Fdo-commits
mailing list