[Auscope-geosciml] CGI Value abomination

Rob.Atkinson at csiro.au Rob.Atkinson at csiro.au
Tue Sep 1 18:22:09 EDT 2009


would it be possible to recast CGI_Value as a facade to an implementation as a specialisation of ISO19146, and have a canonical implementation of ISO19146 using a pre-defined set of service interfaces (SKOS maybe + something with more ontological power?)

This way no client models actually need to change. The implementation of CGI_Value using the old model is now an implementation choice, that can be deprecated. New systems (with suitable deployment profiles) could demand the canonical implementation.


Rob Atkinson
Team Leader, Interoperable Systems
CSIRO Land & Water
Ph (mobile) +61 419 202 973


________________________________
From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Simon Cox
Sent: Tuesday, 1 September 2009 5:10 PM
To: Oliver.Raymond at ga.gov.au
Cc: auscope-geosciml at lists.arcs.org.au
Subject: [Auscope-geosciml] CGI Value abomination

Ollie, others:

I have been grumbling about this for a while, and hope that it can be addressed in the upcoming meeting in Quebec.


Way too many of the class attributes in GeoSciML use CGI_Value and its variants.

I am fully aware of the history of when CGI_Value it was created (Ottawa, 2005) and its value (it allowed us to move forward on the bigger issues).
It also allowed a lazy UML design process, where for most atttributes the type was set following a logic of just 'we can't really think about this now but it'll be some kind of word/number'.

Now I think it is time to set it aside and move on.

My fundamental objections to the almost ubiquitous use of CGI_Value are
(i) it is hard to implement - it relies on XML Schema substitution groups
(ii) it is not compatible with any other domain schema
(iii) it allows data providers to be 'lazy' and create instances that are not interoperable on arrival
(iv) it forces decisions required for data-fusion over to the client - this is fundamentally what a standard encoding is supposed to avoid!
(v) it privileges a marginal GeoSciML use-case (transmission of field data) at the expense of the dominant use-case (exchange of quality-controlled archival data).

Most of the time, the client will refer to 'standard definitions' provided in the GeoSciML concept schemes to translate the values provided into standard forms anyway, so why not get the provider to do that rather than the client

It is the job of the GeoSciML design task group to actually make some choices, fix the type of the basic class attributes, and then require that service providers conform - make them make the choice about the 'best' value for an attribute, don't shirk the job and push it back to the client.

Almost all CGI_Value should be replaced by
(a) ScopedName
(b) Measure
with just a few being
(c) Range (new type)

Simon



--------------------------------------------------------
Simon Cox

European Commission, Joint Research Centre
Institute for Environment and Sustainability
Spatial Data Infrastructures Unit, TP 262
Via E. Fermi, 2749, I-21027 Ispra (VA), Italy
Tel: +39 0332 78 3652
Fax: +39 0332 78 6325
mailto:simon.cox at jrc.ec.europa.eu
http://ies.jrc.ec.europa.eu/simon-cox

SDI Unit: http://sdi.jrc.ec.europa.eu/
IES Institute: http://ies.jrc.ec.europa.eu/
JRC: http://www.jrc.ec.europa.eu/

--------------------------------------------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20090902/b6129bee/attachment.htm>


More information about the GeoSciML mailing list