Motivation:	Ben noticed that our use of Name was inconsistent, we need to fix that up.
Contact:	Jody Garnett
Tracker:	http://jira.codehaus.org/browse/GEOT-XXXX
Tagline:	a rose by any other name? type or instance

This page represents the current plan; for discussion please check the tracker link above.

Tasks
API Changes

Data Access
FeatureSource
FeatureCollection

Documentation Changes

Description

In the DataAccess super class for DataStore proposal a List<Name> was introduced to DataAccess. It is not clear if these names refer to the content (ie a Descriptor) or to the type (ie FeatureType) - the language used in the javadocs was "names of the available Resources".

This is an aspect of the feature model that was new to the development community and we did not notice this gap until implementation.

Feature Name	Name used to retrieve the content; like an identifier for the data set
Schema Name	Name of the type or schema the content is available in

Unless a datastore is publishing a formal schema defined else where (or has otherwise separated out an information model that they are publishing against) these two names will be the same.

This may be tricky where two tables in a database have the same structure. The table name would show up as the feature name; the description of the structure would be the type name. By sharing a structural description the two tables would be able to reuse Styles definitions.

Status

This proposal is under attack from all sides.

Voting has not started yet:

Tasks

This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success