CloudEvents Specification
Switch branches/tags
Nothing to show
Clone or download
duglin Merge pull request #339 from JemDay/attribute-consistency
Simplified/Reduced context property names.
Latest commit 8579f97 Nov 8, 2018
Permalink
Failed to load latest commit information.
artwork replace logos with readme file Sep 10, 2018
community Issue #323 Nov 8, 2018
extensions Fix bad hrefs due to w3c move Oct 31, 2018
share Minor tweaks to our governance docs (#309) Sep 20, 2018
tools fix issue with filenames starting with http May 29, 2018
.gitignore add artwork (#297) Aug 30, 2018
.travis.yml add ref to RFC2119 and href checker Jan 7, 2018
CONTRIBUTING.md Fix some syntax issues Feb 22, 2018
GOVERNANCE.md Merge pull request #310 from duglin/issue271 Nov 1, 2018
LICENSE Adding Copyright date and owners (#113) Mar 14, 2018
Makefile Add protobuf format (#295) Nov 8, 2018
OWNERS Make OWNERS point to the spreadsheet for our list of 'approvers' Sep 21, 2018
README.md Update README.md Nov 8, 2018
amqp-format.md adding Integer support (#345) Nov 8, 2018
amqp-transport-binding.md Issue #323 Nov 8, 2018
cloudevent.proto Add protobuf format (#295) Nov 8, 2018
documented-extensions.md Rename URI to URI-reference, fix JSON Schema Nov 2, 2018
http-transport-binding.md Issue #323 Nov 8, 2018
http-webhook.md Fix some simple typos in docs Jun 7, 2018
json-format.md Issue #323 Nov 8, 2018
mqtt-transport-binding.md Issue #323 Nov 8, 2018
nats-transport-binding.md Issue #323 Nov 8, 2018
primer.md Minor tweaks to our governance docs (#309) Sep 20, 2018
protobuf-format.md Add protobuf format (#295) Nov 8, 2018
roadmap.md Issue #323 Nov 8, 2018
source-event-action.png First pass at a primer Jun 29, 2018
spec.json Issue #323 Nov 8, 2018
spec.md Issue #323 Nov 8, 2018

README.md

CloudEvents

CloudEvents logo

Events are everywhere. However, event producers tend to describe events differently.

The lack of a common way of describing events means developers must constantly re-learn how to consume events. This also limits the potential for libraries, tooling and infrastructure to aide the delivery of event data across environments, like SDKs, event routers or tracing systems. The portability and productivity we can achieve from event data is hindered overall.

CloudEvents is a specification for describing event data in common formats to provide interoperability across services, platforms and systems.

CloudEvents has received a large amount of industry interest, ranging from major cloud providers to popular SaaS companies. CloudEvents is hosted by the Cloud Native Computing Foundation (CNCF) and was approved as a Cloud Native sandbox level project on May 15, 2018.

CloudEvents Documents

The following documents are available:

Latest Release Working Draft
Core Specification:
CloudEvents v0.1 master
Optional Specifications:
HTTP Transport Binding v0.1 master
JSON Event Format v0.1 master
Web hook - master
MQTT Transport Binding - master
NATS Transport Binding - master
AMQP Event Format - master
AMQP Transport Binding - master
Additional Documentation:
Primer - master
Documented Extensions master

If you are new to CloudEvents, it is recommended that you start by reading the Primer for an overview of the specification's goals and design decisions, and then move on to the core specification.

Community

Learn more about the people and organizations who are creating a dynamic cloud native ecosystem by making our systems interoperable with CloudEvents.

  • Contributors: people and organizations who helped us get started or are actively working on the CloudEvents specification.
  • Coming soon: demos & open source -- if you have something to share about your use of CloudEvents, please submit a PR!

Process

The CloudEvents project is working to formalize the specification based on design goals which focus on interoperability between systems which generate and respond to events.

In order to achieve these goals, the project must describe:

  • Common attributes of an event that facilitate interoperability
  • One or more common architectures that are in active use today or planned to be built by its members
  • How events are transported from producer to consumer via at least one protocol
  • Identify and resolve whatever else is needed for interoperability

Communications

The mailing list for e-mail communications:

And a #cloudevents Slack channel under CNCF's Slack workspace.

Meeting Time

See the CNCF public events calendar. This specification is being developed by the CNCF Serverless Working Group. This working group meets every Thursday at 9AM PT (USA Pacific):

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/cncfserverlesswg

Or iPhone one-tap :

US: +16465588656,,3361029682#  or +16699006833,,3361029682#

Or Telephone:

Dial:
    US: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)
    or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)

Meeting ID: 336 102 9682

International numbers available: https://zoom.us/zoomconference?m=QpOqQYfTzY_Gbj9_8jPtsplp1pnVUKDr

NOTE: Please use *6 to mute/un-mute your phone during the call.

World Time Zone Converter: http://www.thetimezoneconverter.com/?t=9:00%20am&tz=San%20Francisco&

In Person Meetings

There is a face-to-face meeting planned for June 15, 2018 in San Francisco. Please see the first page of the minutes document for more information.

Meeting Minutes

The minutes from our calls are available here.

Recording from our calls are available here.