Hi All,
The ids have another purpose and that is to identify reusable items. If I
have in an XML document located at
http://asdd.ga.gov.au/asdd/work/ISOmetadata/GAOpenDaySeries.xml with some
content in it like this:
...
<gmd:contactInfo>
<gmd:CI_Contact id="GAContactDetails">
<gmd:phone>
<gmd:CI_Telephone>
<gmd:voice>
<gco:CharacterString>+61 2 6249
9111</gco:CharacterString>
</gmd:voice>
<gmd:facsimile>
<gco:CharacterString>+61 2 6249
9999</gco:CharacterString>
</gmd:facsimile>
</gmd:CI_Telephone>
</gmd:phone>
<gmd:address>
<gmd:CI_Address>
<gmd:deliveryPoint>
<gco:CharacterString>GPO Box
378</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gco:CharacterString>Canberra</gco:CharacterString>
</gmd:city>
<gmd:administrativeArea>
<gco:CharacterString>ACT</gco:CharacterString>
</gmd:administrativeArea>
<gmd:postalCode>
<gco:CharacterString>2601</gco:CharacterString>
</gmd:postalCode>
<gmd:country>
<gco:CharacterString>Australia</gco:CharacterString>
</gmd:country>
<gmd:electronicMailAddress>
<gco:CharacterString>sales@anonymised.com</gco:CharacterString>
</gmd:electronicMailAddress>
</gmd:CI_Address>
</gmd:address>
<gmd:onlineResource>
<gmd:CI_OnlineResource>
<gmd:linkage>
<gmd:URL>http://www.ga.gov.au</gmd:URL>
</gmd:linkage>
</gmd:CI_OnlineResource>
</gmd:onlineResource>
</gmd:CI_Contact>
</gmd:contactInfo>
<gmd:role>
<gmd:CI_RoleCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI
_RoleCode"
codeListValue="pointOfContact"></gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:contact>
...
I can refer to this information in another XML document (eg.
http://asdd.ga.gov.au/asdd/work/ISOmetadata/GAOpenDaySeries.xml )using XLINK
to use the same contact details and hence save time creating the metadata and
maintaining the metadata. The bit in the XML document that calls the
GADetails looks like this:
<gmd:contact
xlink:href="http://asdd.ga.gov.au/asdd/work/ISOmetadata/GAOpenDaySeries.xml#G
ADetails"/>
There are many other xlink attributes to identify when to resolve the
information held in the XML document that has the original information. This
is a good way to maintain information because only the original document
needs to be edited if the contact details for "GADetails" changes.
There is more information about this topic at:
http://www.w3.org/TR/xlink/ and
https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/PropertyMetadata
Thanks.
John
-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] On
Behalf Of "RIVIERE Robert - CETE Méditerr./DI/ETER"
Sent: Monday, 24 September 2007 5:58 PM
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] Dealing with time in GML part 2Hi,
Jeroen wrote :> the TimePeriod element requires the gml:id attribute with
some formatted
> content to actually pass the validation. I put
gml:id="ID001" in the
> above sample and that does the job. Sorry for my ignorance,
but why
> is this supposed to be there? What is the idea behind the
identifier
> and could I just put anything I wanted in there?As far as I've understood, there is a basic principle in GML
saying that every object
has to be given an identifier.
There is at the GML level no rule specifying what to put in
the identifier. This should be
done at a higher level. For instance in Europe, INSPIRE draft
documents recommend to use a
namespace-based syntax.Hope this helps,
Robert
PS Congratulations for new GN release. Really nice work.
--------------------------------------------------------------
-----------
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