Table of Contents

Date

28 Sep 2017

Agenda

New action items

Standing action items

• Capture API use cases relevant to your organization
• Identify high-priority use cases in Confluence or to Former user (Deleted)
• Tell Former user (Deleted) about API errors & exceptions that need work
• Define Standard Test Cases for API clients

Actions items from previous meetings

Language Bindings

• Former user (Deleted)/anyone: add to Standard Test Cases: attachments (plus hash validation), PresentationML validity, tag limit validation(?)
• Former user (Deleted)Former user (Deleted): set API client maintainers up with early access to new API versions for testing

Use Cases

• Former user (Deleted): review API use cases with LLC team before the next meeting to determine/document whether they're supported by the existing API.

REST API Best Practices

• Dan Nathanson (Deactivated) / Former user (Deleted) / Matt Joyce (Deactivated): if there is any change in how attachments work, update the RESTful API Design Guidelines to reflect the recommended practice
• All: add your comments and questions to the RESTful API Design Guidelines
•  

Attendees

Meeting notes