[GeoSciML] circular dependencies Basic-Extension [SEC=UNCLASSIFIED]

Tue Apr 21 21:19:15 EDT 2015

EA v12 (and possibly v11) has built-in dependency checking.
They also have recognised the different levels of dependency (referring to diagrams vs re-using a class for example) and allow checking these. This is necessary as most of the ISO models have circular dependencies.

Cheers
Bruce Simons
Interoperable Systems
Integrated Basin Management and Informatics
CSIRO Land and Water Flagship

PO Box 56 Highett,
Graham Road, Highett, Vic 3190

Ph +61-3-92526514 |  Mob +61-429177155

________________________________________
From: GeoSciML [geosciml-bounces at lists.opengeospatial.org] on behalf of Oliver.Raymond at ga.gov.au [Oliver.Raymond at ga.gov.au]
Sent: 22 April 2015 08:20
To: geosciml at lists.opengeospatial.org
Subject: Re: [GeoSciML] circular dependencies Basic-Extension   [SEC=UNCLASSIFIED]

I agree. The dependency-checking function is very useful. I think it got added to EA (ie, without needing the solidground plugin)

If you run the dependency check on each package, it will highlight where we have mistakenly linked to swe v1 rather than swe v2.

Ollie

On 22 Apr 2015, at 8:01 am, Steve Richard <steve.richard at azgs.az.gov<mailto:steve.richard at azgs.az.gov>> wrote:

I have found Solid Ground to be very useful. CSIRO stopped working on it and supposedly some of the functionality was going to be incorporated into EA. I'm running 10.0.1007, so I don't know if any of the standards conformance stuff from solid ground has been incorporated.

steve

Stephen Richard

Chief Geoinformatics Section

Arizona Geological Survey

416 E. Congress #100, Tucson 85745

steve.richard at azgs.az.gov<mailto:steve.richard at azgs.az.gov>

520-209-4127

________________________________
From: GeoSciML <geosciml-bounces at lists.opengeospatial.org<mailto:geosciml-bounces at lists.opengeospatial.org>> on behalf of Boisvert, Eric <Eric.Boisvert at RNCan-NRCan.gc.ca<mailto:Eric.Boisvert at RNCan-NRCan.gc.ca>>
Sent: Tuesday, April 21, 2015 9:35 AM
To: Public: A mailing list for GeoSciML
Subject: Re: [GeoSciML] circular dependencies Basic-Extension

Yep, I’m still cleaning stuff in the model and I took note of the package dependency issue (there none left in the model itself).  I use ShapeChange to generate the XSD (another learning curve) and it reports issues that I fix as I go (I spent some times with Basic to learn how ShapeChange works). I’m still trying to understand why basic keeps including both SWE 1.0 and SWE 2.0 (and SWE 1.0 without any schemaLocation)

>have you been using 'SolidGround' to update the package dependency diagram

Nope, do you recommender I use it ?

De : GeoSciML [mailto:geosciml-bounces+eric.boisvert=rncan-nrcan.gc.ca at lists.opengeospatial.org] De la part de Steve Richard
Envoyé : April 21, 2015 12:26
À : A mailing list for GeoSciML (geosciml at lists.opengeospatial.org<mailto:geosciml at lists.opengeospatial.org>)
Objet : [GeoSciML] circular dependencies Basic-Extension

Eric-- have you been using 'SolidGround' to update the package dependency diagrams as you clean up the implementation model for v4 in trunk?

the Dependency diagram in GeoSciMLBasic is showing circular dependencies with GeoSciMLExtension. There should be no dependency of Basic on Extension. I don't want to delve into it if you're working on things. Let me know if I should investigate.

steve

Stephen Richard

Chief Geoinformatics Section

Arizona Geological Survey

416 E. Congress #100, Tucson 85745

steve.richard at azgs.az.gov<mailto:steve.richard at azgs.az.gov>

520-209-4127

Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks.
-------------------------------------------------------------------------------------------------------------------------