[GeoNetwork-devel] Metadata Exchange Format

GeoNetwork GeoNetwork Developer
1

Hi all,

here is a small PDF (4 pages) describing a file format to import/export metadata and data.
I'm starting to implement it but I would like some feedback from you in order to make it
better. The budget to implement it has already been istantiated so it is difficult to make
heavy changes but we can discuss them anyway.

Any feedback is welcome.

Have a good reading,
Andrea

(attachments)

mef-format.pdf (45.4 KB)

2

Ciao Andrea,

This is a backup format (I assume all metadata records will be stored in metadata.xml).

In order to establish a geodata network there is also a need to exchange minimal metadata between metadata/catalog services and index/search services. For this there exists the international OAI-PMH protocol. => Is its implementation in GeoNetwork still scheduled by January/February 2007?

– Stefan

2006/11/13, Andrea Carboni <acarboni@anonymised.com>:

Hi all,

here is a small PDF (4 pages) describing a file format to import/export metadata and data.
I’m starting to implement it but I would like some feedback from you in order to make it
better. The budget to implement it has already been istantiated so it is difficult to make
heavy changes but we can discuss them anyway.

Any feedback is welcome.

Have a good reading,
Andrea

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

3

Hi Stefan,

the MEF format and the OAI-PMH protocol address different needs. Indeed,
the former is a format (define what gets moved) and the latter is a protocol
(define how to move contents).

The idea behind the MEF format is to bundle the metadata with all its relevant
information that a site has. Some of this information cannot be put inside
the metadata because it is not feasible (think about a thumbnail or data itself)
or because the metadata does not have a location for it (for example the
FGDC format does not have a location to store the uuid).

Now the main idea behind the MEF is backup and harvesting: for example when
harvesting from a geonetwork node the client could use the MEF format to
harvest thumbnails, categories and privileges. We could even think to extend the
OAI-PMH protocol to move metadata in MEF format instead of simple XML.

Cheers,
Andrea

Ciao Andrea,

This is a backup format (I assume all metadata records will be stored in
metadata.xml).

In order to establish a geodata network there is also a need to exchange
minimal metadata between metadata/catalog services and index/search
services. For this there exists the international OAI-PMH protocol. => Is
its implementation in GeoNetwork still scheduled by January/February 2007?

-- Stefan

2006/11/13, Andrea Carboni <acarboni@anonymised.com>:
>
> Hi all,
>
> here is a small PDF (4 pages) describing a file format to import/export
> metadata and data.
> I'm starting to implement it but I would like some feedback from you in
> order to make it
> better. The budget to implement it has already been istantiated so it is
> difficult to make
> heavy changes but we can discuss them anyway.
>
> Any feedback is welcome.
>
> Have a good reading,
> Andrea
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> _______________________________________________
> GeoNetwork-devel mailing list
> GeoNetwork-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
>
>

4

Hi Andrea, how do you plan to build the interface for metadata export ?

Could we imagine to be able to apply a stylesheet before creating the MEF
file ? For example, allow user to select metadata based on iso19115 schema,
select the one user wants to export and then make a batch export in an
iso19139 schema ...

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Andrea
Carboni
Envoyé : lundi 13 novembre 2006 18:46
À : geonetwork-devel@lists.sourceforge.net
Objet : [GeoNetwork-devel] Metadata Exchange Format

Hi all,

here is a small PDF (4 pages) describing a file format to import/export
metadata and data.
I'm starting to implement it but I would like some feedback from you in
order to make it better. The budget to implement it has already been
istantiated so it is difficult to make heavy changes but we can discuss them
anyway.

Any feedback is welcome.

Have a good reading,
Andrea

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

5

Hi François,

now there are 2 xml services: xml.mef.import (to do) and xml.mef.export (done).
The export service is intended to export one metadata at a time and can be
called by an upper level exporter. Now it accepts the following parameters:

- 'uuid' : uuid of the metadata
- 'format' : export format among {simple, partial, full}. (simple is with no thumbnails).

Adding an xsl transformation is feasible: a client could provide the stylesheet using
a local file on the server or embedding it into the request. I don't know if this could be
usefull. For example, into the info.xml file there is the metadata schema: should I
change this value if I execute an XSL transformation ? Which should be the new value ?

