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.

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

[Registry] How do people know what content-type the messages will be? #1162

Closed
duglin opened this issue Feb 23, 2023 · 3 comments
Closed

[Registry] How do people know what content-type the messages will be? #1162

duglin opened this issue Feb 23, 2023 · 3 comments

Comments

@duglin
Copy link
Collaborator

duglin commented Feb 23, 2023

We have a format property that will tell people that the message is a CloudEvent, but nothing in the Endpoint metadata to indicate whether it'll be xml, json, avro, ... or what the possible formats might be so people could specify that choice on the Subscribe() operation (if it supported it).

We should consider adding something to indicate the content-type(s) of the messages.

@duglin duglin changed the title [Discovery] How do people know what content-type the messages will be? [Registry] How do people know what content-type the messages will be? Feb 23, 2023
@clemensv
Copy link
Contributor

"Content-type" is a message-format specific field that exists in all message format definitions either explicitly or implicitly. There is no hard correlation between the schema format and the media-type/content-type for a message.

What is "vnd.contoso.application/foobar"?

It's an app-level hint.

@github-actions
Copy link

This issue is stale because it has been open for 30 days with no
activity. Mark as fresh by updating e.g., adding the comment /remove-lifecycle stale.

@duglin
Copy link
Collaborator Author

duglin commented Apr 18, 2023

Moved to: xregistry/spec#19

@duglin duglin closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants