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] Commented: (ODATA-321) Use consistent naming for headers

    [ http://tools.oasis-open.org/issues/browse/ODATA-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32881#action_32881 ] 

Ralf Handl commented on ODATA-321:

I propose DataServiceId => OData-EntityId as we consistently switched from "entry" to "entity" and use "entry" only within the Atom format document when refering to atom:entry elements.

> 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


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