[GeoNetwork-devel] CSW 19139-19119 schemas [SEC=UNCLASSIFIED]

GeoNetwork GeoNetwork Developer
1

Hi All,

ALARM BELLS are ringing in my head regarding this email thread. I believe
that the ISO 19139 XML implementation was created because there were so many
different implementations of ISO 19115 that none of them were the same and it
wasn't interoperable. With ISO 19139 there is now an official TC 211 XML
implementation that can be used to prove compliance (mostly and with some
added Schematron) to ISO 19115.

Are we getting into the same situation of multiple implementations of ISO
19119 without an official TC 211 XML implementation? This can't be
supported. We *must* have one ISO 19119 XML implementation that is approved
by the ISO TC 211 and this must be the only one used to prove compliance to
ISO 19119. Otherwise we will be in the same situation as the implementations
for ISO 19115 before ISO 19139 was approved.

We in Australia (mostly Nick Ardlie working for Geoscience Australia) put a
lot of effort into making sure that the eden web site XSDs were properly
implementing ISO 19119. It seemed to be accepted by those experts who were
contributing to the development of this XML. I would be very worried if
something else was adopted for proof of compliance to ISO 19119 of XML
document instances because it may be going against what these experts
approved.

Having said that, I don't see a problem in using any other way of
implementing a CSW that serves this XML as long as it is compliant to the CSW
specification.

If I have misinterpreted this thread and "jumped the gun" in assuming that
there may be multiple XML implementations of ISO 19119 then please flame me.
(It may be more efficient if there is only one email that does the flaming.)
;--)

Thanks.

John

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] On
Behalf Of Lagarde Pierre
Sent: Tuesday, 8 January 2008 1:51 AM
To: Jeroen Ticheler; geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] CSW 19139-19119 schemas

Hi jeroen,

A happy new year and a long life of GN...

For 19119, we prefer to use the profile ISO 1.0.0 CSW 2.0.2 -
http://www.opengeospatial.org/standards/cat

And you could find the official schema on OGC repository :
http://schemas.opengis.net/csw/2.0.2/ - only supplemental
information in regard of the 19119 standards and linked with
http://schemas.opengis.net/iso/19139/20060504/ (where the srv
directory includes 19119 schema).

Cheers,

Pierre

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la
part de Jeroen Ticheler
Envoyé : lundi 7 janvier 2008 15:21
À : geonetwork-devel@lists.sourceforge.net
Objet : [GeoNetwork-devel] CSW 19139-19119 schemas

Hi all,
I searched and found this page and downloadable schemas that
are a draft of how to encode 19119 service metadata:

http://eden.ign.fr/xsd/csw_profile

The release is dated 15 November 2006 (!).

I would be keen to hear from people if this is the latest
that was done on this issue and if more can be expected?

We should discuss what schemas we use when adding 19119
service metadata support. :slight_smile: François, did you already have
this/a schema for 19119 encoding?

Ciao,
Jeroen
--------------------------------------------------------------
-----------
This SF.net email is sponsored by: Microsoft Defy all
challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
**************************************************************
********************************

Pensez à l'environnement avant d'imprimer ce message
Think Environment before printing

Le contenu de ce mél et de ses pièces jointes est destiné à
l'usage exclusif du (des) destinataire(s) désigné
(s)
comme tel(s).
En cas de réception par erreur, le signaler à son expéditeur
et ne pas en divulguer le contenu.
L'absence de virus a été vérifiée à l'émission, il convient
néanmoins de s'assurer de l'absence de
contamination à sa réception.

The contents of this email and any attachments
areconfidential. They are intended for the named recipient
(s)
only.
If you have received this email in error please notifythe
system manager or the sender immediately and do
not
disclose the contents to anyone or make copies.
eSafe scanned this email for viruses, vandals and malicious content.

**************************************************************
********************************

--------------------------------------------------------------
-----------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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

2

Hi John,

I’m sorry to confirm your observation that there are more different implementations of ISO19115 Metadata Schema than you probably expected - and it’s even worse: ISO19139 Metadata XML Implementation already is not compatible with the initially “higher level” ISO19118 Encoding and CSW 2.0.2 is about 127 pages (plus references to many mandatory ISO documents)!

I read too about your investigations to map ISO 19115/19139 to Dublin Core, since Dublin Core is part of a community (i.e. librarians, scientists) which is larger than GIS. Even here, my “acoustic sensors” tell me that there exists currently neither a usable XML encoding nor a commonly accepted minimal geospatial metadata schema which includes data and services!

Let me add that my goals are about metadata exchange between metadata catalogues (repositories) at different levels as well as between catalogues and between desktop or web-based applications - and which are implementable: i.e. simple, parsimounious, RESTful, mass-IT-adopted, etc… I’m aware of the fact that the requirements to a metadata schema and encoding seem to be higher than even for geodata itself.

Perhaps my expectations are too high. Still, currently I’m agonized regarding geo-metadata exchange… Please prove me wrong!

Stefan

2008/1/8, John.Hockaday@anonymised.com < John.Hockaday@anonymised.com>:

Hi All,

ALARM BELLS are ringing in my head regarding this email thread. I believe
that the ISO 19139 XML implementation was created because there were so many
different implementations of ISO 19115 that none of them were the same and it
wasn’t interoperable. With ISO 19139 there is now an official TC 211 XML
implementation that can be used to prove compliance (mostly and with some
added Schematron) to ISO 19115.

Are we getting into the same situation of multiple implementations of ISO
19119 without an official TC 211 XML implementation? This can’t be
supported. We must have one ISO 19119 XML implementation that is approved
by the ISO TC 211 and this must be the only one used to prove compliance to
ISO 19119. Otherwise we will be in the same situation as the implementations
for ISO 19115 before ISO 19139 was approved.

We in Australia (mostly Nick Ardlie working for Geoscience Australia) put a
lot of effort into making sure that the eden web site XSDs were properly
implementing ISO 19119. It seemed to be accepted by those experts who were
contributing to the development of this XML. I would be very worried if
something else was adopted for proof of compliance to ISO 19119 of XML
document instances because it may be going against what these experts
approved.

Having said that, I don’t see a problem in using any other way of
implementing a CSW that serves this XML as long as it is compliant to the CSW
specification.

If I have misinterpreted this thread and “jumped the gun” in assuming that
there may be multiple XML implementations of ISO 19119 then please flame me.
(It may be more efficient if there is only one email that does the flaming.)
;–)

Thanks.

John

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net ] On
Behalf Of Lagarde Pierre
Sent: Tuesday, 8 January 2008 1:51 AM
To: Jeroen Ticheler; geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] CSW 19139-19119 schemas

Hi jeroen,

A happy new year and a long life of GN…

For 19119, we prefer to use the profile ISO 1.0.0 CSW 2.0.2 -
http://www.opengeospatial.org/standards/cat

And you could find the official schema on OGC repository :
http://schemas.opengis.net/csw/2.0.2/ - only supplemental
information in regard of the 19119 standards and linked with
http://schemas.opengis.net/iso/19139/20060504/ (where the srv
directory includes 19119 schema).

Cheers,

Pierre

-----Message d’origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net ] De la
part de Jeroen Ticheler
Envoyé : lundi 7 janvier 2008 15:21
À : geonetwork-devel@lists.sourceforge.net
Objet : [GeoNetwork-devel] CSW 19139-19119 schemas

Hi all,
I searched and found this page and downloadable schemas that
are a draft of how to encode 19119 service metadata:

http://eden.ign.fr/xsd/csw_profile

The release is dated 15 November 2006 (!).

I would be keen to hear from people if this is the latest
that was done on this issue and if more can be expected?

We should discuss what schemas we use when adding 19119
service metadata support. :slight_smile: François, did you already have
this/a schema for 19119 encoding?

Ciao,
Jeroen

This SF.net email is sponsored by: Microsoft Defy all
challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

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

Pensez à l’environnement avant d’imprimer ce message
Think Environment before printing

Le contenu de ce mél et de ses pièces jointes est destiné à
l’usage exclusif du (des) destinataire(s) désigné
(s)
comme tel(s).
En cas de réception par erreur, le signaler à son expéditeur
et ne pas en divulguer le contenu.
L’absence de virus a été vérifiée à l’émission, il convient
néanmoins de s’assurer de l’absence de
contamination à sa réception.

The contents of this email and any attachments
areconfidential. They are intended for the named recipient
(s)
only.
If you have received this email in error please notifythe
system manager or the sender immediately and do
not
disclose the contents to anyone or make copies.
eSafe scanned this email for viruses, vandals and malicious content.

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

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

Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

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