"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Meeting Minutes

Also see RomeF2FMeetingMinutesDiscussion

Monday

Berlin Meetings' outcomes

CGI Council meeting briefing - BruceSimons

CGI Report:
  1. Request from GGIC to have the EarthResourceML extension to GeoSciML governed by CGI accepted and the IWG requested to look at what resources are required to adequately govern this.
  2. Science Language Task Group and Multi-lingual Thesaurus Group (MTG) dissolved and to be re-formed as a new Task Group under the IWG.
  3. The IWG should put a budget request in to the CGI for upgrading of cookbooks, putting further documentation together (example database, example mapping and instant documents) and domain registration to maintain a permanent web address for vocabularies and schema.
  4. The IWG need to maximise their effort to establish GeoSciML WFSs, particularly in North America.
The CGI Council made it very clear that GeoSciML must be a usable standard, and not necessarily ‘perfect’ before it is rolled out.

Future Meetings:

CGI are likely to meet in June20-24 INSPIRE conference in Edinburgh, Scotland. A less likely alternative is the GSA in Minnesotta, USA in October 2011.

The IWG should aim to meet in the week prior to INSPIRE to avoid the IUGG conference in Melbourne during the last week of June 2011.

Science Language Workshop briefing - SteveRichard

Language workshop in Berlin the week before. Organised by Christine Asch 50-60 participants with new faces from Russia, China, Japan, SE Asia, Argentina --> Good participation

Sessions divided and focused on (1) purely vocabs and (2) map harmonization issues (particularly 1GEurope) Break out in small groups and discussed about priority. Came with 16 priorities and 4 have been voted by the participants. Top 4:

  1. clarify user requirements and develop best practices for collecting the requirements
  2. need a CGI web vocab service for vocabs
  3. recommendation for initiating a project for global geological maps
  4. international effort for devel a standard for international vocab standard
Of particular interest to the WG: item 2 --> CGI Will need to move the vocabs to GeoSciML.org or similar IWG/CGI managed location.

Standardise vocab service: W3C incubator group has been scoped (from Peter Fox information). We need to be represented there.

Best practice for identifiers was priority 15 in list of 16 from workshop participants, but need to be discussed by IWG.

Stratigraphic time Scale: integrating the ICS timescale in our registry with their namespace

TD: comment on last week meeting > need a international standard for vocab services. We may be able to decide where to go inside our group.

SR asked for a presentation of the different vocab services (AuScope + BRGM) in vocabuary discussion on Wednesday (no moved to Tuesday) to compare operations offered.

BS: we should ensure CGI funds some domain registration.

Technical workshop was very successful and CGI wants to run it again in the future (information session only in the past). Should have a Vocab discussion session in Asia (organized by Japanese representative) in 2011. Other meetings: Edinburg in June 2011 with INSPIRE meeting, GSA in Minnesota in October 2011. Edinburg is preferred for participation of the European. IUGG meeting in Melbourne and want CGI presentation.

GeoSciML open day briefing and outreach discussion - JohnLaxton

Friday Aug 26. V.2.1 focus. Most particpants from vocabulary workshop stay over. Breakouts in afternoon to work on people's databases that they brought. Overall successful, real measure will be how many people uptake. New Zealand, Ireland, Austria, Argentina, Denmark actively interested in implementing service.There were reservations on some parts about implementing v2.1 when v.3 is imminent. Try to simplify migration process by updating the element mapping spreadsheet to account for v.3 difference. Use of spreadsheet for element mapping was a good tool for getting people to walk through the schema and think about how their content compares. Need about half day for basic service architecture description (request and response syntax). Workshop in Beijing was 2 days for WMS workshop (not WFS). Bruce and Alistair spend 4 days at Finnish Survey with workshop for EarthResourceML (much of time on educating about purpose and utility of service) Workshop concept successful in providing a venue for people to learn about the deployment of services and GeoSciML schema without coming to workgroup meeting. More than half the work is making case to management for benefits of implementing services.

OneGeology/OneGeology Europe GeoSciML usage status - TimDuffy

15 Geological surveys in OGE serving 2.1 services according to a very specific profile. Surface geologic and bedrock geology at 1;1000000 scale. A couple of issues with schema implementation, and there are some issues with layer naming conventions. Perhaps another 15 by end of September. Requirement is to keep services for 2 years. Eurgeosurveys portal will support OGE portal and metadata catalog for continuing availability. These services will require some modification when IWG develops detailed 2.1 profile.

INSPIRE GeoSciML usage status - Main. JeanJacquesSerrano

