Ben should really enter this conversation :-) The app schema guys are the only ones who are experiencing this stuff....
Let me try - type name is used here: - DataAccess.getNames(): List<Name> - DataStore.getTypeNames(): String[] - DataAccess.getFeatureSource( name ); - DataStore.getFeatureSource( String); - ... Up until this point this has always been "type name" ... what it means we need to talk to Ben about. For "typeName" is the FeatureType "name" and matches to a complexType in XML Schema DataSource.getSchema().getName() DataSource.getDescriptor().getType().getName() // pending proposal as "descriptor" is not available FeatureCollection.getSchema().getName(); Feature.getType().getName() For "memberName" is a descriptor name and matches to am XML element, such as feature collection member ... this is not really "outed" in our API yet until Ben thinks it through. - DataStore.getDescriptor( name ) /// huh not sure if this makes sense? - FeatureSource.getDescriptor() // pending proposal as "descriptor" is not available - FeatureCollection.getDescriptor() // pending proposal as "descriptor" is not available What is your take on things? Jody On 05/05/2010, at 3:05 PM, Michael Bedward wrote: > Hi Jody and all, > > Looking again at the javadocs for DataStore after yesterdays > discussion about feature names vs feature type names... > > For a method like: > SimpleFeatureSource DataStore.featureSource(String typeName) > > I guess consistency dictates that the parameter should be called > "name" or "featureName" and the method docs should refer to it as such > rather than as a type name (despite the two being synonymous for > SimpleFeature). Would that be correct ? > > Michael ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
