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-1019) Add term Core.OptionallyComputed or Core.ComputedDefault

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

Michael Pizzo commented on ODATA-1019:

We should clearly define interaction between Computed, Immutable, and this new option, and permissions.

I assume immutable means that the value never changes (directly or indirectly), not just that it can't be set.

Could you assume a Computed property with Write permissions was settable? Are there other cases where its useful to explicitly specify that a property is settable (i.e., should we have two properties "Computed" and "Settable", and if both set it means that the default is computed but that it can be set, or is Computed the only case where settable is also interesting, in which case we should define a ComputedDefault?)

> Add term Core.OptionallyComputed or Core.ComputedDefault
> --------------------------------------------------------
>                 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
>            Reporter: 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

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