[OASIS Issue Tracker] (ODATA-937) Consider making odata- prefix optional in headers, preference values, format parameters

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

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

Michael Pizzo edited comment on ODATA-937 at 7/6/16 1:19 AM:
-------------------------------------------------------------

Applied to [Protocol] and [ABNF].

Note proposed handling of EntityId in response header:

Note: The EntityId header was named OData-EntityId in OData version 4.0. Services MUST return the OData-EntityId header for responses that have an OData.Version response header of 4.0 and the EntityId header for response with an OData.Version header of 4.01 or greater, and MAY return both EntityId and OData-EntityId headers in the same response.


was (Author: mikep):
Note proposed handling of EntityId in response header:

Note: The EntityId header was named OData-EntityId in OData version 4.0. Services MUST return the OData-EntityId header for responses that have an OData.Version response header of 4.0 and the EntityId header for response with an OData.Version header of 4.01 or greater, and MAY return both EntityId and OData-EntityId headers in the same response.

> Consider making odata- prefix optional in headers, preference values, format parameters
> ---------------------------------------------------------------------------------------
>
>                 Key: ODATA-937
>                 URL: https://issues.oasis-open.org/browse/ODATA-937
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA03
>         Environment: [Propose]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> We defined our own namespacing mechanism for things like preferences and headers by prefixing with odata.  Specifically:
> OData Headers:
> OData-Version
> OData-MaxVersion
> OData-Isolation
> OData-EntityId
> OData-SchemaVersion
> OData Preferences:
> odata.allow-entityreferences
> odata.callback
> odata.continue-on-error
> odata.include-annotations
> odata.maxpagesize
> odata.track-changes
> odata.omit-values
> OData format parameters:
> odata.metadata
> odata.streaming
> In the interest of making some of these conventions and behaviors more broadly adopted, should we consider supporting some of them without the "odata" prefix?



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