[auscope-geosciml] Sequence of Events
Laxton, John L.
jll at bgs.ac.uk
Fri Apr 15 04:58:40 EDT 2011
Thanks for that. Your statement that ‘The two GeologicEvents are two GeologicFeatures….’ is the bit I don’t understand. GeologicEvents aren’t GeologicFeatures so I don’t see how the target/source associations can point to GeologicEvents? It was to overcome this that I suggested we needed GeologicEventRelation with target/source associations to GeologicEvent.
From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Bruce.Simons at dpi.vic.gov.au
Sent: 15 April 2011 05:40
To: auscope-geosciml at lists.arcs.org.au
Subject: Re: [auscope-geosciml] Sequence of Events
Sorry for the delay but I've been trying to get the instance documents to validate in order to produce an example (without success so far - so no example produced).
> Surely GeologicFeatureRelation is describing the relationship between two GeologicFeatures, not two GeologicEvents applying to the same GeologicFeature?
The two GeologicEvents are two GeologicFeatures that relate to the same GeologicUnit (they may also relate to other GeologicUnits). The GeologicFeaturerelation is describing the relationship between these two events in terms of the enclosing GeologicUnit. The following captures that:
<gsml:GeologicEvent gml:id="Event 1">
<gsml:relationship codeSpace="http=URI for event relationships">Preceding Event</gsml:relationship>
<gsml:sourceRole codeSpace="http-URI for event roles">precedes</gsml:sourceRole>
<gsml:targetRole codeSpace="http-URI for event roles">succeeds</gsml:targetRole>
<gsml:target xlink:href="Event 1"/>
<gsml:source xlink:href="Event 2"/>
Ideally the relationship between the GeologicEvents external to the GeologicUnit would be consistent with the relationship between the GeologicEvents within the GeologicUnit.
So an alternative is to describe the relationships between all the GeologicEvents (a GeologicEvent WFS) and then refer to these byReference from within the GeologicUnit (this would need testing).
Of course neither adequately covers specifying the ordering of GeologicEvents, which it should, but was left out as being too hard in Ottawa.
Senior Information Geoscientist
IUGS-Commission for Geoscience Information Oceania Councillor
GeoScience Victoria/Australian Spatial Research Data Commons
Level 9, 55 Collins St
PO Box 4440
Melbourne, Victoria, 3001
Ph: +61-3-9658 4502
Fax: +61-3-9658 4555
Mobile: +61 429 177155
From: "Laxton, John L." <jll at bgs.ac.uk>
To: "auscope-geosciml at lists.arcs.org.au" <auscope-geosciml at lists.arcs.org.au>
Date: 08/04/2011 09:04 PM
Subject: [auscope-geosciml] Sequence of Events
Sent by: auscope-geosciml-bounces at lists.arcs.org.au
There is a note attached to GeologicEvent in the model stating that the sequence of GeologicEvents can be handled with GeologicFeatureRelation. I’m not quite clear how this will work. Surely GeologicFeatureRelation is describing the relationship between two GeologicFeatures, not two GeologicEvents applying to the same GeologicFeature? Do we not need a GeologicEventRelation subtype of GeologicRelation with source/target links to GeologicEvent?
British Geological Survey
West Mains Rd
Edinburgh, EH9 3LA
Tel: +44 (0)131 667 1000
Fax: +44 (0)131 668 1535
email: jll at bgs.ac.uk
Web site: www.bgs.ac.uk<http://www.bgs.ac.uk/>
Internet Shop: www.thebgs.co.uk<http://www.thebgs.co.uk/>
This message (and any attachments) is for the recipient only. NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system._______________________________________________
auscope-geosciml mailing list
auscope-geosciml at lists.arcs.org.au
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the GeoSciML