Skip to content

Minutes

Jump to bottom
Stephan Meißl edited this page Jun 12, 2019 · 25 revisions

Minutes of various meetings

Teleconference 20190612

Agenda

Attendees

Chuck, Eugene, James, Joan, Stephan

Minutes

  • Discussion about using SwaggerHub like for Map Tiles -> recommendation from API Common (cf. section 6)
  • Fabian from EOX has started for coverages at https://app.swaggerhub.com/apis/constantinius/ogc-api-coverages/1.0.0
  • Stephan informs that there are resources reserved on the Azure cloud provided by ordnance survey for the WCS SWG
  • Agreed to leave teleconference next week scheduled in case it is needed but likely it will be canceled as most of us will be traveling

Actions

  • Chuck: Build GitHub project following the example of API Common
  • Stephan: Add tags to GitHub issues (e.g. Hackathon) and organize in the project built by Chuck following the example of API Common
  • Stephan: Prepare slides about open points for discussion with API Common at the hackathon
  • All: Prepare and get ready for the hackathon next week

Recording

GoToMeeting

Teleconference 20190529

Agenda

Attendees

Amy, Chris, Chuck, Eugene, Gobe, Stephan

Minutes

  • How do we define success for the Hackathon? The groups common understanding of the main objectives is to get consensus that OpenAPI is the right way to go for the next generation of OGC standards and to factor out commonalities in OGC API Common which all groups agree to use.
  • Gobe: Key points are
    • OpenAPI
    • in line with WFS 3
    • make specs consistent
    • Hackathon focus on testable and implementable
  • Chuck: Regarding scope, currently OpenAPI is the only definition language we're using but there might be others in future
  • Gobe: The agenda does not focus on Common, it has both splitting into teams (resource specific) as well as common
    • boundary between common and resource specific
    • what should be optional in common
  • Chuck: common defines mechanisms that can be used if needed but don't have to be used
  • Additionally the idea was brought forward to have a break-out session to harmonize by looking at overlaps and commonalities between building blocks, i.e., coverages, features, and common.
    • The agenda is flexible and up to the SWG chairs to coordinate and organize ad-hoc sessions
    • 2 times 10 people in board room; event space 50 people sitting at desks; social space/kitchen with probably 4 tables
      • possible configurations
        • 10, 10, 25, 25
        • 10, 10, 50
        • 20, 25, 25
  • Gobe: Please fill in form if you need space on provided infrastructure https://docs.google.com/forms/d/1HH_Lbnx797yGWWn5xBcCrVF0sWbcqbsn5fsYtYwGsO8

Actions

  • Stephan: Fill in form for resources on behalf of the WCS SWG
  • All: Review and contribute issues and requirements

Recording

GoToMeeting

Teleconference 20190522

Agenda

Attendees

Amy, Chris, Michael, Eugene, Paul, Peter, Stephan

Minutes

  • Chris informs that the Met-Office is going to be at the hackathon and will provide/bring multidimensional data and service
  • Known participants are
    • Met-Office
    • National Weather Service
    • Ordnance survey
    • OpenEO
    • Sinergise
    • Jacobs University/rasdaman
    • EOX
  • There is space for a maximum of 70 participants and twice as much are on the waiting list
  • Chris raises the question how success is defined for the hackathon.

    • Michael emphasized to define a mission like Chris Holmes did for WFS and STAC.

    • Chris: Indication if WFS 3 is going the right direction. Build suite of APIs that are consistent. Met-Ocean hackathon in December in Washington based on WFS. Coverages are only for GeoSpatial experts.

    • Stephan: This is a first hackathon in a series with focus on Common. Personal objective to make it way easier for client implementers.

    • Chris: UK Gov OpenAPI initiative API guidance is that they all should be based on OpenAPI 3.0 - https://github.com/alphagov/open-standards/issues/31#issuecomment-493437352

    • The groups common understanding of the main objectives is to get consensus that OpenAPI is the right way to go for the next generation of OGC standards and to factor out commonalities in OGC API Common which all groups agree to use.

  • Michael introduces his view on OGC Next Generation APIs. He will put the diagram on GitHub.
  • Peter suggests a break-out session to harmonize by looking at overlap, commonalities between building blocks, i.e., coverages, features, and common.

Actions

  • Stephan: Send mail to Gobe to ask about objectives and invite to next week's meeting
  • Michael: Put shown diagram on GitHub
  • All: Review and contribute issues and requirements

Recording

GoToMeeting

Teleconference 20190508

Agenda

Attendees

Chuck, Eugene, Jürgen, Peter, Stephan S.

Minutes

  • We only had a brief general discussion mainly about API Common and usage of IDs

Actions

  • Chuck: Check definition for IDs #19. Do we break OpenAPI when using IRIs as defined in RFC3987?
  • All: Review and contribute issues and requirements

Recording

GoToMeeting

Teleconference 20190503

Agenda

Attendees

Chuck, Eugene, Joan, Peter, Stephan S., Stephan M.

Minutes

  • Weekly meeting time slot moved to Wednesday 10am EDT / 4pm CEST
  • Stephan introduces new wiki page capturing minutes
  • We reviewed some issues and try to close them
    • #20 - Agreed on steps to resolve
    • #19 - Deferred to API Common
    • #18 - Closed as part of #20
    • #17 - Might be inherited from API Common
    • #16 - Agreed to support both methods (bbox, subset) in filtering on collection level but only use subset mechanism on coverage level

Actions

  • All: Review and contribute issues and requirements

Recording

GoToMeeting

Teleconference 20190426

Agenda

Attendees

Amy, Chuck, Eugene, Paul, Peter, Stephan

Minutes

  • Chuck presents changes made to the GitHub repository
    • got rid of distracting stuff, e.g. removed OAPI-Common directory
    • requirements directory
      • is the only normative part
      • they are included in clause 7
    • examples directory
      • are important to see how the requirements are actually implemented
      • again included in clause 7
    • for the hackathon clause 7 is the most important one
    • anything not specific to coverages should probably be in common
      • don't waste time on it
      • tie back to common via requirements class
    • everything needed for functional complete implementation should go in core, everything else in extensions
    • pattern for extensions
      • top level directory for each along OAPI-Coverages
    • naming convention will be in mail from Clemens soon, following ISO nomenclature
    • focus on getting requirements written
  • Stephan introduces new wiki page capturing decisions
  • We review some issues and try to close them

Actions

  • Chuck: Write some notes about structure and next steps up in the wiki
  • All: Review and contribute issues and requirements

Recording

GoToMeeting

Clone this wiki locally