Telco 24. OGC Best Practice

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

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

Attendants

Kaori Otsu / CREAF, Andreas Matheus / Secure Dimensions (SECD), Henning Bredel / 52°North

Agenda
  • Progress report on OGC Best Practice document
    • relation –> party
      • Need to associate contributions to a user
      • Relation.description = code list vs. free text?
    • Group.purpose –> free text
      • code list too limited for domain related use cases
    • Group closed
      • runTime(TM_Period) requires to set start/end - this is not what we wanted
      • runTime changed to endTime (TM_Instant)
    • Group has group(s)
      • Need for data assembly (== group) which includes data (e.g. observation)
      • implementation specific defined by application (immutable vs. not immutable)
    • Project.runtime
      • runTime split into startTime|endTime
    • Party.displaName
      • name is not always possible
      • what to use for citation (in case of CC-BY)

Minutes

  • Contributions on semantics by Kathi Schleich
    • KS will see if she is able to become part of the Inter Op IE
    • KS has use cases at hand where the Relation entity will be helpful
  • Roadmap:
    • Pending documents until next TC
    • Proposing to SWG for June meeting
    • RfC after TC in June (OAB briefing required: Andreas + Joan)
    • First version for voting expected for September TC
  • Recent changes to the model
    • Relation → Party
      • Adding relations are contributions from a user
    • Group takes a reference to a collection of Groups
      • use case "referenceable data assembly" containing the actual "observation data group"
    • Add StartTime and EndTime and Done properties to Group and Project
      • Period is a closed time interval
      • Need for open interval
      • Done indicates if the entity is sealed or closed
      • Up to the operator if closing (write protection) shall be recursive
      • Group.purpose → free text (no code list definition from the best practice)
      • Party.displayName → make "name" optional
  • First idea of adding an optional party.personalData (JSON_Object) which can be added and deleted depending on the user's consent and application logic
    • we do not model it as an explicit OData entity as it shall not be accessible via API
    • the business model needs to reflect if personal data can be obtained
    • do we want to specify explicit attributes for the standard personal data: "name", "email"?
  • AOB

Connections

GoToMeeting details



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


You can also dial in using your phone.
(For supported devices, tap a one-touch number below to join instantly.)

United States: +1 (909) 259-0010
- One-touch: tel:+19092590010,,321982654#

Access Code: 321-982-654


More phone numbers:
(For supported devices, tap a one-touch number below to join instantly.)

Australia: +61 2 8014 4937
- One-touch: tel:+61280144937,,321982654#

Austria: +43 7 2088 1406
- One-touch: tel:+43720881406,,321982654#

Belgium: +32 28 08 4296
- One-touch: tel:+3228084296,,321982654#

Denmark: +45 69 91 89 33
- One-touch: tel:+4569918933,,321982654#

Finland: +358 942 59 9121
- One-touch: tel:+358942599121,,321982654#

France: +33 182 880 462
- One-touch: tel:+33182880462,,321982654#

Germany: +49 898 7806 6465
- One-touch: tel:+4989878066465,,321982654#

Ireland: +353 14 845 982
- One-touch: tel:+35314845982,,321982654#

Italy: +39 0 247 92 12 41
- One-touch: tel:+390247921241,,321982654#

Netherlands: +31 208 080 384
- One-touch: tel:+31208080384,,321982654#

Norway: +47 21 04 29 12
- One-touch: tel:+4721042912,,321982654#

Spain: +34 911 82 9783
- One-touch: tel:+34911829783,,321982654#

Sweden: +46 852 503 473
- One-touch: tel:+46852503473,,321982654#

Switzerland: +41 225 3314 54
- One-touch: tel:+41225331454,,321982654#

United Kingdom: +44 20 3318 4724
- One-touch: tel:+442033184724,,321982654#
Topic revision: r2 - 23 Mar 2022, KaoriO
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