Process is focus, for organizations to provide input. Current work is on user requirements/use cases for geology in INSPIRE. These will be used as basis to justify requirements in final content model. Will probably have to add geomorphic feature, as well as WaterML and O&M. 2 Teams--also have mineral resources team. Content model will be subject to vote, decision will have financial implications for INSPIRE service deployment. First version due end of October. This draft will define scope, main features; will be subject to review. Likely to be subset of GeoSciML.

INSPIRE is regional model, GeoSciML is intended to be global. INSPIRE can combine various packages to get implemention of content model. Model, codelist, enumerations will go into EU law. We need to carefully consider whether to include codelists and enumerations in model. (Bruce Simons)

Tim Duffy propose that IWG should agree on intention that INSPIRE geology annex schema elements that are in GeoSciML v3 should be imported from IUGS-CGI-governed schema (GeoSciML, EarthResourceML). J. Laxton-- INSPIRE may require that schema are under EU governance. JJS--committed will produce an draft specification, EC may modify. Tim's concern is to avoid reinvention of duplicate elements; considerable resource and effort has gone into GeoSciML, don't want to see effort negated. JL--in the end we don't have final control of INSPIRE/ EC decisions.Need to work with JRC on development of policy on how INSPIRE uses existing domain models/specs.

GIN GeoSciML usage status

