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] (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:

    Environment: Applied

> 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: Applied
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: V4.01_CS01
> 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

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