Justin Deoliveira wrote:
> Starting a new thread for this one.
>
> Sure its useful but in most cases it just does not apply. I mean
> consider the three types data stores we have:
>
> * file based (shapefile)
> * database (postgis)
> * services (wfs)
>
> And consider the following metadata:
My priorities would be
shapefile database wfs wms
title x x x x
keywords x x x x
description x x x x
publisher x x
type x x x x Formally
schema
source x x x x
icon x x x x
Notes:
- Schema is used to indicate the kind of service this is ... looks like
you would like this encoded as an instanceof check? I will stick with a
URI but it would be good to call it "type".
- Icon is needed by any client api; since we have an open ended set of
services (ie a plug-in system) we need to ask data source providers to
provide icons; we cannot guess up front.
- the remaining entries requested by the osgeo data list have to do with
access fees and license or something; and I don't really care
For information on the contents (called "resource" to match OWS specs)...
title x x x x
keywords x x x x
description x x x x
name
schema x x x x
icon x x x x
bounds x x x x
crs
Notes:
- name - is the machine readable name; not needed here as it is part of
the data model already
- schema - is the URI for the FeatureType; I really want to track this
as it lets me know when a specific Style can be used, a specific editor,
or data taken from one place to another etc...
- icon - even more important this time out
- crs is not needed as it is covered by getBounds().getCRS()
- gabriel really wanted a latLonBoundingBox, it can be considered if you
wish...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
