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-1067) Consider ability to define computed default values

     [ https://issues.oasis-open.org/browse/ODATA-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-1067:

    Fix Version/s:     (was: V4.01_CS02)
                       (was: V4.0_ERRATA04)

> Consider ability to define computed default values
> --------------------------------------------------
>                 Key: ODATA-1067
>                 URL: https://issues.oasis-open.org/browse/ODATA-1067
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: CSDL JSON , CSDL XML, Vocabularies
>    Affects Versions: V4.01_WD01
>            Reporter: Michael Pizzo
>             Fix For: V5.0_WD01
> Currently, default values for properties and (now, as of ODATA-1066) parameters are static values.
> There are some cases where the default value may be the result of a calculation. Examples:
> 1) The value of a related property/parameter
> 2) An expression based on the value of one (or more) related properties/parameters
> 3) The result of invoking a function(import) on the service (with params?)
> Issues: 
> -how to express the value of the defaultvalue (use Edm.Untyped? -- this could only be supported in 4.01)
> -what is the syntax of the expression?
> -can it invoke a funciton(import) and, if so, how are parameters passed?
> For parameters, could define a derived OptionalParameterType that has a DefaultValueExpression that is Edm.Untyped and only returned as that derived type in a 4.01 payload.

This message was sent by Atlassian JIRA

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