Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / cloudevents/spec issues and pull requests
#1174 - [Registry] should we require `epoch` even in non-API cases? (meaning docs)
Issue -
State: closed - Opened by duglin almost 2 years ago
- 3 comments
Labels: lifecycle/stale
#1173 - [Registry] Which resources should require `name`?
Issue -
State: closed - Opened by duglin almost 2 years ago
- 2 comments
Labels: lifecycle/stale
#1172 - [Registry] Should we add "id" to the root of the Registry doc?
Issue -
State: closed - Opened by duglin almost 2 years ago
#1171 - [Registry] Define where registry files live in a git repo
Issue -
State: closed - Opened by duglin almost 2 years ago
- 2 comments
Labels: lifecycle/stale
#1170 - [Registry] property casing discussion
Issue -
State: closed - Opened by duglin almost 2 years ago
- 4 comments
Labels: lifecycle/stale
#1169 - Move batch restrictions from HTTP to the main spec
Pull Request -
State: closed - Opened by jskeet almost 2 years ago
- 3 comments
#1168 - Fix tool - support "maybe" and ignore words that start with backtick
Pull Request -
State: closed - Opened by duglin almost 2 years ago
#1167 - Add more Registry text
Pull Request -
State: closed - Opened by duglin almost 2 years ago
- 1 comment
#1166 - Adding get for singular endpoint
Pull Request -
State: closed - Opened by matzew almost 2 years ago
- 4 comments
#1165 - Pre-check-in scripts issue: Capitalization of keywords used as expressions in spec
Issue -
State: closed - Opened by clemensv almost 2 years ago
- 2 comments
#1164 - Group/Resource/Format Details for Registry
Pull Request -
State: closed - Opened by clemensv almost 2 years ago
- 4 comments
#1163 - [Registry] `format` vs `contenttype`
Issue -
State: closed - Opened by duglin almost 2 years ago
- 4 comments
Labels: lifecycle/stale
#1162 - [Registry] How do people know what content-type the messages will be?
Issue -
State: closed - Opened by duglin almost 2 years ago
- 3 comments
Labels: lifecycle/stale
#1161 - Add schemaformat
Pull Request -
State: closed - Opened by duglin almost 2 years ago
- 1 comment
#1160 - Rename Group to DefinitionGroup
Pull Request -
State: closed - Opened by duglin almost 2 years ago
- 3 comments
#1158 - saver->severe
Pull Request -
State: closed - Opened by duglin almost 2 years ago
- 1 comment
#1157 - Remove old Discovery and SchemaRegistry specs
Pull Request -
State: closed - Opened by duglin almost 2 years ago
- 3 comments
#1156 - Make it clear that datacontenttype MAY appear w/o data
Pull Request -
State: closed - Opened by duglin almost 2 years ago
- 2 comments
#1155 - Warn people about dataref
Pull Request -
State: closed - Opened by duglin almost 2 years ago
- 2 comments
#1154 - Initial attempt at batch clarification
Pull Request -
State: closed - Opened by jskeet almost 2 years ago
- 3 comments
#1153 - Discovery: "schemaformat" next to "schemaurl"
Issue -
State: closed - Opened by clemensv about 2 years ago
- 1 comment
#1150 - Make "batch" less confusing
Issue -
State: closed - Opened by duglin about 2 years ago
#1146 - CloudEvents Connectors Proposal
Issue -
State: closed - Opened by JieDing about 2 years ago
- 15 comments
#1143 - Support CDATA for textual data
Pull Request -
State: closed - Opened by JemDay about 2 years ago
- 11 comments
Labels: needs work
#1136 - Event-data spec when data is too large, so truncated/pruned
Issue -
State: closed - Opened by ratankr39 about 2 years ago
- 5 comments
#1132 - Security Audit - Outdated dependencies
Issue -
State: open - Opened by embano1 about 2 years ago
- 5 comments
Labels: lifecycle/stale
#1132 - Security Audit - Outdated dependencies
Issue -
State: open - Opened by embano1 about 2 years ago
- 5 comments
Labels: lifecycle/stale
#1121 - Subscriptions manager API and Kafka, and event logging producers in general
Issue -
State: open - Opened by jroper about 2 years ago
- 7 comments
Labels: lifecycle/stale
#1114 - JOSE Extension
Issue -
State: closed - Opened by alexec over 2 years ago
- 9 comments
Labels: lifecycle/stale
#1113 - Encryption Extension
Issue -
State: closed - Opened by alexec over 2 years ago
- 6 comments
Labels: lifecycle/stale
#1109 - feat: explicitly state otel mapping in severity extension
Issue -
State: closed - Opened by sasha-tkachev over 2 years ago
- 4 comments
Labels: lifecycle/stale
#1104 - sampledrate extension edge case
Issue -
State: closed - Opened by sasha-tkachev over 2 years ago
- 8 comments
Labels: lifecycle/stale
#1102 - feat: jwt extension
Pull Request -
State: closed - Opened by sasha-tkachev over 2 years ago
- 15 comments
Labels: needs work
#1083 - dataschema for signed or encrypted payload
Issue -
State: closed - Opened by duglin over 2 years ago
- 25 comments
Labels: lifecycle/stale
#1072 - feat: clarify that `datacontenttype` MAY exist without `data`
Issue -
State: closed - Opened by sasha-tkachev over 2 years ago
- 1 comment
Labels: lifecycle/stale
#1066 - [Registry] I wonder if this example is misleading, as it needs the `usage` to be understood. That might tell me that usage and options should be colocated in an object together one level off of the root?
Issue -
State: closed - Opened by duglin over 2 years ago
- 3 comments
Labels: lifecycle/stale
#1065 - [Registry] `usage` seems odd to me. I would call this `role`.
Issue -
State: closed - Opened by duglin over 2 years ago
- 3 comments
Labels: lifecycle/stale
#1064 - [Registry] I would rename to `auth` and define it as an undefined object.
Issue -
State: closed - Opened by duglin over 2 years ago
- 3 comments
Labels: lifecycle/stale
#1063 - [Registry] If we do not define what `channel` means, I would lean towards `channel` being either a documented extension that defines one way to interpret `channel`, or drop it entirely and vendors can add private extensions to the api.
Issue -
State: closed - Opened by duglin over 2 years ago
- 3 comments
Labels: lifecycle/stale
#1062 - [Registry] Feels like `channel` should be an array.
Issue -
State: closed - Opened by duglin over 2 years ago
- 14 comments
#1061 - [Discovery] Would this (/why would this) docsurl be different than the endpoint docsurl?
Issue -
State: closed - Opened by duglin over 2 years ago
- 2 comments
Labels: lifecycle/stale
#1060 - [Registry] if the definition of the same endpoint is modified by two systems, and then both increment the epoch by 1, and then they sync, who wins?
Issue -
State: closed - Opened by duglin over 2 years ago
- 3 comments
Labels: lifecycle/stale
#1059 - [Discovery] I do still wonder if `epoch` will confuse people more than anything. https://en.wikipedia.org/wiki/Epoch_(disambiguation)
Issue -
State: closed - Opened by duglin over 2 years ago
- 2 comments
Labels: lifecycle/stale
#1058 - [Registry] I see a lack of symmetry between `deprecated` and the introduction of the endpoint. I might want a created and updated times?
Issue -
State: closed - Opened by duglin over 2 years ago
- 2 comments
#1052 - Combining with JSON Schema specification for validation?
Issue -
State: open - Opened by devinbost over 2 years ago
- 30 comments
Labels: lifecycle/stale
#1040 - [Subscription API] Purpose of Filter schema object in OAS not clear
Issue -
State: open - Opened by HenriKorver over 2 years ago
- 9 comments
Labels: lifecycle/stale
#1039 - [Subscription API] I get confused by introduction section about filter dialects
Issue -
State: open - Opened by HenriKorver over 2 years ago
- 11 comments
Labels: lifecycle/stale
#1038 - [Subscription API] OAS schema for filter expressions seems not to be correct
Issue -
State: open - Opened by HenriKorver over 2 years ago
- 9 comments
Labels: lifecycle/stale
#1036 - schemaregistry: Inconsistencies between 3. HTTP ("REST") API and 2. Schema Registry Elements
Issue -
State: closed - Opened by nielspardon over 2 years ago
- 4 comments
Labels: lifecycle/stale
#1015 - XSD - Provide concrete XSD that XML Documents can Validated against
Issue -
State: open - Opened by JimWeier-VeteransUnited over 2 years ago
- 7 comments
Labels: lifecycle/stale
#1014 - Named Element 'ExtensionAttributes' of Type any
Issue -
State: open - Opened by duglin over 2 years ago
- 15 comments
Labels: lifecycle/stale
#1013 - Support CDATA as body type for 'data' element
Issue -
State: closed - Opened by duglin over 2 years ago
- 9 comments
#1004 - XML format: do we have a whitespace policy?
Issue -
State: closed - Opened by jskeet almost 3 years ago
- 19 comments
#963 - JSON format spec review (for scope creep, ambiguity etc)
Issue -
State: open - Opened by jskeet almost 3 years ago
- 16 comments
Labels: lifecycle/stale
#951 - [Registry] Support import and sync'ing between Registry Endpoints
Issue -
State: closed - Opened by duglin almost 3 years ago
- 4 comments
Labels: lifecycle/stale
#919 - [CESQL] MUST requirement to support CESQL?
Issue -
State: closed - Opened by deissnerk about 3 years ago
- 5 comments
Labels: lifecycle/stale
#913 - Use of "epoch" to mean "version" in Discovery
Issue -
State: closed - Opened by jskeet about 3 years ago
- 5 comments
Labels: lifecycle/stale
#912 - Clarify usage of Distributed Tracing Extension by OpenTelemetry
Pull Request -
State: closed - Opened by joaopgrassi about 3 years ago
- 31 comments
#890 - Should we target a Kubernetes Resource Model for the Discovery and Subscription APIs?
Issue -
State: closed - Opened by n3wscott over 3 years ago
- 5 comments
#885 - Discovery spec: avoid "all lower case without punctuation"?
Issue -
State: closed - Opened by jskeet over 3 years ago
- 8 comments
#863 - Issues with discovery
Issue -
State: closed - Opened by duglin over 3 years ago
- 5 comments
Labels: lifecycle/stale
#861 - fix(json-format): Clarify data encoding in JSON format with a JSON datacontenttype
Pull Request -
State: closed - Opened by dazuma over 3 years ago
- 5 comments
#848 - Hash/Checksum Attribute
Issue -
State: closed - Opened by jadedfire over 3 years ago
- 6 comments
Labels: security, lifecycle/stale
#844 - Support timestamp and time functions on SQL fliters
Issue -
State: open - Opened by evankanderson over 3 years ago
- 9 comments
Labels: lifecycle/stale
#830 - New feature requirement - Cross-tenant channels
Issue -
State: closed - Opened by clemensv over 3 years ago
- 17 comments
#829 - [Registry] New feature requirements - Announcements
Issue -
State: open - Opened by clemensv over 3 years ago
- 7 comments
Labels: lifecycle/stale
#824 - [Registry] Align naming conventions for Registry and subscription API
Issue -
State: closed - Opened by deissnerk over 3 years ago
- 2 comments
#815 - [CESQL] Better string concatenation
Issue -
State: open - Opened by slinkydeveloper almost 4 years ago
- 7 comments
Labels: lifecycle/stale
#807 - Why does the HTTP binding for batch require the same spec version for all events in the batch?
Issue -
State: open - Opened by jskeet almost 4 years ago
- 5 comments
Labels: v2.0, lifecycle/stale
#704 - [Discovery] should epoch be global
Issue -
State: closed - Opened by duglin over 4 years ago
- 5 comments
#682 - [Registry] Add support for partial name matching
Issue -
State: closed - Opened by duglin over 4 years ago
- 5 comments
#676 - [Registry] Detecting changes in the discovery service
Issue -
State: closed - Opened by clemensv over 4 years ago
- 4 comments
#630 - [Registry] de-normalize our data model?
Issue -
State: closed - Opened by duglin over 4 years ago
- 4 comments
#623 - [Registry] add small example before we dive deep
Issue -
State: closed - Opened by duglin almost 5 years ago
- 2 comments
#575 - Mandatory fields in Avro representation of CloudEvents.
Issue -
State: open - Opened by arvindkasale08 almost 5 years ago
- 14 comments
#565 - Message Producer Signature
Issue -
State: open - Opened by jkozlick about 5 years ago
- 9 comments
Labels: not-required-for-v1.0
#557 - Register application/cloudevents+json per RFC6838
Issue -
State: open - Opened by duglin about 5 years ago
- 1 comment
#435 - AWS Support of CloudEvents
Issue -
State: closed - Opened by timbray over 5 years ago
- 35 comments
Labels: GoingToClose, try-for-v1.0
#382 - Deprecation extension proposal
Pull Request -
State: closed - Opened by Tapppi about 6 years ago
- 16 comments
Labels: needs work, try-for-v1.0
#382 - Deprecation extension proposal
Pull Request -
State: closed - Opened by Tapppi about 6 years ago
- 15 comments
Labels: needs work, try-for-v1.0
#365 - How should we deal with Deprecated events
Issue -
State: closed - Opened by mbernard about 6 years ago
- 11 comments
Labels: needs work, GoingToClose, try-for-v1.0
#365 - How should we deal with Deprecated events
Issue -
State: closed - Opened by mbernard about 6 years ago
- 11 comments
Labels: needs work, GoingToClose, try-for-v1.0
#365 - How should we deal with Deprecated events
Issue -
State: closed - Opened by mbernard about 6 years ago
- 11 comments
Labels: needs work, GoingToClose, try-for-v1.0