Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-1095) Allow empty edm:Schema elements

From
OASIS Issues Tracker <>
Date
2017-11-06T13:24:57+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-1095) Allow empty edm:Schema elements
[ https://issues.oasis-open.org/browse/ODATA-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-1095:
------------------------------

    Fix Version/s: V4.01_CSD03
                       (was: V4.01_CS01)

> Allow empty edm:Schema elements
> -------------------------------
>
>                 Key: ODATA-1095
>                 URL: https://issues.oasis-open.org/browse/ODATA-1095
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: CSDL JSON , CSDL XML
>    Affects Versions: V4.01_CSD02
>         Environment:  
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>            Priority: Minor
>             Fix For: V4.01_CSD03
>
>
> The current XML Schema for the EDM namespaces requires the edm:Schema element to contain at least one child element.
> This is problematic in at least two use cases:
> * OData API Designer tools - when starting with a "blank page"
> * Services that "shrink" the schema to match user authorization - when the current user isn't allowed to see anything
> Both require workarounds, e.g. having a dummy annotation in the schema telling that "this schema is intentionally empty".



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →