[OASIS Issue Tracker] (ODATA-1019) Add term Core.DynamicDefaultValue

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

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

Ralf Handl commented on ODATA-1019:
-----------------------------------

From https://github.com/oasis-tcs/odata-vocabularies/blob/master/vocabularies/Org.OData.Core.V1.md#Immutable

Immutable	A value for this non-key property can be provided on insert and remains unchanged on update
Computed	A value for this property is generated on both insert and update

I read this as
- Immutable implies Permission/Write for Insert, after that Permission/Read
- Computed implies Permission/Read

DynamicDefaultValue (formerly: ComputedDefault) is just a special case for DefaultValue: there is a default value, but it isn't static. If we only had reserved a niche in the values of DefaultValue I'd rather express this as 

  <Property Name="ExpirationDate" Type="Edm.Date" DefaultValue="variable" /> 

similar to Scale="variable". Unfortunately we also need this for string properties were "variable" is a literal static default value :-(

> Add term Core.DynamicDefaultValue
> ---------------------------------
>
>                 Key: ODATA-1019
>                 URL: https://issues.oasis-open.org/browse/ODATA-1019
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: Vocabularies
>    Affects Versions: V4.0_ERRATA03
>         Environment: Proposed
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> We sometimes have properties that are "auto-filled" by the service if the client provides no value on insert, and the auto-filled value is not static, so it cannot be specified as a DefaultValue.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)