On Sun, Jun 24, 2012 at 11:32 AM, Jody Garnett <jody.garn...@gmail.com>wrote:
> I think getDescriptor() is simply missing.
>
> Still don't get it. The need is either clear or it should be left out.
>
> I don't get what you don't get :(
>
> getSchema(): FeatureType (holds the type of the element of the feature
> collection), consider rename to getType()?
> getDescriptor(): AttribtueDescriptor (holds the name of the elements of
> the feature collection)
>
> There is a separate proposal to add getDescriptor(), we can choose if we
> want to have getType() at that point in time, rather then hold up this "pre
> release deprecation" check.
>
Well, I don't get why we need the name to start with. In my mind a feature
collection is either a stand alone container,
for which I don't see the need of a descriptor, or it could be the value of
a complex feature property, but in the latter case
the property already has its own descriptor.
What's the use case for having a descriptor of a collection?
Cheres
Andrea
--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
