[GeoSciML] pattern to use for decoupling packages in OGC type modular implementation

Simon.Cox at csiro.au Simon.Cox at csiro.au
Thu Aug 16 21:32:16 EDT 2012

There is a lot of sense to that.
What I proposed in my mails in June was to go straight to the pattern below and implicitly to put the 'complete' model aside.
But I recognize that there are merits in having the complete model for view as an abstract model, perhaps being less picky about cardinalities and omitting 'nillable' concerns altogether.
The question then would be how to link from the implementation model to the abstract model, which presumably acts as the 'canonical' view and would have a lot of semantic description embedded.
Do you have explicit dependencies from each class or even attribute and association in the implementation view back to the abstract model?
If not, then they will certainly drift apart ...

From: Steve Richard [mailto:steve.richard at azgs.az.gov]
Sent: Friday, 17 August 2012 3:51 AM
To: Cox, Simon (CESRE, Kensington)
Cc: A mailing list for GeoSciML
Subject: pattern to use for decoupling packages in OGC type modular implementation

Simon-here's what we're contemplating as a pattern to reduce dependencies in GeoSciML and generate a more modular implementation. Current thinking is to make GeosciML v3 schema an abstract specification, and then use a pattern like this to generate modular implementation:

[cid:image001.png at 01CD7C58.F60659B0]

Any thoughts?

Stephen M Richard
Arizona Geological Survey
416 W. congress #100
Tucson, AZ
AZGS: 520-770-3500
Office: 520-209-4127
FAX: 520-770-3505

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20120817/c43e0bdb/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 21665 bytes
Desc: image001.png
URL: <http://lists.opengeospatial.org/pipermail/geosciml/attachments/20120817/c43e0bdb/attachment.png>

More information about the GeoSciML mailing list