Skip to content
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

Jump to bottom

Specify if event-type can include a namespace prefix #32

Closed
rachelmyers opened this issue Jan 25, 2018 · 0 comments
Closed

Specify if event-type can include a namespace prefix #32

rachelmyers opened this issue Jan 25, 2018 · 0 comments

Comments

@rachelmyers
Copy link
Contributor

Decide and document if the event-type attribute can include a namespace as a prefix.
@sslavic sslavic mentioned this issue Apr 5, 2018
Merged
inlined added a commit to inlined/cloudevents that referenced this issue Apr 10, 2018
@inlined
Soften stance on namespacing to SHOULD.
374dd5f 
Accept wording suggestions.

This closes issue cloudevents#32

Signed-off-by: Thomas Bouldin <inlined@google.com>
inlined added a commit to inlined/cloudevents that referenced this issue Apr 15, 2018
@inlined
Soften stance on namespacing to SHOULD.
929190f 
Accept wording suggestions.

This closes issue cloudevents#32

Signed-off-by: Thomas Bouldin <inlined@google.com>
duglin pushed a commit that referenced this issue Apr 15, 2018
@inlined
Add namespacing to event-type (#137)
a51068f 
* Add namespacing to an event.

This commit has been spliced off of #129

Signed-off-by: Thomas Bouldin <inlined@google.com>

* Update serialization.md to namespace event-type.

Noticed that "namespace" was still in the searialization
docs, even though it was removed from spec.md. Fixed.

Signed-off-by: Thomas Bouldin <inlined@google.com>

* Soften stance on namespacing to SHOULD.

Accept wording suggestions.

This closes issue #32

Signed-off-by: Thomas Bouldin <inlined@google.com>

* Clarify the meaning of the event-type package namespace.

It is explicitly OK for one software organization
to emit event-types of another organizatoin, so
long as they are conforming to the standard set
by the organization in the namespace.

Signed-off-by: Thomas Bouldin <inlined@google.com>
clemensv pushed a commit to clemensv/spec that referenced this issue May 16, 2018
@inlined
Add namespacing to event-type (cloudevents#137)
678a35f 
* Add namespacing to an event.

This commit has been spliced off of cloudevents#129

Signed-off-by: Thomas Bouldin <inlined@google.com>

* Update serialization.md to namespace event-type.

Noticed that "namespace" was still in the searialization
docs, even though it was removed from spec.md. Fixed.

Signed-off-by: Thomas Bouldin <inlined@google.com>

* Soften stance on namespacing to SHOULD.

Accept wording suggestions.

This closes issue cloudevents#32

Signed-off-by: Thomas Bouldin <inlined@google.com>

* Clarify the meaning of the event-type package namespace.

It is explicitly OK for one software organization
to emit event-types of another organizatoin, so
long as they are conforming to the standard set
by the organization in the namespace.

Signed-off-by: Thomas Bouldin <inlined@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rachelmyers