[OASIS Issue Tracker] (ODATA-1144) Allow percent-encoded colon in time values in URLs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68974#comment-68974 ] 

Evan Ireland commented on ODATA-1144:
-------------------------------------

Another observation: when clients use odata.metadata=minimal, the server normally need not return readLink etc (if it uses canonical URLs). If a client creates a read link (canonically, for use in a subsequent GET/PUT/PATCH/DELETE request) it should be permissible for it to use percent-encoding (in case the client needs the URL to pass through a fussy URI/HTTP layer). Therefore the server needs to accept the URL-encoded time values in key predicates, to ensure end-to-end interoperability.

If we allow it to be optional for servers to accept percent-encoded time values in key predicates, that might limit interoperability with clients. However it clearly needs to be optional for 4.0 (even if we publish an errata for 4.0), since existing servers might not support it.

So we can have a good story for 4.01, not so good for 4.0.

> Allow percent-encoded colon in time values in URLs
> --------------------------------------------------
>
>                 Key: ODATA-1144
>                 URL: https://issues.oasis-open.org/browse/ODATA-1144
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: ABNF Construction Rules
>    Affects Versions: V4.01_CS01, V4.0_ERRATA03
>         Environment: Proposed
>            Reporter: Ralf Handl
>             Fix For: V4.01_CS02, V4.0_ERRATA04
>
>
> The ABNF currently does not allow percent-encoded colons in URLs.
> This is an unnecessary restriction and collides with the habit of many URL libraries to over-eagerly percent-encode everything except ALPHA and DIGIT.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)