Any comments?

Cheers,
Andrea

Hi Andrea, how do you plan to build the interface for metadata export ?

Could we imagine to be able to apply a stylesheet before creating the MEF
file ? For example, allow user to select metadata based on iso19115 schema,
select the one user wants to export and then make a batch export in an
iso19139 schema ...

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Andrea
Carboni
Envoyé : lundi 13 novembre 2006 18:46
À : geonetwork-devel@lists.sourceforge.net
Objet : [GeoNetwork-devel] Metadata Exchange Format

Hi all,

here is a small PDF (4 pages) describing a file format to import/export
metadata and data.
I'm starting to implement it but I would like some feedback from you in
order to make it better. The budget to implement it has already been
istantiated so it is difficult to make heavy changes but we can discuss them
anyway.

Any feedback is welcome.

Have a good reading,
Andrea

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

6

Hi Andrea, I think it could be usefull regarding two point of view :

- in a short term perspective, actually this could be useful to migrate from
an ISO19115 node to an ISO19139. But we also have a migrate procedure which
has been developped.

- in a long term perspective, I think in the coming month or year we will
have an awesome number of profils based on ISO19139 or ISO19115 (which will
be national one, thematics, european, and so on ... ). And when we will try
to exchange metadata between nodes we will have bottleneck dealing with
'profiling'. Then we will expect to have a common based format (which will
certainly be the core ISO19139). Currently, Geonetwork is easily
configurable to set up a new profil ... And I expect that a lot of users
will do so (France has ;). In such a situation, if Geonetwork is able to at
least do a MEF export to a common based format (well known by all nodes)
that could be really useful.

Then we will have to explain to users that when creating their own profil in
Geonetwork, the last step will be to define an XSL transformation between
the user's profil and the ISO19139 if they want to be able to speak with
other nodes ....

Thoughts ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Andrea
Carboni
Envoyé : vendredi 24 novembre 2006 19:43
À : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] Metadata Exchange Format

Hi François,

now there are 2 xml services: xml.mef.import (to do) and xml.mef.export
(done).
The export service is intended to export one metadata at a time and can be
called by an upper level exporter. Now it accepts the following parameters:

- 'uuid' : uuid of the metadata
- 'format' : export format among {simple, partial, full}. (simple is with no
thumbnails).

Adding an xsl transformation is feasible: a client could provide the
stylesheet using a local file on the server or embedding it into the
request. I don't know if this could be usefull. For example, into the
info.xml file there is the metadata schema: should I change this value if I
execute an XSL transformation ? Which should be the new value ?

Any comments?

Cheers,
Andrea

Hi Andrea, how do you plan to build the interface for metadata export ?

Could we imagine to be able to apply a stylesheet before creating the
MEF file ? For example, allow user to select metadata based on
iso19115 schema, select the one user wants to export and then make a
batch export in an
iso19139 schema ...

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
Andrea Carboni Envoyé : lundi 13 novembre 2006 18:46 À :
geonetwork-devel@lists.sourceforge.net
Objet : [GeoNetwork-devel] Metadata Exchange Format

Hi all,

here is a small PDF (4 pages) describing a file format to
import/export metadata and data.
I'm starting to implement it but I would like some feedback from you
in order to make it better. The budget to implement it has already
been istantiated so it is difficult to make heavy changes but we can
discuss them anyway.

Any feedback is welcome.

Have a good reading,
Andrea

--
Ce message a ete verifie par MailScanner pour des virus ou des
polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont
personnels, confidentiels et prives. Toute publication, utilisation ou
diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is
personal, confidential and secret. Any total or partial publication,
use or distribution must be authorized.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et prives. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized.

7

Hi Francois,

I won't consider the short term perspective but about the long term one,
I have these 2 considerations:

- In my vision, the metadata should be exported 'as is' and the transformation
  should be done in the client/import procedure side. This imply that the
  client 'knows' the metadata format and how to transform it. This means that
  the stylesheets must be moved to the client but this way I cannot create a
  new profile remotely and hope that the client understands it: it is reasonable
  that the node that creates a profile is also responsible for creating the stylesheets.
  
- We could add a 'schema' parameter to the xml.mef.export. If missing, the metadata
  is exported as is, otherwise geonetwork will try to convert the metadata into the
  specified format. This can be done this way: beside the xml/schemas folder (which
  contains dublin-core, fgdc, iso19139 etc...) we could add another one containing
  subfolders like <schema1>-to-<schema2>. Each subfolder will contain the stylesheets
  to convert the metadata from schema1 to schema2. Finding the proper stylesheets
  to use (if any) is simple and this way the xml.mef.export interface should have a
  behaviour similar to the CSW part.

Cheers,
Andrea

Hi Andrea, I think it could be usefull regarding two point of view :

- in a short term perspective, actually this could be useful to migrate from
an ISO19115 node to an ISO19139. But we also have a migrate procedure which
has been developped.

- in a long term perspective, I think in the coming month or year we will
have an awesome number of profils based on ISO19139 or ISO19115 (which will
be national one, thematics, european, and so on ... ). And when we will try
to exchange metadata between nodes we will have bottleneck dealing with
'profiling'. Then we will expect to have a common based format (which will
certainly be the core ISO19139). Currently, Geonetwork is easily
configurable to set up a new profil ... And I expect that a lot of users
will do so (France has ;). In such a situation, if Geonetwork is able to at
least do a MEF export to a common based format (well known by all nodes)
that could be really useful.

Then we will have to explain to users that when creating their own profil in
Geonetwork, the last step will be to define an XSL transformation between
the user's profil and the ISO19139 if they want to be able to speak with
other nodes ....

Thoughts ?

Francois

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Andrea
Carboni
Envoyé : vendredi 24 novembre 2006 19:43
À : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] Metadata Exchange Format

Hi François,

now there are 2 xml services: xml.mef.import (to do) and xml.mef.export
(done).
The export service is intended to export one metadata at a time and can be
called by an upper level exporter. Now it accepts the following parameters:

- 'uuid' : uuid of the metadata
- 'format' : export format among {simple, partial, full}. (simple is with no
thumbnails).

Adding an xsl transformation is feasible: a client could provide the
stylesheet using a local file on the server or embedding it into the
request. I don't know if this could be usefull. For example, into the
info.xml file there is the metadata schema: should I change this value if I
execute an XSL transformation ? Which should be the new value ?

Any comments?

Cheers,
Andrea

> Hi Andrea, how do you plan to build the interface for metadata export ?
>
> Could we imagine to be able to apply a stylesheet before creating the
> MEF file ? For example, allow user to select metadata based on
> iso19115 schema, select the one user wants to export and then make a
> batch export in an
> iso19139 schema ...
>
>
> Francois
>
> -----Message d'origine-----
> De : geonetwork-devel-bounces@lists.sourceforge.net
> [mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
> Andrea Carboni Envoyé : lundi 13 novembre 2006 18:46 À :
> geonetwork-devel@lists.sourceforge.net
> Objet : [GeoNetwork-devel] Metadata Exchange Format
>
> Hi all,
>
> here is a small PDF (4 pages) describing a file format to
> import/export metadata and data.
> I'm starting to implement it but I would like some feedback from you
> in order to make it better. The budget to implement it has already
> been istantiated so it is difficult to make heavy changes but we can
> discuss them anyway.
>
> Any feedback is welcome.
>
> Have a good reading,
> Andrea
>
> --
> Ce message a ete verifie par MailScanner pour des virus ou des
> polluriels et rien de suspect n'a ete trouve.
>
> Les donnees et renseignements contenus dans ce message sont
> personnels, confidentiels et prives. Toute publication, utilisation ou
> diffusion, meme partielle, doit etre autorisee.
>
> Any data and information contained in this electronic mail is
> personal, confidential and secret. Any total or partial publication,
> use or distribution must be authorized.
>
>
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
Ce message a ete verifie par MailScanner pour des virus ou des polluriels et
rien de suspect n'a ete trouve.

Les donnees et renseignements contenus dans ce message sont personnels,
confidentiels et prives. Toute publication, utilisation ou diffusion, meme
partielle, doit etre autorisee.

Any data and information contained in this electronic mail is personal,
confidential and secret. Any total or partial publication, use or
distribution must be authorized.