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-494) Define inheritance for enumeration types

    [ https://issues.oasis-open.org/browse/ODATA-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63465#comment-63465 ] 

Michael Pizzo commented on ODATA-494:

We have approved (and applied) ODATA-940 to add an "AllowedValues" term for enumerating the allowed values for a property without the more rigid semantics of an enumeration.  

If we want to define inheritance (which breaks enumeration semantics), we should do it as part of AllowedValues rather than as an extension to enumerations.

> Define inheritance for enumeration types
> ----------------------------------------
>                 Key: ODATA-494
>                 URL: https://issues.oasis-open.org/browse/ODATA-494
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_CS01
>         Environment: Enum Types
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: GoodIdea
>             Fix For: V4.01_WD01
> We currently don't have a way for adding values to an enumeration type. This would be helpful for defining custom vocabularies that extend base vocabularies. 
>  It's sort of inheritance for enumerations, given the fact that some programming languages implement enumerations as classes/objects with members/properties for the enumeration values. 
>  So we could add an attribute "BaseType" or "Extends" for EnumType to add new enumeration values. 

This message was sent by Atlassian JIRA

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