[ODATA-1311] Edm.AnyPropertyPath: no corresponding path expression - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Proposal:

Hide

Remove type Edm.AnyPropertyPath.

Vocabulary designers can use Edm.ModelElementPath instead, and can annotate the term or term property with Validation.DerivedTypeConstraint to restrict it to just Edm.PropertyPath and Edm.NavigationPropertyPath.

Show
Remove type Edm.AnyPropertyPath. Vocabulary designers can use Edm.ModelElementPath instead, and can annotate the term or term property with Validation.DerivedTypeConstraint to restrict it to just Edm.PropertyPath and Edm.NavigationPropertyPath.
Resolution:

Hide

Seeing the growing similarities between (structural) properties and navigation properties it seems helpful to have this abstract type.

Annotations will have to provide a path to the respective property, which is either structural or navigation, so no specific path expression needed for AnyPropertyPath.

Show
Seeing the growing similarities between (structural) properties and navigation properties it seems helpful to have this abstract type. Annotations will have to provide a path to the respective property, which is either structural or navigation, so no specific path expression needed for AnyPropertyPath.

~~ODATA-516~~ introduced Edm.AnyPropertyPath and Edm.AnyPath (later renamed to Edm.ModelElementPath).

While we added a dynamic annotation expression for ModelElementPath, we did not add one for Edm.AnyPropertyPath.