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-1008) Consider deprecating symbolic "max" length

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

Michael Pizzo commented on ODATA-1008:

I would say 4.01 "MUST NOT" use max (and perhaps that 4.0 SHOULD NOT?), and leave it open to the service whether they provide a concrete maximum or omit the MaxLength attribute, something like:

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. 

> 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

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