[GeoNetwork-devel] Config.xml for languages

GeoNetwork GeoNetwork Developer
1

Hi Andrea,

There is a list of ISO 639-2 country codes at:

http://www.loc.gov/standards/iso639-2/ISO-639-2_values_8bits.txt

Please note that they are in a pipe "|" delimited text list. They should be
converted to XML to be used as an ISO 19139 XML codeList. I.E.
"CT_CodelistCatalogue" XML type.

Regarding the root element of metadata. The DS_DataSet is a valid root
element if it is an aggregate of dataset and metadata records. The trouble
with the ISO 19139 implementation is that there can be many root elements
depending on what object is being described. This is identified in the ISO
19115 UML by the use of aggregation associations and not composition
associations. For example,

  MD_Metadata is the root element when one metadata record is being
described,
  DS_DataSet is the root element when the dataset and aggregated
metadata records are being described,
  CI_ResponsibleParty is the root element when a CI_ResponsibleParty is
being described.

These can all exist as individual XML document instances and hence can be
referenced using the Xlink element when an XML document instance is being
created. That is, this XML document instance contains these XML document
instances.

This probably doesn't help you with your implementation but I don't think
that you should limit the root element to MD_Metadata if it is at all
possible. I'm sure there will be someone out there who, in the future, will
want to describe a DS_DataSet and will complain (like I did for MD_Metadata
;--)) that GeoNetwork doesn't allow it to be defined. Once we start defining
"series", "dataset", "featureType" and "feature" etc. XML metadata records
we will want to start relating them to each other.

We can discus this more if you like but I expect that you have got the idea.

Thanks for listening. I have always found the developers on this list to be
very accommodating if at all possible.

Thanks again.

John

-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] On
Behalf Of Andrea Carboni
Sent: Wednesday, 3 January 2007 11:12 AM
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] Config.xml for languages

Hi John,

we are glad to have your feedback and we try to make changes
you suggest
as we can. I have just changed the metadata root element from
DS_DataSet
to MD_Metadata and I will address the language codes before
the final version.

Looking into the 19139 schema, I have found that into the
codelist files there
are only 2 languages (english and francaise). Does anybody
have a list of those
codes (better in the same 19139 codelist format with short names) ?

Cheers,
Andrea

> Hi All,
>
> First of all happy new year.
>
> Secondly, I would just like to point out that ISO 19115
stipulates in the
> data dictionary that ISO 639-2 should be used for the
"language" element .
> That is, the three letter code for languages. EG. "eng".
>
> Probably now is a good time to switch to the three letter
code. Just a
> suggestion. ;--)
>
> Thanks.
>
>
> John

--------------------------------------------------------------
-----------
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

2

Hi Andrea and John,

Sorry, but I have to disagree with this.
Yes, ISO 19139's XML structure allows for many root elements (MD_Metadata, but also DS_Dataset,
DS_Aggregate and even small items like contact info elements).

However, according to OGC document "05-015" on Imagery Metadata, in chapter 6.2 "Core metadata", a structure of required core metadata elements is given, which starts with a MD_Metadata element. In the text, it says that the shown hierarchy is "prescribed by ISO 19115", so I assume ISO 19115 prescribes the use of MD_Metadata as root element.

If someone really wants to describe a DS_Dataset, or an aggregate of datasets (DS_Aggregate), or
one of the GMX extensions thereof (MX_Dataset or MX_Aggregate), the required structure is like this:
<MD_Metadata>
   <....>
   <describes>
      <DS_Dataset> or <MX_Dataset>
      <.....>
</MD_Metadata>
for a simple dataset and
<MD_Metadata>
   <....>
   <series>
      <DS_Aggregate> or <MX_Aggregate>
         <composedOf>
             <DS_Dataset> or <MX_Dataset>
         <composedOf>
             <DS_Dataset> or <MX_Dataset>
         <composedOf>
             <DS_Dataset> or <MX_Dataset>
         <.....>
</MD_Metadata>

<MD_Metadata> can even "describe" multiple -unassociated- datasets (via multiple <describes> elements) or refer to multiple series of aggregated datasets, if I'm not mistaken.

Best regards,

Tim

From: <John.Hockaday@anonymised.com>
To: <acarboni@anonymised.com>,<geonetwork-devel@lists.sourceforge.net>
Subject: Re: [GeoNetwork-devel] Config.xml for languages
Date: Wed, 3 Jan 2007 16:07:32 +1100

Hi Andrea,

There is a list of ISO 639-2 country codes at:

http://www.loc.gov/standards/iso639-2/ISO-639-2_values_8bits.txt

Please note that they are in a pipe "|" delimited text list. They should be
converted to XML to be used as an ISO 19139 XML codeList. I.E.
"CT_CodelistCatalogue" XML type.

Regarding the root element of metadata. The DS_DataSet is a valid root
element if it is an aggregate of dataset and metadata records. The trouble
with the ISO 19139 implementation is that there can be many root elements
depending on what object is being described. This is identified in the ISO
19115 UML by the use of aggregation associations and not composition
associations. For example,

MD_Metadata is the root element when one metadata record is being
described,
DS_DataSet is the root element when the dataset and aggregated
metadata records are being described,
CI_ResponsibleParty is the root element when a CI_ResponsibleParty is
being described.

These can all exist as individual XML document instances and hence can be
referenced using the Xlink element when an XML document instance is being
created. That is, this XML document instance contains these XML document
instances.

This probably doesn't help you with your implementation but I don't think
that you should limit the root element to MD_Metadata if it is at all
possible. I'm sure there will be someone out there who, in the future, will
want to describe a DS_DataSet and will complain (like I did for MD_Metadata
;--)) that GeoNetwork doesn't allow it to be defined. Once we start defining
"series", "dataset", "featureType" and "feature" etc. XML metadata records
we will want to start relating them to each other.

We can discus this more if you like but I expect that you have got the idea.

Thanks for listening. I have always found the developers on this list to be
very accommodating if at all possible.

Thanks again.

John

> -----Original Message-----
> From: geonetwork-devel-bounces@lists.sourceforge.net
> [mailto:geonetwork-devel-bounces@lists.sourceforge.net] On
> Behalf Of Andrea Carboni
> Sent: Wednesday, 3 January 2007 11:12 AM
> To: geonetwork-devel@lists.sourceforge.net
> Subject: Re: [GeoNetwork-devel] Config.xml for languages
>
> Hi John,
>
> we are glad to have your feedback and we try to make changes
> you suggest
> as we can. I have just changed the metadata root element from
> DS_DataSet
> to MD_Metadata and I will address the language codes before
> the final version.
>
> Looking into the 19139 schema, I have found that into the
> codelist files there
> are only 2 languages (english and francaise). Does anybody
> have a list of those
> codes (better in the same 19139 codelist format with short names) ?
>
> Cheers,
> Andrea
>
> > Hi All,
> >
> > First of all happy new year.
> >
> > Secondly, I would just like to point out that ISO 19115
> stipulates in the
> > data dictionary that ISO 639-2 should be used for the
> "language" element .
> > That is, the three letter code for languages. EG. "eng".
> >
> > Probably now is a good time to switch to the three letter
> code. Just a
> > suggestion. ;--)
> >
> > Thanks.
> >
> > John
>
> --------------------------------------------------------------
> -----------
> 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

-------------------------------------------------------------------------
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

_________________________________________________________________
All things trendy for Windows Live Messenger ... http://entertainment.msn.be/funwithmessenger