Improved: Referential Constraints Referential constraints can specify navigation properties and complex properties in addition to primitive properties. Improved: Unicode Facet The Unicode can be used for defining terms, parameters, and return types. Somehow that got lost in version 4.0, and only properties and type definitions explicitly allowed it. New: Terms applying to Collections can now be marked as applicable to any collection of entities (e.g. collection-valued navigation properties), not just to entity sets. New: Annotations targeting Parameters and Return Types External targeting of annotations is now also possible for parameters and return of actions and functions, with the restriction that these annotations apply to all overloads. There’s still no way to externally target an individual overload. New: Inheriting Annotations Annotations are propagated along inheritance hierarchies: annotations on a base type are also valid on a derived type unless applied again with a different value. New: Absolute Paths in Annotations In version 4.0 path expressions in annotations are relative to the annotated model element. ersion 4.01 absolute paths starting with a forward slash followed by the qualified name of a model element. Pruned: Metadata Service Exposing an OData service’s metadata itself as an OData service seemed a good idea, but we’ve seen no implementation of it, so that concept on hold. Services using version 4.0 may still implement a but we don’t guarantee that the additional features of a version metadata service, 4.01 service can be represented in a version 4.0 metadata service.
Improved: Referential Constraints Referential constraints can specify navigation properties and complex properties in addition to primitive properties. Improved: Unicode Facet The Unicode can be used for defining terms, parameters, and return types. Somehow that got lost in version 4.0, and only properties and type definitions explicitly allowed it. New: Terms applying to Collections can now be marked as applicable to any collection of entities (e.g. collection-valued navigation properties), not just to entity sets. New: Annotations targeting Parameters and Return Types External targeting of annotations is now also possible for parameters and return of actions and functions, with the restriction that these annotations apply to all overloads. There’s still no way to externally target an individual overload. New: Inheriting Annotations Annotations are propagated along inheritance hierarchies: annotations on a base type are also valid on a derived type unless applied again with a different value. New: Absolute Paths in Annotations In version 4.0 path expressions in annotations are relative to the annotated model element. ersion 4.01 absolute paths starting with a forward slash followed by the qualified name of a model element. Pruned: Metadata Service Exposing an OData service’s metadata itself as an OData service seemed a good idea, but we’ve seen no implementation of it, so that concept on hold. Services using version 4.0 may still implement a metadata service, but we don’t guarantee that the additional features of a version 4.01 service can be represented in a version 4.0 metadata service.
new-in-odata-v4.01-wd01-2017-01-20.docx