[OASIS Issue Tracker] Updated: (ODATA-496) Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Drees updated ODATA-496:
-------------------------------

    Resolution: 
https://www.oasis-open.org/committees/download.php/50769/odata-v4.0-wd04-part1-protocol-2013-09-20.docx

Applied: https://www.oasis-open.org/committees/download.php/50877/odata-meeting-54_on-20131001-minutes.html#ga_01


  was:https://www.oasis-open.org/committees/download.php/50769/odata-v4.0-wd04-part1-protocol-2013-09-20.docx


> Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3
> ---------------------------------------------------------------------------------------------
>
>                 Key: ODATA-496
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-496
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Applied]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD03
>
>
> The latest change to the overload resolution strategy (type of binding parameter, set of names of non-binding parameters) didn't make it into the corresponding sections 11.5.3.2 and 11.5.4.2.
> Also the Part 1 text still uses the former term "bindable overload" instead of "bound overload".

-- 
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