| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
| <HTML> |
| <HEAD> |
| <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=shift_jis"> |
| <TITLE>Eclipse Data Tools Project</TITLE> |
| <META NAME="GENERATOR" CONTENT="Microsoft FrontPage 4.0"> |
| <META NAME="CREATED" CONTENT="20050606;16532063"> |
| <META NAME="CHANGEDBY" CONTENT="John Graham"> |
| <META NAME="CHANGED" CONTENT="20050606;17530555"> |
| <STYLE> |
| <!-- |
| TD P { margin-left: 0.12in; color: #000000; font-family: "arial", "helvetica", "geneva"; font-size: 10pt } |
| P { margin-left: 0.12in; color: #000000; font-family: "arial", "helvetica", "geneva"; font-size: 10pt } |
| H3 { color: #000000 } |
| H3.cjk { font-family: "Times New Roman" } |
| A:link { color: #0000ee } |
| A:visited { color: #551a8b } |
| --> |
| </STYLE> |
| </HEAD> |
| <BODY LANG="en-US" TEXT="#000000" LINK="#0000ee" VLINK="#551a8b" BACKGROUND="DTP_Proposal/proposal.gif" DIR="LTR"> |
| <P STYLE="margin-bottom: 0in"><BR> |
| </P> |
| <TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=5> |
| <TR> |
| <TD WIDTH=60%> |
| <P ALIGN=LEFT><B><FONT SIZE=6><FONT FACE="Verdana, Arial, Helvetica, sans-serif">Data |
| Tools Platform</FONT></FONT></B><BR><FONT SIZE=1><FONT FACE="Arial, Helvetica, sans-serif"><FONT COLOR="#8080ff">Project |
| Charter</FONT></FONT></FONT></P> |
| </TD> |
| <TD WIDTH=40%> |
| <P><IMG SRC="DTP_Charter/Idea.jpg" NAME="Graphic1" ALIGN=MIDDLE HSPACE=50 WIDTH=120 HEIGHT=86 BORDER=0></P> |
| </TD> |
| </TR> |
| </TABLE> |
| <TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0> |
| <COL WIDTH=252*> |
| <COL WIDTH=4*> |
| <TR> |
| <TD COLSPAN=2 WIDTH=100% VALIGN=TOP BGCOLOR="#0080c0"> |
| <P ALIGN=LEFT><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><B>The |
| Eclipse Data Tools Platform Project – Top Level Project |
| Charter – The Eclipse Foundation</B></FONT></FONT></P> |
| </TD> |
| </TR> |
| <TR> |
| <TD WIDTH=99%> |
| <P STYLE="margin-left: 0in"><B>Overview<BR><BR></B>“Data |
| Tools” is a vast domain, yet there are a fairly small number |
| of foundational requirements when developing with or managing |
| data-centric systems. A developer is interested in an environment |
| that is easy to configure -- one in which the challenges of |
| application development are due to the problem domain, not the |
| complexity of the tools employed. Data management, whether by a |
| developer working on an application, or an administrator |
| maintaining or monitoring a production system, should also provide |
| a consistent, highly usable environment that works well with |
| associated technologies.</P> |
| <P STYLE="margin-left: 0in"><FONT SIZE=2><FONT FACE="arial, helvetica, geneva, sans-serif">Such |
| an environment starts with key frameworks designed both for use |
| and extensibility. Examples include location and management of |
| data source drivers, and configurations for access to particular |
| data source instances. Once a connection is successfully made, the |
| next task often is to explore the data source, making changes as |
| required. Some of these operations might be carried out by GUI |
| actions, others directly through commands. For example, users – |
| both developers and administrators – typically will create, |
| edit, and test SQL for these commands. Assistance in editing SQL |
| through code completion, formatting, and dialect specialization, |
| greatly enhances productivity. Further, the ability to execute or |
| debug commands, both SQL and stored procedures, rounds out the |
| rapid development process that Eclipse supports so well. Finally, |
| bridging chasms, whether between relational, object, or other |
| structures, presents challenges that data management tooling |
| should address.</FONT> </FONT> |
| </P> |
| <P STYLE="margin-left: 0in"><B>Mission<BR><BR></B><FONT FACE="arial, helvetica, geneva, sans-serif">The |
| Data Tools Platform (DTP) project will include extensible |
| frameworks and exemplary tools, enabling a diverse set of plug-in |
| offerings specific to particular data-centric technologies and |
| supported by the DTP ecosystem. In the spirit of Eclipse, the |
| project will be guided by the following values:</FONT></P> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><I>Vendor |
| neutrality: </I>We intend to provide data management frameworks |
| and tools not biased toward any vendor. Our intention is that DTP |
| be leveraged to provide the Eclipse community with the widest |
| range of choices possible. To this end, we seek community |
| involvement in formulating key framework interfaces, so that the |
| largest possible constituency is represented.</FONT></P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><I>Extensibility:</I> |
| We recognize both the common need for data tooling infrastructure |
| and the desire to extend the offerings in new and innovative |
| ways. To support these efforts, our components will be designed |
| for, and make good use of, extensibility mechanisms supported by |
| Eclipse. </FONT> |
| </P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><I>Community |
| Involvement: </I>Success for DTP, as with other eclipse.org |
| projects, is as much a factor of community involvement as the |
| technical merit of its components. We strongly believe that DTP |
| will achieve its full potential only as the result of deep and |
| broad cooperation with the Eclipse membership-at-large. Thus, we |
| will make every effort to accommodate collaboration, reach |
| acceptable compromises, and provide a project management |
| infrastructure that includes all contributors, regardless of |
| their affiliation, location, interests, or level of involvement. |
| Regular meetings covering all aspects of DTP, open communication |
| channels, and equal access to process will be key areas in |
| driving successful community involvement.</FONT></P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><I>Transparency: |
| </I>As with all projects under the eclipse.org banner, key |
| information and discussions at every level – such as |
| requirements, design, implementation, and testing – will be |
| easily accessible to the Eclipse membership-at-large. </FONT> |
| </P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><I>Agile |
| development </I>We will strive to incorporate into our planning |
| process innovations that arise once a project is underway, and |
| the feedback from our user community on our achievements to date. |
| We think an agile planning and development process, in which |
| progress is incremental, near-term deliverables are focused, and |
| long-term planning is flexible, will be the best way to achieve |
| this.</FONT></P> |
| </UL> |
| <P STYLE="margin-left: 0in"><B>Scope<BR><BR></B><FONT FACE="arial, helvetica, geneva, sans-serif">Data-centric |
| applications are those having an association with a data source, |
| and a mapping from a data source to an in-memory model. The |
| distinguishing characteristic of such applications is that their |
| domain of capabilities is no more specific than <I>data-centric</I>. |
| For instance, while a Java source file and its in-memory |
| representation could be considered data, the domain of Java |
| development is clearly present, and is more specific than just |
| “data.” Thus, <I>data-centric</I> delineates an |
| abstract, foundational domain, which is superseded by more |
| specific domains when the application manipulates something more |
| than just “data.” An application with a more specific |
| domain is <I>data-dependent</I> rather than <I>data-centric</I>. |
| <I>Data-dependent</I> applications are not within the scope of |
| this project.</FONT></P> |
| <P STYLE="margin-left: 0in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Using |
| a model-driven approach, the Data Tools Project (DTP) consists of |
| extensible frameworks and exemplary tools for data-centric |
| applications. These include:</FONT></FONT></P> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>In-memory |
| representation: Models providing a domain-based interaction with |
| data, such as database definitions, query models, result sets, |
| and objects. These models provide the basis upon which all other |
| DTP components are constructed.</FONT></FONT></P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Connectivity: |
| Specification and configuration of data source drivers. </FONT></FONT> |
| </P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Management: |
| Administration of data sources including both generic and |
| vendor-specific configuration options. Examples include adding |
| and removing tables from a database, setting type information for |
| contained data, and setting performance parameters.</FONT></FONT></P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Data-centric |
| model transformation: Changing data from one format to another is |
| a common task in data-centric application development. For |
| example, there are several popular dialects of the SQL standard. |
| A query using vendor-specific-dialect extensions is useless when |
| used with another vendor’s data source. Hence, there is a |
| need to translate between the two dialects.</FONT></FONT></P> |
| </UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Extract-Transform-Load: |
| Obtaining data from and supplying data to data sources, typically |
| using large-scale batch movements and involving data checking and |
| validation. Often includes some operations on data obtained |
| before loading into target data source.</FONT></FONT></P> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Data |
| Mapping: Mapping between data source and in-memory |
| representation, used for bridging between domains such as object, |
| relational, hierarchical, and multi-dimensional data structures. </FONT></FONT> |
| </P> |
| </UL> |
| <P STYLE="margin-left: 0in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Although |
| the scope of DTP includes exemplary connectors for popular open |
| source and commercial data sources, these are not necessarily |
| intended to be the definitive connectors. Instead, they are |
| intended to serve two purposes. First, they are intended to enable |
| users to immediately use these data sources, although possibly |
| without exploiting all their features. Second, they are intended |
| to serve as examples to both commercial and open source developers |
| who want to integrate data sources into Eclipse. It is consistent |
| with the goals of this project that the exemplary connectors |
| become superseded by more complete implementations provided by |
| third parties, both commercial and open source. </FONT></FONT> |
| </P> |
| <P STYLE="margin-left: 0in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2><B>Projects</B></FONT></FONT></P> |
| <P STYLE="margin-left: 0in; font-weight: medium"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Initially |
| DTP will contain the following three projects, and emphasize |
| relational data sources and structures.</FONT></FONT></P> |
| <H3 CLASS="western" STYLE="margin-left: 0.79in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Model |
| Base</FONT></FONT></H3> |
| <P STYLE="margin-left: 0.79in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>The |
| Model Base project provides the foundation for DTP. Using industry |
| best practices such as model-driven development with UML, and |
| taking advantage of the Eclipse Modeling Framework (EMF), |
| initially included are models for:</FONT></FONT></P> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Driver |
| definition</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Database |
| definition</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>SQL</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>SQL |
| Query </FONT></FONT> |
| </P> |
| </UL> |
| </UL> |
| </UL> |
| <P STYLE="margin-left: 0.79in"><FONT FACE="Arial"><FONT SIZE=2><FONT FACE="arial, helvetica, geneva, sans-serif">Key |
| features supported and benefits provided include:</FONT> </FONT></FONT> |
| </P> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif">Support |
| for change management: Models can be version controlled through |
| Eclipse team support.</FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif">Broad |
| editing support: Visual and other means of model editing, |
| integrated with EMF, enabling seamless editing and EMF model |
| generation. </FONT> |
| </P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif">Published |
| models with documentation (Java Doc) to support DTP consumers. </FONT> |
| </P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif">Extensible |
| and database-agnostic models.</FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif">Compliance |
| with the latest standards, such as SQL. </FONT> |
| </P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif">Support |
| for JDBC and other connectivity standards</FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif">Sample |
| code/plug-ins: To demonstrate model usage.</FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <H3 CLASS="western" STYLE="margin-left: 0.79in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Connectivity</FONT></FONT></H3> |
| <P STYLE="margin-left: 0.79in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>The |
| Connectivity project includes components for defining, connecting |
| to, and working with data sources. These include:</FONT></FONT></P> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Driver |
| Management Framework<BR><BR>Access to the appropriate drivers |
| is a prerequisite for programmatic interaction with data |
| sources. The Driver Management Framework (DMF) supplies an |
| Eclipse preference page enabling users to create driver |
| definitions based on supplied templates. A number of templates |
| are provided in the base installation, and additional templates |
| can be added by component developers contributing to DMF |
| extension points.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Connection |
| Management Framework<BR><BR>The Connection Management Framework |
| (CMF) is the foundation upon which specific connection types |
| are created. The connection types, called <I>Connection |
| Profiles</I> (CP), are contributed to the CMF through extension |
| points. Users then connect to data source instances by creating |
| and configuring a CP for that data source type. Data |
| source-standard configuration parameters, such as the |
| connection URL, user name, and password, are provided on CP |
| instance creation and stored as secure meta-data for the CP. CP |
| allow for host connectivity checks (“ping”), |
| connection, auto-connect on CP startup, and disconnect. |
| Further, CP Extensions enable additional functionality and |
| content to be added to a CP. For reuse of CP instance |
| configuration, base export/export functionality is provided by |
| CMF and surfaced in tools such as the DTP Explorer (see below). |
| Data source CP then become the connection providers through |
| which other DTP tooling accesses data source instances.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>JDBC |
| connection support<BR><BR>DTP will include a JDBC driver |
| template and CP, as a means of enabling database connectivity, |
| and serving as an example for further CP development. |
| Database-specific capabilities can then be surfaced as CP |
| extensions, allowing for specialization and presentation of |
| differentiating database functionality directly in that |
| database's CP.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Data |
| Source Explorer<BR><BR>The Data Source Explorer (DSE) is an |
| Eclipse view housing CP instances. From this view, CP |
| capabilities are surfaced, and data source content is |
| presented. The type and level of detail for any one instance is |
| constrained only by the CP itself. DSE also is a provider of CP |
| instance data to clients, such as drag and drop and API calls. |
| This allows data tooling requiring connection management to |
| interact with the DSE as a mediator to CP instances.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Open |
| Data Access<BR><BR>The Open Data Access (ODA) component is an |
| open and flexible data access framework that allows |
| applications to access data from both standard and custom data |
| sources. It enables data connectivity between data consumers |
| and data source providers through published run-time and |
| design-time interfaces. In addition, the framework also |
| includes an ODA driver management package that helps an ODA |
| consumer application to manage diverse behavior of individual |
| ODA data drivers. <BR><BR>A data driver is created simply by |
| implementing the run-time interfaces defined by the framework. |
| The run-time interfaces include support for establishing a |
| connection, accessing meta-data, and executing queries to |
| retrieve data. A driver can define internal data source |
| connection profiles and/or work with the CMF's Connection |
| Profiles extensions. Once developed, the driver can be |
| registered through an extension point with individual ODA |
| consumer components to enable data connectivity. The framework |
| also provides design-time interfaces to integrate custom query |
| builders within an application designer tool.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <H3 CLASS="western" STYLE="margin-left: 0.79in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>SQL |
| Development Tools</FONT></FONT></H3> |
| <P STYLE="margin-left: 0.79in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>The |
| SQL Development Tools project provides frameworks and tools for |
| deep and broad SQL support. The frameworks include:</FONT></FONT></P> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Routines |
| Editor Framework<BR><BR>An extensible framework for editing |
| database routines and SQL statements. Vendor-specific |
| extensions enable specialized support for particular databases.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Routines |
| Debugger Framework<BR><BR>While routine debug support varies |
| widely in existing database offerings, the Routines Debugger |
| Framework will provide an extensible base enabling debug |
| support for specific cases in a manner consistent with existing |
| Eclipse debug infrastructure.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>SQL |
| Query Parser<BR><BR>Although SQL is defined by a standard, |
| several major dialects exist. Thus, while the standard must be |
| supported, practicality also demands flexibility in adjustment |
| to dialects. The SQL Query Parser meets these needs by |
| providing an extensible framework, enabling dialect-aware SQL |
| components and tools.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>SQL |
| Execution Plan Framework<BR><BR>The ability to understand how a |
| SQL evaluation engine will execute a given query is vital in |
| tuning queries to optimize performance. The SQL Execution Plan |
| Framework will provide a means for capturing and presenting |
| execution plans in a generic fashion, enabling |
| extensions to |
| customize support for specific SQL execution engines.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <P STYLE="margin-left: 0.79in"><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>The |
| tools include:</FONT></FONT></P> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>SQL |
| Editor<BR><BR>The SQL Editor will provide an exemplary tool for |
| standard text-based editing of SQL statements. Providing |
| content assist tied to the SQL Model, syntax colorization, and |
| multiple statement support, this editor will provide an |
| essential tool for data-centric development.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Visual |
| SQL Builder<BR><BR>The Visual SQL Builder allows for graphical |
| editing of SQL, raising the level of abstraction, increasing |
| developer productivity, and making query construction possible |
| for a wider user base.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Results |
| View<BR><BR>The Results View displays the output of routine or |
| SQL statement execution in a tabular form typical of SQL result |
| sets. These results can be exported to persistent storage in a |
| variety of formats and reloaded at a later time into the |
| results view.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <UL> |
| <UL> |
| <UL> |
| <LI><P><FONT FACE="arial, helvetica, geneva, sans-serif"><FONT SIZE=2>Script |
| History<BR><BR>Typically a number of scripts will be executed |
| repeatedly during the course of data-centric development. The |
| ability to retain a history of these queries and thereby |
| quickly repeat execution of them and view results increases |
| productivity. The Script History is a view meeting these needs, |
| based on a development session.</FONT></FONT></P> |
| </UL> |
| </UL> |
| </UL> |
| <P><FONT FACE="arial, helvetica, geneva, sans-serif"><B>Other |
| Terms<BR><BR></B>This Charter inherits all terms not otherwise |
| defined herein from the Eclipse Standard Top-Level Charter |
| (</FONT><U><FONT COLOR="#0000ff"><A HREF="/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html"><FONT FACE="arial, helvetica, geneva, sans-serif">/org/processes/Eclipse_Standard_TopLevel_Charter_v1.0.html</FONT></A><FONT FACE="arial, helvetica, geneva, sans-serif">)</FONT></FONT></U><FONT FACE="arial, helvetica, geneva, sans-serif">. |
| This includes, but is not limited to, sections on the Program |
| Management Committee, Roles, Project Organization, The Development |
| Process, and Licensing. </FONT> |
| </P> |
| </TD> |
| <TD WIDTH=1% VALIGN=TOP></TD> |
| </TR> |
| </TABLE> |
| <P><BR><BR> |
| </P> |
| </BODY> |
| </HTML> |
