[OASIS Issue Tracker] (ODATA-1365) Enhance Validation.AllowedValue to have optional Name property

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

Evan Ireland created ODATA-1365:
-----------------------------------

             Summary: Enhance Validation.AllowedValue to have optional Name property
                 Key: ODATA-1365
                 URL: https://issues.oasis-open.org/browse/ODATA-1365
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
    Affects Versions: V4.0_OS
            Reporter: Evan Ireland


In some cases EnumType is undesirable because adding member(s) constitutes a backwards-incompatible change.

If Validation.AllowedValue had an optional Name property (Type="Edm.String" Nullable="true") then Validation.AllowedValues could be used to define "better enums" (including String-valued enums) that would allow graceful evolution of services without backwards-incompatible changes.

To consider (possibly should be spun off to another JIRA issue): how to mark an AllowedValues to indicate that it provides the equivalent of a Flags-style EnumType.




--
This message was sent by Atlassian Jira
(v8.3.3#803004)