[OASIS Issue Tracker] Updated: (ODATA-321) Use consistent naming for headers

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

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

Michael Pizzo updated ODATA-321:
--------------------------------

    Proposal: 
Rename the following headers:
 DataServiceVersion => OData-Version
 MaxDataServiceVersion => OData-MaxVersion
 MinDataServiceVersion => OData-MinVersion
 DataServiceId => OData-EntityId

  was:
Rename the following headers:
 DataServiceVersion => OData-Version
 MaxDataServiceVersion => OData-MaxVersion
 MinDataServiceVersion => OData-MinVersion
 DataServiceId => OData-EntryId


> Use consistent naming for headers
> ---------------------------------
>
>                 Key: ODATA-321
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-321
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_WD01
>
>
> Where we add odata-specific names within an open http extensibility point (for example, preferences) we generally prefixed the names we define with "OData-".
> For headers we even reserve headers beginning with "OData".  However, the headers in the original contribution did not follow this proposed naming pattern.
> We should prefix all of the headers we define with "OData-".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira