Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Community Attendees:

Christopher Aubut

Community Attendees:

LF Staff:

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?

Action items

  • No labels