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

Move upload resource and target resource to Conventions and Definitions #2874

Open
ioggstream opened this issue Aug 28, 2024 · 1 comment · May be fixed by #2929
Open

Move upload resource and target resource to Conventions and Definitions #2874

ioggstream opened this issue Aug 28, 2024 · 1 comment · May be fixed by #2929

Comments

@ioggstream
Copy link
Contributor

ioggstream commented Aug 28, 2024

Question

I suggest to move "upload resource" and "target resource" to "Conventions and Definitions".

While it is OK to refer to the final resource as the "target resource", it may have a slightly different meaning wrt HTTP, thing that's probably worth mentioning in some way.

Note

In other specs we have "Notational Conventions", is there a specific reason for having a different section name?

@Acconut
Copy link
Member

Acconut commented Sep 10, 2024

That's a good point. The document is still a bit sparse on details about the upload resource in general, so a proper definition would be helpful. I will take care of that soon.

In other specs we have "Notational Conventions", is there a specific reason for having a different section name?

So far we kept the name "Conventions and Definitions" from the I-D template (https://github.com/martinthomson/internet-draft-template/blob/main/draft-todo-yourname-protocol.md#conventions-and-definitions), but we can change it to "Notational Conventions", of course.

@martinthomson Do you think the I-D template should be updated to use "Notational Conventions"?

@Acconut Acconut linked a pull request Oct 28, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants