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-812) Allow omitting namespaces for unambiguous functions/actions

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

Steven Legg commented on ODATA-812:

Alternatively, apply a term to an entity type or complex type to indicate the (qualified) names of functions that can be used without the namespace. Another effect of the term would be to disallow additional properties or dynamic properties with the same names in the type or its derived types (i.e., to reserve a name as though there actually was a property with that name). External documents would not be a problem because the type owner would be controlling what added functions could be used without a namespace.

There is a potential for a collision between a property added to a base type and a function name reserved by a derived type, but that's no different from a property to property name collision.

The prohibition on a property and a function having the same name could be relaxed in circumstances where ambiguity isn't a problem, say if the type and function are in the same namespace and the term is applied to the same type that defines the property and the function parameters can't be confused with a key predicate.

> Allow omitting namespaces for unambiguous functions/actions
> -----------------------------------------------------------
>                 Key: ODATA-812
>                 URL: https://issues.oasis-open.org/browse/ODATA-812
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>              Labels: AdoptionBlocker
>             Fix For: V4.01_WD01
> I hear a lot of pushback on having to qualify functions/actions when invoking.
> We can support unqualified function/actions as long as they don't conflict with any properties.

This message was sent by Atlassian JIRA

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