-
Notifications
You must be signed in to change notification settings - Fork 13
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
Path case-sensitive #11
Comments
very much so, +1 for uniform appearance in the URLs. It should be a pain in the
neck to always consider case for each path component. Umm...nobody voting for
ALL UPPERCASE? ;-)
-Peter
On 09.04.19 16:00, Stephan Meißl wrote:
According to RFC 3986 the path component is case-sensitive. Do we want to use
the camel-case notation from XML or rather mandate all lower case?
I tend to prefer all lower case as it looks more natural in a URL.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AF0ejgqDDw1xepcFD-rUU7ETNG4miFrIks5vfJ0PgaJpZM4ckk4i>.
--
Dr. Peter Baumann
- Executive Director, rasdaman GmbH Bremen (HRB 26793)
www.rasdaman.com, mail: baumann@rasdaman.com
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
- Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann
mail: p.baumann@jacobs-university.de
tel: +49-421-200-3178, fax: +49-421-200-493178
"A brilliant idea is a job halfdone."
|
Why are we restricting URIs from RFC3986? Why not follow IRIs from RFC3987? we are trying to establish a global standard. Upper and lower case are really only meaningful for some writing systems. There is no distinction in Cyrillic or Chinese for example. If I wanted to access colleagues' weather services at 中国气象网, why should they have to transliterate into a subset of 1960's ASCII? |
I suggest we follow RFC 6570 (URI Templates) since templates are what we are actually defining. I also like the approach taken by 6570 |
Sorry -did not mean to close this issue - hit wrong button while rushing for a bus. |
Sorry, I didn't mean to restrict anything. My question was only regarding the parts of the path we define in the spec, e.g., Parts defined at runtime by a service like IDs are a different topic. Being based on XML in WCS these have to follow the NCName convention. |
Any objection to using lower case in the spec defined path components? Please reopen if there is any. |
According to RFC 3986 the path component is case-sensitive. Do we want to use the camel-case notation from XML or rather mandate all lower case?
I tend to prefer all lower case as it looks more natural in a URL.
The text was updated successfully, but these errors were encountered: