This Commonalities release is planned as a basis for the first CAMARA meta-release.
This page should be updated after fixing the scope in https://github.com/camaraproject/Commonalities/issues/175
Proposed topics to be resolved within this release
1. Error responses
Clarifications related to the format of error response and usage of error codes:
- Issue #127 Which error send back when issue with Device Identifier provided by the API Consumer?
- PR #145 Added 501 Not Supported error response
- Issue #128 API Design : UNAUTHENTICATED 401
- Issue #156 Add reference documentation link to error responses
- Issue #157 Adopting RFC 9457 for Error Handling (???)
2. Test definitions
- Issue #158 Enhancement of the Testing Guidelines
3. CAMARA_common.yaml cleanup
- PR #120 Update CAMARA_common.yaml: add Device headers, fix address
- Issue #163 common.yaml unnecessarily list ErrorInfo properties as required
4. Evolved model of event subscription (???)
- Issue #149 Consolidated issue for subscription discussion
- Issue #153 Subscription-Issue1: A common way to manage lifecycle of subscriptions
- Issue #154 Subscription-Issue2: Allow event consumers to subscribe to more than one event types with a single subscription
- Issue #155 Subscription-Issue3: Support filter option for subscriptions
- Issue #163 Subscription-Issue4: Need to change the scope pattern for explicit subscriptions
- Issue #150 Using CloudEvents extension Authcontext for certain event types
- Issue #151 Copy CloudEvents extension Authcontext also for explicit subscriptions
- Issue #140 Add initialEvent management in subscription
5. String formats
- Issue #93 Specify string format whenever possible
- Issue #137 Proposal to add a standard for defining durations for API Design guidelines
6. Release Management issues
Input to API Design Guidelines:
- Add guidance for Info object in apis
- Readiness Checklist step 6 update proposal
- API Versioning - Aggregation
- How to manage version for a API family release
- Remove basePath in servers.url as variable