[OASIS Issue Tracker] Commented: (ODATA-128) Restrict scheme in OData URIs to http and https

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31262#action_31262 ] 

Stefan Drees commented on ODATA-128:
------------------------------------

I second this proposal. 

Rationale: As articulated by Ralf in the description.

Additional note:
We may  amend it "later" with "odata.beep" and "odata.beeps" (OData over BEEP over TCP) starting with version 5.0 and if we have clients and servers 
exchanging messages based on [BEEP](http://tools.ietf.org/html/rfc3080). 
Since the existing communication partners as of now only use http(s), there will be no validating trap, in disallowing it in version 4.0.



> Restrict scheme in OData URIs to http and https
> -----------------------------------------------
>
>                 Key: ODATA-128
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-128
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules v1.0
>    Affects Versions: WD01
>         Environment: [proposed]
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: WD01
>
>
> We're always referring to HTTP, but allow all sorts of schemes in the odataUri ABNF rule. Do we really want to allow service roots to start with mailto: or file:?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira