-
Notifications
You must be signed in to change notification settings - Fork 6
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
Trailing-slash policy inconsistency #22
Comments
The href in the controls array is not a primary path is it? Unless that is wrong as well. |
Personally, I believe it is referring to a primary path. (Link didn't work for me, due to GitHub's rendering of underscores. This should work: https://amwa-tv.github.io/nmos-device-connection-management/tags/v1.0.1/docs/3.1._Interoperability_-_NMOS_IS-04.html.)
As noted in AMWA-TV/is-04#87, "in many cases in the documentation, examples include a trailing slash when they should not. These ought to be addressed, and the expectations placed upon clients in processing them clarified." The important part of this is mostly to make clear that clients cannot blindly append sub-paths to a URL which may or may not end in a trailing slash. |
@garethsb-sony , do you think we should address this in the IS-07 project now, or should we start a NMOS-wide discussion on this and then address it across all projects (maybe in NMOS Core)? |
Another example in IS-07 that contradicts the usual guidance: the documentation for "For consistency the |
https://github.com/AMWA-TV/nmos-event-tally/blob/v1.0/docs/6.0.%20Event%20and%20tally%20rest%20api.md#2-nmos-resource
is in direct contradiction with
https://github.com/AMWA-TV/nmos-discovery-registration/blob/v1.2.1/docs/2.0.%20APIs.md#urls-approach-to-trailing-slashes
(See also AMWA-TV/is-04#87, and AMWA-TV/is-05#65.)
The text was updated successfully, but these errors were encountered: