Hi francois,
I found in http://eden.ign.fr/xsd/csw_profile the version of 15 November 2006 and in OGC portal (members only), in the CSW 19115/19119 RWG project, the version of 30 march 2007.
I try to integrate the last one in a new schema in GN but without success for the moment...
Pierre.
________________________________
De : François Prunayre [mailto:fx.prunayre@anonymised.com]
Envoyé : vendredi 6 avril 2007 13:48
À : Lagarde Pierre
Cc : geonetwork-devel@lists.sourceforge.net; geonetwork-users@anonymised.comorge.net
Objet : RE: [GeoNetwork-devel] ISO19119
Ok Pierre, thanks for your feedback 
Task 1 : Which version are you using, I have version of the 15 November 2006 ...
I'm wondering if we could mutualize some xsd files in all that new schemas and profils, because we always have references to gml, gco, gmx, gsr schemas ...
Task 2 : we could use the ISO standard in order to link :
- "Service OperatesOn Metadata". On the srv:OperatesOn tag we could gmd:MD_DataIdentification tag to describe all datasets or use an xlink attribute to link to another file ?
- "Metadata ParentOf Metadata" using gmd:parentIdentifier
but can't link "Metadata provided by Service" ... is there any profils with an extension of ISO19139 to create such a link ?
Do you know if people working on the INSPIRE DT have ideas on that point ?
Task 3 : It could be nice to have an import process like the one for DC, FGDC & ISO transforming a GetCapability file to an ISO19139 ... a lot of info are already on the GetCapabilities operation of a service.
Cheers. Francois
________________________________
De : geonetwork-devel-bounces@lists.sourceforge.net [mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Lagarde Pierre
Envoyé : vendredi 6 avril 2007 09:23
À : François Prunayre; geonetwork-devel@lists.sourceforge.net; geonetwork-users@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] ISO19119
Hi francois,
I confirm you the interest to implement the ISO19119 in GN to use in Geosource. I'll split in 3 tasks :
1 / Add a new schema in GN with 19119 implementation and definition of specific template to access it.
2 / Allow the link between an service MD and Data MD. If you create a Service MD, a specific field allows to link ("OperatesOn") with datasets. With data MD, no link available with 19115 standarsd. In GN, two solutions to manage the link :
- add a link table of MD. This table allows to manage the link 19115/19119, but also 19115/19115, 19115 / 19119 and so one.
- use only the OperatesOn attribute in the 19119 standards.
I prefer the first solution but need a "important" change of GN.
3 / Create a useful interface to add the link between the two metadata. I explain. Currently, When you create a MD 19115 (or 19139), you could quickly add a WMS address (in distribution/onlineresource). With 19119, you have to create a specific service 19119 file to identify the WMS address (it's a service !). Perhaps the use of subtemplates but I don't really success in using with beta version...
A first proposition for the discussion...
Pierre,
________________________________
De : geonetwork-devel-bounces@lists.sourceforge.net [mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de François Prunayre
Envoyé : vendredi 6 avril 2007 08:12
À : geonetwork-devel@lists.sourceforge.net
Objet : [GeoNetwork-devel] ISO19119
Hi, anyone working on implementing ISO19119 (Geographic information : services) in Geonetwork ? I will be interested on discussing that topic if some of you are working on that.
Thanks for any feedback.
Cheers
Francois
Le contenu de ce mél et de ses pièces jointes est destiné à l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de réception de ce
mél par erreur, le signaler à son expéditeur et ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient néanmoins de
vérifier l'absence de contamination à sa réception.
The contents of this email and any attachments are confidential. They are intended for
the named recipient(s) only. If you have received this email in error please notify the
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.
**********************************************************************************************
Le contenu de ce mél et de ses pièces jointes est destiné à l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de réception de ce
mél par erreur, le signaler à son expéditeur et ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient néanmoins de
vérifier l'absence de contamination à sa réception.
The contents of this email and any attachments are confidential. They are intended for
the named recipient(s) only. If you have received this email in error please notify the
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.
**********************************************************************************************