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

Don't redefine terminology #45

Closed
WhyNotHugo opened this issue Oct 15, 2024 · 1 comment
Closed

Don't redefine terminology #45

WhyNotHugo opened this issue Oct 15, 2024 · 1 comment
Assignees

Comments

@WhyNotHugo
Copy link

The Terminology section defines a few terms which are already defined in RFC8030 (the specification for HTTP Web Push): https://datatracker.ietf.org/doc/html/rfc8030#section-1.1

For example, RFC8030 reads:

push message: A message sent from an application server to a user
agent via a push service.

And the current draft defines the same concept in other words:

Push message Actual network message that is sent from the server
over a push transport to the client. Notifies the client that a
specific collection (identified by its push topic) has changed.

Instead, the draft should re-use existing terminology:

This specification reuses much of the same terminology as RFC8030

@rfc2822
Copy link
Member

rfc2822 commented Dec 15, 2024

Since Web Push is only a (although the only at the moment) transport, I think we need to do that

@rfc2822 rfc2822 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 15, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in DAVx⁵ Releases Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants