Versions Compared

Old Version 3

changes.mady.by.user Benjamin Balder Bach

Saved on

compared with

New Version Current

changes.mady.by.user Lal Chandran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agenda

Presenter

Discussion

 Update from Tech Committee

 Ain Aaviksoo (Deactivated)

Aug-19 meeting cancelled

Guidelines for API endpoint spec guideline

Lal Chandran Benjamin Balder Bach

  • Suggested guidelines to Max+Taylor (Aug-15 meeting)

    • More discussions needed (eg describe the “problem-to-be solved”

    This will be forwarded to a TAC meeting, perhaps on August 27th. Presentations are updated.

    https://docs.google.com/presentation/d/16-iwfJGq_c-wrRqfBmY1VOnaUIkUhW8_7gOEH9jMoSk/edit#slide=id.g1429778ced4_0_0

    https://docs.google.com/presentation/d/1FrL92sYJx2WcAxc-K99Tonzl2RVFbtTeoULjSgdz9mA/edit?usp=sharing

     

    Jira Legacy
    serverSystem JIRA
    serverIdf5c6bdaf-d23e-347d-a1e8-579e20a81dda
    keyGOV-408

     Update on API development

     Benjamin Balder Bach Lal Chandran

    • Jamboard for commenting

    • Write comments directly in the API spec, notice there is a second sheet with the new endpoint structure.

    https://docs.google.com/spreadsheets/d/1snIszqyTGYk1u25liwQ_1jONTsQeH7D8aqv1Td74xt4/edit#gid=486318441

    https://jamboard.google.com/d/1aGF_B-Y-dpA7-9JkqXmYxMhAvDApSTKk8DKKXBQ0Cxw/viewer

    Planning test scenarios

    @everybody

    AOB

    @everybody

    ...

    •  Reach out to TAC regarding versioning in API base URL Benjamin Balder Bach
    •  Forward 2 proposals for TAC - possible to mention general perspective, that we have to start everything from scratch and that “best-practice” sharing is desirable when a general standard/convention isn’t adopted. Lal ChandranAin Aaviksoo (Deactivated)
    •  All group members will write comments in API spec, Benjamin Balder Bach will take “role” as “author” of the spec and respond to review questions.

    Decision