OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-664) Consider supporting parameterless function imports with no parens


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

Michael Pizzo updated ODATA-664:
--------------------------------

    Proposal: For function imports with no parameters the service may support an alternate syntax of omitting the parens. For maximum interoperability, the service must still support calling function imports with the parens.  (was: See summary.

This is unproblematic as the names of all container children must be unique, so there's no collision possible between entity sets, singletons, and functions.)

> Consider supporting parameterless function imports with no parens
> -----------------------------------------------------------------
>
>                 Key: ODATA-664
>                 URL: https://issues.oasis-open.org/browse/ODATA-664
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ABNF Construction Rules, OData URL Conventions
>    Affects Versions: V4.0_OS
>         Environment: Simplified Syntax
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>              Labels: AdoptionBlocker
>             Fix For: V4.01_WD01
>
>
> Currently we require function imports to have open/close parens, even if they have no parameters.
> Services could be more lax in allowing clients to call parameterless function imports with no parens.



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]