US GIN-- testing of v2.0, now have v.3 test service implemented for Arizona. Work has focused on CSW implementation and profile (see http://lab.usgin.org/profiles/usgin-iso-19139-profile, http://catalog.usgin.org/).

GSC GIN -- GSML and Google Earth servies. Groundwater ML 2 EA version based on GeoSciML v3. Not year ready for Full Moon. Current implemention is GroundWaterML v1, GeoSciML v2. ; currently broken because of out of sync updates. http://www.opengeospatial.org/projects/initiatives/gwiebnd

Other interop experiment for groundwater. OGC experiment with USGS. USGS Nate Boot Wisconsin, Madison. GSC also involved in SOS services using O&M. Group lead by Peter Tyler, CSIRO developing WaterML 2.0 (profile of sOS, Rob Atkinson). WaterML 2 is outgrowth of WaterML 1. GeoSciML for aquifer part; WaterML for time series.SOS experiment with USGS serving time series from Canada and US, objective is dealing with trans boundary aquifers. Read Groundwater ML into Google Earth, ArcSDE, Excel. WaterML profile for OGC interop experiment. OGC has template for OGC profile.

GroundwaterML to intermediate table-structured xml via xslt, then have tools for intermediate xml to shape, geodatabase, KML, or possible map into MapInfo.

GSC working profile for groundwater services, moving from Gsml 2 to 3, will eventually be made public (end of fiscal year--April 2011?)

AuScope GeoSciML usage status

Built a portal as client few feature services, has established services from various jurisdictions. Deploying EarthResourceML, 5 of 8 have services deployed. GeoServer and Deegree implementations.

https://twiki.auscope.org/wiki/bin/view/Grid/ProjectPages

AuScope portal

Vocab service client

Vocab documentation:

Borehole instance response

NVCL O&M config for GeoServer

GeoSciML emplhasis has been on EarthResoruce ML. Portal consumes GA and GSV WMS. No GeoSciML WFS produced or consumed. Borehole GeoSciML deployed in two locations, borehole header services. Serving hyperspectral scans of core as O&M service.

Software development. Establish vocabulary service. Software development of GeoServer for application profiles of complex features. Move FullMoon to web service planned, long term sustainability of FullMoon unsure. Vocabulary service deployed by Jacquir Gilgatha, start with BRGM service. Vocab stored in triple store (Sesame). Using for EarthResoruceML commodities. Geoserver servers working from nightly releases. Beta for GeoServer 2.1 (or alpha) scheduled next week (sprint at FOSS in Madrid, Sept. 3-4). Two outstanding issues. Encoding SRS name on spatial type; Occasionally problems not encoding elements in right order. Problem chaining features in different namespaces. GSV using 2.0.2; community hoping for more solid GeoServer 2.1. How are Auscope services dealing with GeoServer issues? Services validate because problems are with optional features, some are working off or trunk builds with fixes, other workarounds; some don't validate.

Borehole services not using MappedInterval profile. Will need to discuss whether need one or 2 borehole profiles. Need to figure out how to deal with 1-D locations in GML; is 1-D geometry in simple feature profile, if not, how to represent. A simple feature profile of GML 3.2.1 is being voted on by OGC at this time.

Deegree v3 development is progressing, supporting gml3.1.1, wfs 1.1.1, GeoSciML 2.1. Have greatly improved filter capabilities. Deegree has announced to INSPIRE that will be implementing WFS v2. SAFE software not developing WFS, will recommend Deegree. Deegree has apparently re engineered the application, may be a viable deployment alternative. Snowflake has record of supporting gml 3.2.1.

WFS 2 will default to GML 3.2.1.

Shape change product for UML to XSD. EU Humboldt project is developing UML to xml tool. J.Laxton was testing, but xml schema generation is not currently in package, so couldn't test. Announced at INSPIRE meeting, but hasn't appeared yet.

ESRI USA will take part in test bed 4, testing GSML3, GML 3.2.1(?). S. Satish present at Quebec meeting. ESRI Germany offering Fusion center produce in Europe, supposed to be supplying INSPIRE compatible WFS services. Question is what is needed in WFS 2.0 and GML 3.2.1.

GA, GSV, GSC will be using Deegree, Geoserver on Oracle using SDO_spatial objects.

Questions.

how to represent SRS for boreholes, where 1-D geometry is represented in SRS for borehole trace. Currently using URI for borehole with doc fragment to represent borehole as SRS.

need to sort out agenda to determine when will discuss profiles.

Testbed 4 status

Chair -- EricBoisvert

Snowflake is only WFS2 GML 3.2 implementation. BGS is working on implementation.

OGE used GeoSciML v.2.1 because v3. schema were not available. Migration of OGE services to GSML v3 we hope will occur with migration to OneGeology Global. INSPIRE compliance will require v3.2. ESRI is supporting effort in OneGeology global.

Also have to deal with URN to URI conversion of identifiers. Implementation requires proper handling of 303 redirects and content negotiation.

Auscope had to decide on scheme to use, and went with URN's because that was the OGC and IWG scheme at the time

OGE Europe is also URN based.

Also trying to get people up to speed in using Trac system. Tool is for tracking Issues, not tasks. System requires identifying one owner for each issue. Currently only one is Ollie. Ollie is fine with those who know how to edit UML doing so by : post issue to Trac, if is simple typo, fix, then inform others of fix. More complex issues will require formal discussion process. People adding issues to Trac should post to e-mail list that issue has been posted. Explore approaches to having trac emails forwarded to Auscope GeoSciML List.

Review of Current Trac issues:

Pavel is not here to give Schematron report on case study. Ollie note that Schematron constrains can be put in XML schema. Ideally would like these to show in UML diagram. As UML constrants. Gilly will be doing a demo this afternoon.

What is schedule for completion of Tb4. What is timing for extension for TB4. Published, usable schema before Christmas 2010 and June 2011. INSPIRE Testbed in June will require GeoSciML v3; this will require a complete, released Gsml v3 profile. Problem is can't test Gsml 3 until there are server tools that will produce GSML 3 on GML 3.2.1. How much testing and what kind are necessary before release? Profiles will determine the necessary testing.

Need GeoSciML v2.1 profile and and candidate v3 profile.

GML 3.2 needs to be tested with GeoScIML for ISO metadata, identifiers, and nil reasons. Big question is when will server software be available. Deegree, GeoServer, ESRI all looking at having tools available for INSPIRE test bed. It would appear that for GSML3, GML3.1 we would need to test our proxy model for Metadata. Most GML3.1 content could be mapped to GML3.2 geosciml except for strings in ISO19115 proxy scheme. Any test services should implement GML 3.2. Those that can't server GML3.2 would need to create instance documents only.

Test of model could sufficiently be done by creating instance documents exercising all parts of model. Also need some GML3.2 test services. Currently only candidate to implement services is BGS with snowflake, GSC may be able to do with Cocoon mediator.

Remove additional borehole header issue from Trac. Dale Percival is tied up with service implementation.

EB. Should SOS be used instead of WFS for physical properties. Properties are delivered associated with specimen. SOS API is more constrained; core is designed for O&M scheme. Response is equivalent to WFS serving Observations. GetCapabilities describes queryable properties. SOS allows query by phenomenon. SOS in GeoServer see http://2010.foss4g.org/presentations_show.php?id=3800

Issue number 7, map package see comment #3 at https://projects.arcs.org.au/trac/geosciml/ticket/7

Issue 8--Deliver O&M data in a borehole. GSV has implemented, tested various approaches. Input will contribute to profile discussion tomorrow. Best solution seemed to be collection of specimens. We are using OGC O&M v2 in GeoSciML v3. Is anyone testing mapped intervals for boreholes. See discussion at https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/BoreHolesAndObservation and https://www.seegrid.csiro.au/twiki/bin/view/CGIModel/BoreHolesAndObservationDiscussion. Issue closed. Pick up in service architecture/profiles tomorrow

Issue 9. Discussion of representation of 3-D borehole trace. GML requires using multipoint. Survey data typically is a collection of vectors. Need to figure out how to do it correctly, but probably don't need to sort out here. Gilly is working on borehole data with survey and will solve with Simon Cox.

Issue 10 Geochemical data. GeoSciML as O&M Observations. Set of located specimens. Observations are results are assays. GeoSciML 2. Instrumentation proposal in v3 needs to be vetted by group. WaterML is looking at the proposal as well. Example of response document shown to group. Feature collection feature member is LocatedSpecimen/relatedObsevation/Observation/ uses same pattern as GSV/Auscope used for borehole. Observation contains analyzes. Use SWEET URI to identify components in analysis. Different observation for each analyte. No way to encode detection limits. SOS is engine that can be harvested. SOS appears to make more sense for chemical analyses. SOS capabilities would advertise 'traceElementChem' or 'WRChem'. Close Item, new ticket for v3 chemistry services to test instrumentation model if model team adopts on Thurs.

Issue 11-- Schematron to validate topic. XML Spy does not do Schematron validataion Objective does does Schematron Validation. Have to determine doing OGC or ISO (ISO19747-3) schematron. Pavel implement 2 phase validation, implemented as web service. Profile will specify schematron rules that must validate. [[http://standards.iso.org/ittf/PubliclyAvailableStandards/c040833_ISO_IEC_19757-3_2006(E).zip][ISO Schematron Spec] can actually be obtained free of charge!

Use case-- send in instance doc, first test is to determine if is xml schema valid. Then ask user if they would like to do 'schematron validation according to one of the following profiles...'

Issue 12-- this is regional vocabulary. For now the decision is that these should be under governance of regional organizations.

Issue 13 -- Ollie needs to fix UML and xml schema for v. 2.1. Francois L. is tasked to generate html documentation from repaired EA UML.

May be modeling issue if ShearDisplacementStructure should be abstract ductile shear zone and fault as concrete subtypes in GeoSciML v3. New Trac Issue. Use TWIKI for discussion, Trac to flag issues that are open.

Issue 14. Would have to change cardinality of age in EventAge to allow age assignments according to different time scales. Profile for interoperability would have to proscribe some shared vocabulary term as required.

Issue 15. Filter based on age and lithology value. Client runs get map against multiple WMS servers with SLD for filter criteria using GeoSciML; BRGM mediator on each WMS client maps the SLD filter query into query for that WMS and returns appropriated symbolized polygons. SLD is at http://onegeology-europe.brgm-rec.fr/slds/sld_quaternary.sld. Filter property xpath for lithology looks like this: ogc:PropertyName>gsml:MappedFeature/gsml:specification/gsml:GeologicUnit/gsml:preferredAge/gsml:GeologicEvent/gsml:eventAge/gsml:CGI_TermRange/gsml:lower/gsml:CGI_TermValue/gsml:value Implemented by Agnes in OGE portal. Close.

Issue 23. http://ogcdev.bgs.ac.uk/Testbed4_BGS_625k_Bedrock_v1/ BGS snowflake test page for WFS 2.0 GML 3.2, GeoSciml 3.0.0. Snowflake does not implement 'Addtional objects' to allow bundling of GeologicFeature to specify multiple MappedFeatures or skos vocabulary terms. Discussion indicates that this is not an issue for Eric, Bruce S or Alistair; first occurrence of repeated element is inline, subsequently references as doc fragment in the instance document.

Snowflake only works to Oracle SDO. Go Publisher desktop to configure WFS is slick, easy to use. ESRI Conterra Germany has WFS security layer implementation.

Is there a special query for a feature based on the identifier.

Other Issues have to do with URI resolver and URI encoding. Eric and Allistair have both implemented solutions; both do 303 redirects, Eric's handles content negotiation.

reports from each of the participants on progress and issues

    • report of 1G Europe
    • report of Snowflake implementation.
    • report of instance implementation and preparation of a list of issues for modelling group.
    • report on Schematron validation (CaseStudyRome2010

TUESDAY

Concept Definitions Task Group

see RomeF2FConceptDefinitionsTGMeetingNotes

Service Architecture Task Group

see RomeF2FServiceArchitectureTGMeetingNotes

WEDNESDAY

Service Architecture Task Group continued

see RomeF2FServiceArchitectureTGMeetingNotes

THURSDAY

Model Design Task Group

see RomeF2FModelDesignMeetingNotes
Topic revision: r7 - 19 Apr 2011, MarcusSen
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).