GeoSciML GeoScienceDWG join meeting

Toulouse, France November 2019

We are at the point we need to decide what’s next
  • Status report
    • Standing issues
    • Activities
  • New drivers
  • What’s next ?
Small report given during join GeoScienceDWG (no formal GeoSciML meeting)
  • We have standing issues, almost all are minor and were pushed to eventual new version

OGC CR system

Github issues

By email : The latter was briefly discussed during the presentation.

There are other activities, but they don't require at this moment a change to the standard (so, no SWG issued beside encoding or parrallel activities), except for BoreholeIE ( BoreholeIE ER:

  • BoreholeIE
    • Bulk of activity under OGC involving some GeoSciML members
    • RDF/JSON encoding (fall 2018 test, but no follow up)
    • WFS 3 (OGC API)
    • Linked Data
  • LOOP
    • Not OGC activity, but something that can impact future activities
    • OWL modelling
    • 3D
  • OneGeology Linked Data
Now that BoreholeIE is done, need to assess what to do next (if any)

Eric will circulate email and ask community. Quick win would be to push the trivial change, with the understanding of implied consequences (many of the changes do not come from people operating GeoSciML based system). Also probe next action.

Status report on OGC portal :

-- EricBoisvert - 19 Nov 2019
Topic revision: r2 - 21 Nov 2019, EricBoisvert
This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback