Skip to content

Add namespacing to event-type #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
duglin merged 4 commits into from
Apr 15, 2018
Merged

Add namespacing to event-type #137

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
81d5e7a
Add namespacing to an event.
inlined Apr 2, 2018
546c93e
Update serialization.md to namespace event-type.
inlined Apr 2, 2018
929190f
Soften stance on namespacing to SHOULD.
inlined Apr 10, 2018
5606a11
Clarify the meaning of the event-type package namespace.
inlined Apr 12, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion serialization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ Example:
"cloudEventsVersion": "0.1",
"eventID": "6480da1a-5028-4301-acc3-fbae628207b3",
"source": "http://example.com/repomanager",
"eventType": "created",
"eventType": "com.example.repro.create",
"eventTypeVersion": "v1.5",
"eventTime": "2018-04-01T23:12:34Z",
"schemaURL": "https://product.example.com/schema/repo-create",
Expand Down
15 changes: 8 additions & 7 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,14 +264,15 @@ that contains both context and data).

### eventType
* Type: String
* Description: Type of the event `data`. Producers can specify the format of
this, depending on their service. This enables the interpretation of `data`,
and can be used for routing, policy and more.
* Description: Type of occurrence which has happened. Often this
property is used for routing, observability, policy enforcement, etc.
* Constraints:
* REQUIRED
* MUST be a non-empty string
* Examples:
* customer.created
* REQUIRED
* MUST be a non-empty string
* SHOULD be prefixed with a reverse-DNS name. The prefixed domain dictates
the organization which defines the semantics of this event type.
* Examples
* com.github.pull.create

### eventTypeVersion
* Type: String
Expand Down