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=62461#comment-62461 ] 

Michael Pizzo commented on ODATA-812:

From meeting on 2016-4-21:

Ralf: Going with an annotation allows keeping the XML schema stable

Ralf: Check with mainstream clients whether they specify odata-maxversion:4.0

Ralf: Mike to check .NET clients

Ralf: Ralf to check Olingo clients

I verified that our open source .NET clients always specify the OData-MaxVersion.  I also would prefer to keep usage semantics (such as omitting namespaces) separate from the model of the structure.

I propose we keep this as an annotation, and make sure that docs are clear that services must not require clients to understand custom annotations, but OData annotations may imply semantics that a client reporting support for that version of the specification would need to understand in order to work correctly with the service.

> 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: Simplified Syntax;[Proposed]
>            Reporter: Michael Pizzo
>            Assignee: 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]