Telco 22. OGC Best Practice

When: WED 9 February 2022 - 15:00-16:00 CET

Where: GoToMeeting https://global.gotomeeting.com/join/321982654

Attendants

Joan Masó and Kaori Otsu / CREAF, Andreas Matheus / Secure Dimensions (SECD), Hylke van der Schaaf / Fraunhofer, Mathias Chouet / INRIA

Agenda

• OGC Members meeting:
  • 122nd Meeting: 28 February - 4 March 2022 (Virtual)
    • Citizen Science DWG session on 28 February at 21:45 CET: OGC Best Practice for using SensorThings API with Citizen Science (presentation and discussion) by Andreas Matheus, Joan Masó
    • SensorThings SWG session TBA
• Progress report on STAplus implementation
  • OGC Best Practices report submission

Minutes

• Recap of Ownership in STA+ data model
  • Personal entities: Party, Thing, Datastream, Observation, Group can be deleted/updated by the linked Party.
  • Global entities: the rest can be created by any Party but cannot be deleted/updated.
• Andreas presented ACTION items for the OGC Best Practices document.
  • CREAF (BP 7.1): Creating (semantically enriched) data from Natusfera – how to demonstrate the interoperability and that you can get “the same” information from STAplus that you get from Natusfera
  • SECD (BP 7.2): STAplus latest and greatest achievements (Face Detection with Obervation Upload, Size and max Frames detection), Running a Camera Trap that uploads to STAplus
  • Fraunhofer (BP 7.3): Leveraging the STA API batch-processing
  • INRIA (BP7.4): Performance “issues” and the use of additional indexing
  • CREAF (BP7.5): Building a Web-Application to visualize STAplus
  • 52N (BP7.6): Modelling community processes (blogging)
  • SECD/INRIA/CREAF (future work): demonstrating the use of Microsoft Excel with OData/STAplus (e.g. Pl@ntNet or Natusfera data to the SECD endpoint)
    • INRIA will try loading millions of Pla@ntNet records from OData/STAplus to evaluate query performances in Excel - also to check any limit to data capacity in Excel
• DISCUSSION: batch-processing initialization and runtime
  • Observation (identification) should link the URI (e.g. GBIF taxonomy) to FeatureOfInterest, using Relation?
    • The role of Relation can be dwc:identificationReferences (http://rs.tdwg.org/dwc/terms/identificationReferences)
      • e.g. Subject = Observation (taxonID5219243), externalObject = FeatureOfInterest (https://www.gbif.org/species/5219243)
  • Can a user change the Datastream-> License?
    • Is it allowed to change a license on a datastream that already has observations?
  • What does it mean if the user sets the Group-> Runtime property?
    • A Group is “open” until the Runtime property defines a period [<start>, <end> = null]
      • “open”: Observations (and Relations) can be added to the Group by any Party
      • “closed”: Modifications to the Group can only be made by the owning Party (each update resets the <endTime>)
  • Does the Group need a closed property (License) to seal a set of observations and how strict should it be?
    • Among multiple parties, when one party deletes the individual account, its observations may stay in Group (as a read-only copy) but the owner information is N/A (anonymous)?
    • When an observation record is added to the Group, the service provider should warn or provide options about making a copy of the record?
      • This may be different from one service provider to another. In any case, how data update/delete is being handled should be made clear to the users.
    • Within the Group (sealed by License), observations shall be accessed (read-only) and used for training a dataset but cannot be updated/deleted?
      • e.g. Pl@ntNet AI service GBIF-DL: how was the license issue handled for loading training images from GBIF database?
    • Overview of the license hierarchy and compatibility

• AOB
  • STA+ data model will remain as it is in the UML diagram. Use cases fit to the STA+ will be presented as BPs.
  • Proposed submission by the end of May towards the 123rd OGC Member Meeting in mid-June 2022