[Auscope-geosciml] boo-boo in GeologicEvent [SEC=UNCLASSIFIED]

Oliver.Raymond at ga.gov.au Oliver.Raymond at ga.gov.au
Fri Sep 25 10:22:01 EDT 2009

TM_period appears to have a strange structure.  I also can't seem to find an ISO element which has an upper and lower TM_Coordinate (which is what we want).  And the apparent lack of link to from TM elements to DQ elements for denoting error is a show-stopper for using purely a ISO solution.

Is there any benefit in creating a time-based equivalent of CGI_NumericRange called CGI_TimeRange, with a CGI_TimeMeasure inheriting from TM_Coordinate?


-----Original Message-----
From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of stephen richard
Sent: Friday, 25 September 2009 10:00 PM
To: auscope-geosciml at lists.arcs.org.au
Subject: [Auscope-geosciml] boo-boo in GeologicEvent

There was some uncertainty on my part yesterday as to whether TM_Period is the correct type for numericAgeDate. After studying the ISO 19108 temporalSchema some more, I conclude its not; it only allows a time coordinate specified by a single number, no uncertainty. I recommend we change TM_Period to CGI_NumericRange; this is more consistent with the rest of the model, represents what we want better, and avoids another proxy for a GML3.2 element for v. 3 testing.

Auscope-geosciml mailing list
Auscope-geosciml at lists.arcs.org.au

More information about the GeoSciML mailing list