Re: [Geotools-devel] GeoAPI-SNAPSHOT updated with ISO 19115 interfaces

[Martin D. <mar...@te...>]

Jody Garnett a =E9crit :

>>> org.opengis.metadata.MetaData and Identification contains all methods=
=20
>>> found in org.geotools.metadata.iso19115. Concequently, the later=20
>>> could be removed. Key differences are:
>>>
>>>   - org.opengis.metadata has no MetaDataElement interface, because I
>>>     didn't found it in ISO 19115. However, we could add it if a
>>>     request is send to the GeoAPI mailing list.
>>
>>
> We needed to implement this in order to query against. (Cannot write a=20
> query api against bean properties, and still expect the same api to wor=
k=20
> against metadata xml documents).

Then, could you post a proposal on the geoapi mailing list please? Or=20
maybe we should do the IRC meeting first.




> I think we are going to have more Metadata to implement then just ISO=20
> 19115 interfaces, dublin core was mentioned and for right now we need=20
> "off the cuff" metadata implementations for DataStore/GCE=20
> implementations of Catalog/CatalogEntry to work against.
>=20
> I was thinking of an abstract base class Metadata19115 implementing bot=
h=20
> interfaces that provides the required helper functions to make=20
> everything happy.

It may not be easy. If I look at my recent experience, I tried to=20
refactor the legacy CS framework for implementing both the old API and=20
the new CRS API and quikly abandonned the idea: it was too messy.=20
Implementing two differents API in same time is very difficult for=20
non-trivial API.

An other approach is to choose one API as the reference one (either ISO=20
19115 or Dublin core), and provide adapters from arbitrary metadata API=20
to the reference API. One advantage of this approach is to avoid the=20
introduction of yet an other metadata API.

	Martin.