[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-813) Allow no metadata for non-OData clients
[ https://issues.oasis-open.org/browse/ODATA-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-813: ----------------------------- Proposal: If a client sends an Accept header requesting JSON with a specific odata.metadata level, the service responds with that level. If a client sends an OData-specific header (e.g. OData-Version or OData-MaxVersion), or an Accept header with application/json and an OData-specific format parameter, but no specific odata.metadata level, the service responds with odata.metadata=minimal. If a client does not send any OData-specific headers or format parameters, the service may respond with any format matching the Accept header, e.g. for application/json any JSON dialect, including OData JSON of the odata.metadata level preferred by that service. was: If a client sends an Accept header requesting JSON with a specific odata.metadata level, the service responds with that level. If a client sends an OData-Version or OData-MaxVersion header, or an Accept header with an OData-specific format parameter, but no specific odata.metadata level, the servcie responds with odata.metadata=minimal. If a client does not send any OData-specific headers of format parameters, the service may respond with any JSON dialect, including OData JSON of the odata.metadata level preferred by that service, e.g. none. > Allow no metadata for non-OData clients > --------------------------------------- > > Key: ODATA-813 > URL: https://issues.oasis-open.org/browse/ODATA-813 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData JSON Format > Affects Versions: V4.0_ERRATA02 > Environment: Proposed > Reporter: Michael Pizzo > Labels: AdoptionBlocker > Fix For: V4.01_WD01 > > > We want simple rest services to support OData for interoperability without taxing them for non-interoperability requirements. > The easiest way to do this is to allow no-metadata for non-odata clients. > We can determine if the client is odata by: > -Odata.maxversion header > -Odata.version header > -Odata media type parameters -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]