Agenda

Antitrust Policy

• Device definitions

• Error discussions

• YAML handling

Minutes

Topic 1

• Conflicting device definitions.

• All errors should be moved to examples under its Generic* definition?

• NetworkNotRemovable400 - Optional error for devices that must always have a primary network.

  • 405?

    • The requested method is not allowed/supported on the target resource.

    • May not fit, appears more global to the resource instead of instance of a resource. Thoughts?

  • 409?

    • Specific conflict situation that is relevant in the context of the API.

    • Seems more instance appropriate. Thoughts?

• DefaultDeviceNotSupported403 - When the device cannot be inferred.

  • GENERIC_422_UNIDENTIFIABLE_DEVICE - Seems most aligned with CAMARA in how they handle the mobile-focused device identifier.

• 501 - Any prior art for handling when a large portion of the API doesn’t need to be implemented? Short-term rental vs Value-Added Reseller.

• Any prior art for splitting/combining YAML to be more manageable using includes?

• Dynamic errors allowed and not just static.

Action items

•  Christopher Aubut merge common and our definition in NAM. Create issue with commonalities (not PR, link to NAM).
•  Christopher Aubut yes, move all specific errors under generic as example
•  Christopher Aubut 409 for not removable
•  Christopher Aubut 422 default device
•  Christopher Aubut 501s - Look at splitting short-term / vars use cases into endpoints. Look at QoD.
•  Christopher Aubut Randy Levensalor check with commonalities about tooling. jinja
•  Christopher Aubut Look at QoD for dynamic error messages.