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

Michael Pizzo commented on ODATA-937:
-------------------------------------

I propose we modify the proposal for ODATA-937 by not adding the OData prefix to new headers, preferences, and format parameters added in 4.01 and beyond that have a generic meaning (in particular, omit-values and SchemaVersion).

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