Re: [GeoNetwork-devel] ISO19119

[Lagarde P. <P.L...@br...>]

Hi francois,=20
=20
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.=20

I try to integrate the last one in a new schema in GN but without success=
 for the moment... =20

Pierre.=20


________________________________

De : Fran=E7ois Prunayre [mailto:fx....@oi...]=20
Envoy=E9 : vendredi 6 avril 2007 13:48
=C0 : Lagarde Pierre
Cc : geo...@li...; geo...@li...urc=
eforge.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 2=
006 ...=20
I'm wondering if we could mutualize some xsd files in all that new schema=
s and profils, because we always have references to gml, gco, gmx, gsr sc=
hemas ...=20
=20
Task 2 : we could use the ISO standard in order to link  :
- "Service OperatesOn Metadata". On the srv:OperatesOn tag we could gmd:M=
D_DataIdentification tag to describe all datasets or use an xlink attribu=
te to link to another file ?=20
- "Metadata ParentOf Metadata" using gmd:parentIdentifier
but can't link "Metadata provided by Service" ... is there any profils wi=
th an extension of ISO19139 to create such a link ?
=20
Do you know if people working on the INSPIRE DT have ideas on that point =
?=20
=20
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.=20
=20
Cheers. Francois

________________________________

De : geo...@li... [mailto:geonetwork-de=
vel...@li...] De la part de Lagarde Pierre
Envoy=E9 : vendredi 6 avril 2007 09:23
=C0 : Fran=E7ois Prunayre; geo...@li...; geonet=
wor...@li...
Objet : Re: [GeoNetwork-devel] ISO19119


Hi francois,=20
=20
I confirm you the interest to implement the ISO19119 in GN to use in Geos=
ource. I'll split in 3 tasks :
=20
    1 / Add a new schema in GN with 19119 implementation and definition o=
f specific template to access it.=20
    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=
=2E With data MD, no link available with 19115 standarsd. In GN, two solu=
tions to manage the link :=20
                    - add a link table of MD. This table allows to manage=
 the link 19115/19119, but also 19115/19115, 19115 / 19119 and so one.=20
                    - use only the OperatesOn attribute in the 19119 stan=
dards.=20
=20
I prefer the first solution but need a "important" change of GN.=20
=20
    3 / Create a useful interface to add the link between the two metadat=
a. 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 addr=
ess (it's a service !). Perhaps the use of subtemplates but I don't reall=
y success in using with beta version...=20
=20
=20
A first proposition for the discussion...=20
   =20
Pierre,=20
=20

________________________________

De : geo...@li... [mailto:geonetwork-de=
vel...@li...] De la part de Fran=E7ois Prunayre
Envoy=E9 : vendredi 6 avril 2007 08:12
=C0 : geo...@li...
Objet : [GeoNetwork-devel] ISO19119


Hi, anyone working on implementing ISO19119 (Geographic information : ser=
vices) in Geonetwork ? I will be interested on discussing that topic if s=
ome of you are working on that.=20
=20
Thanks for any feedback.=20
=20
Cheers=20
Francois

Le contenu de ce m=E9l et de ses pi=E8ces jointes est destin=E9 =E0 l'usa=
ge exclusif du=20
(des) destinataire(s) express=E9ment d=E9sign=E9(s) comme tel(s). En cas =
de r=E9ception de ce=20
 m=E9l par erreur, le signaler =E0 son exp=E9diteur et ne pas en divulgue=
r le contenu.=20
L'absence de virus a =E9t=E9 v=E9rifi=E9 =E0  l'=E9mission du message. Il=
 convient n=E9anmoins de=20
v=E9rifier l'absence de contamination =E0 sa r=E9ception.
=20
The contents of this email and any attachments are confidential. They are=
 intended for=20
the named recipient(s) only. If you have received this email in error ple=
ase notify the=20
system manager or  the sender immediately and do not disclose the content=
s to=20
anyone or make copies. eSafe scanned this email for viruses, vandals and =
malicious=20
content.
*************************************************************************=
*********************
Le contenu de ce m=E9l et de ses pi=E8ces jointes est destin=E9 =E0 l'usa=
ge exclusif du=20
(des) destinataire(s) express=E9ment d=E9sign=E9(s) comme tel(s). En cas =
de r=E9ception de ce=20
 m=E9l par erreur, le signaler =E0 son exp=E9diteur et ne pas en divulgue=
r le contenu.=20
L'absence de virus a =E9t=E9 v=E9rifi=E9 =E0 l'=E9mission du message. Il =
convient n=E9anmoins de=20
v=E9rifier l'absence de contamination =E0 sa r=E9ception.=20
The contents of this email and any attachments are confidential. They are=
 intended for=20
the named recipient(s) only. If you have received this email in error ple=
ase notify the=20
system manager or the sender immediately and do not disclose the contents=
 to=20
anyone or make copies. eSafe scanned this email for viruses, vandals and =
malicious=20
content.
*************************************************************************=
*********************