Skip to content

Support for commonalities 0.6.0 #88

@stroncoso-quobis

Description

@stroncoso-quobis

Problem description
Current definition is ready for commonalities 0.5.0

Expected behavior
Commonalities 0.6.0 must be complied

Alternative solution
Review and identify actions to do following the public summary table:

  • This PR removes the 401 AUTHENTICATION_REQUIRED code from the Commonalities documentation
  • API sub-projects are free to decide to allow more than one event type per subscription. Use SubscriptionEventType schema in SubscriptionRequest types attribute
  • the API provider must not respond with an error if the identifiers do not match, but instead use only one of the supplied identifiers and indicate which one in the API response. Changes in test definitions.
  • Check for Mandatory text proposed for responses
  • Check Mandatory text proposed when duration string format is used
  • Update x-correlator pattern and Added schema XCorrelator and respective test
  • Reveiw subscription notification naming: subscription-ended, subscription-started, subscription-updated
  • Added sink pattern and specific 400 - INVALID_SINK error

Finally: API-Readiness-Checklist must be reviewed.

Additional context

Full detail and links at WIKI: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/132218881/Analysis+of+Commonalities+0.6.0-rc.1+changes#Analysis

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions