[OASIS Issue Tracker] (ODATA-1252) TypeDefinition should allow Edm.Primitive as underlying type

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

Michael Pizzo created ODATA-1252:
------------------------------------

             Summary: TypeDefinition should allow Edm.Primitive as underlying type
                 Key: ODATA-1252
                 URL: https://issues.oasis-open.org/browse/ODATA-1252
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Protocol
    Affects Versions: V4.01_CS01
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.01_CS02


In ODATA-1034 we added a DerivedTypeConstraint for the purpose of constraining a typedefinition that specified Edm.Primitive to be one of a subset of primitive types (i.e., a string or integer).

While we originally defined this annotation term as being applied to a TypeDefinition, we missed the fact that TypeDefinition was originally defined with an UnderlyingType that precluded Edm.PrimitiveType.

Defining a type definition with an underlying type of Edm.PrimitiveType requires that we also define semantics around what facets can be applied.  For example, can MaxLength, Precision, or Scale be applied, and what is the meaning of these facets for instances for which those facets don't apply.

The same semantics need to be defined for a property of type Edm.PrimitiveType.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)