[OASIS Issue Tracker] (ODATA-1008) Consider deprecating symbolic "max" length

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

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

Michael Pizzo updated ODATA-1008:
---------------------------------

    Proposal: The OData 4.0 use of the symbolic value max in place of an integer value is deprecated in OData 4.01. While OData 4.0 clients MUST be prepared for this value, OData 4.01 and greater services MUST NOT return a value of max for the MaxLength attribute and MAY instead specify the concrete maximum length supported for the type by the service, or omit the attribute entirely.   (was: Change second paragraph of section 5.3.2 MaxLength to

Instead of an integer value the constant max MAY be specified as a shorthand for the maximum length supported for the type by the service. Responses for OData version 4.01 or later MUST/SHOULD NOT use the symbolic value max and instead specify the concrete maximum length supported for the type by the service.)

> Consider deprecating symbolic "max" length
> ------------------------------------------
>
>                 Key: ODATA-1008
>                 URL: https://issues.oasis-open.org/browse/ODATA-1008
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_ERRATA03
>         Environment: Proposed
>            Reporter: Michael Pizzo
>            Assignee: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> We currently allow specifying "max" as the maximum length of a string property. This is of dubious value, and we don't want to support it in the JSON format. Should we deprecate it from the XML format?



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