Issues
- 0
Test Issue
#136 opened by OIDF-automation - 0
- 2
Markdown source cleanup
#91 opened by timcappalli - 5
- 3
Config Parameters for Receiver Streams
#116 opened by independentid - 1
Spec / Protocol versioning
#124 opened by tulshi - 0
- 2
- 0
- 0
- 5
stream_id as a path parameter instead of a query parameter in event stream management endpoints
#105 opened by ysarig1 - 4
- 9
Authorization server metadata uses `scopes_supported` key vs SSF using `supported_scopes`
#95 opened by appsdesh - 0
`description` field in the stream configuration to identify the stream on the transmitter
#102 opened by appsdesh - 1
Should some event types be delivered by default regardless of whether they were requested?
#119 opened by FragLegs - 9
- 2
- 3
What happens when a paused stream is polled?
#51 opened by tulshi - 0
We should include "format" in at least one of the stream configuration examples
#54 opened by FragLegs - 0
Should we allow `events_requested` to be empty?
#99 opened by appsdesh - 2
- 2
Clarify event retention in section 7.1.2.1
#106 opened by ysarig1 - 0
7.1.2.2 Update Stream Status (inconsistent use of HTTP POST for modify vs. create)
#113 opened by independentid - 0
"supported_scopes": Meaning of multi scopes and switching from endpoints to logical names
#118 opened by independentid - 2
Is there enough difference between PATCH (7.1.1.3) and PUT (7.1.1.4) for Stream Config
#111 opened by independentid - 2
7.1.1.3 PATCH and 7.1.1.4 PUT Switch Transmitter-Supplied Properties to SSF server-supplied properties
#112 opened by independentid - 0
A way to register new event types
#115 opened by FragLegs - 0
Enhancement: StreamConfig Reset Parameters
#114 opened by independentid - 3
- 0
How should event identifiers be versioned?
#98 opened by timcappalli - 0
Explore using URNs for event identifiers
#97 opened by timcappalli - 0
The SSF Spec should define standard scopes and authorization servers in the Transmitter Configuration Metadata
#74 opened by tulshi - 3
How should overlapping subjects be handled?
#64 opened by FragLegs - 2
Breaking change introduced in the latest draft - `endpoint_url` is renamed to `url`
#79 opened by appsdesh - 2
- 2
Stream Status and Error Diagnosis
#77 opened by independentid - 1
Simple & Complex Subject Identifiers: why not use "aliases" construct defined in secevents draft spec?
#85 opened by scvenema - 3
- 2
Stream create/update for the PUSH method to allow defining token for the receivers endpoint
#75 opened by appsdesh - 5
Are subjects required in SSF events?
#60 opened by FragLegs - 0
ComplexSubject should have a format field
#53 opened by FragLegs - 3
Remove stream configuration API to respond back with with HTTP 204 - No Content instead of HTTP 200
#67 opened by appsdesh - 2
- 1
jwt-id should be jwt_id
#62 opened by FragLegs - 3
Before a Receiver creates a stream, there is no way for it to discover which events a Transmitter supports for it
#45 opened by tulshi - 0
Registration of well-known endpoint to IANA
#66 opened by appsdesh - 5
If a transmitter supports CAEP events, should the delivery method be CAEP specific?
#65 opened by appsdesh - 1
Asas
#61 opened by senjataykoseng - 0
What is the semantic difference between PUT and PATCH in stream management?
#59 opened by independentid - 1
Can 'jwks_uri' be changed to an OPTIONAL field in the Transmitter Configuration Metadata?
#44 opened by tulshi