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

are naming in APIs a problem IETF should solve #31

Open
masinter opened this issue Dec 28, 2014 · 0 comments
Open

are naming in APIs a problem IETF should solve #31

masinter opened this issue Dec 28, 2014 · 0 comments
Labels
IETF

Comments

@masinter
Copy link
Contributor

from http://www.ietf.org/mail-archive/web/apps-discuss/current/msg13507.html

"differences among APIs for manipulating resource identifiers. I do not think that is a problem and does not need solving"

This may not be a problem to solve in the URL standard, or in the 3986/3987 replacement. Partly because APIs come and go, and have multiple purposes, and different interoperability and naming requirements (translated to other languages?).

At least noting the question should be in the problem statement draft
@rubys rubys added the IETF label Dec 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
IETF
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rubys @masinter