[OASIS Issue Tracker] (ODATA-1020) Remove / in reference in instance annotation in filter and orderby expression

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

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

Michael Pizzo edited comment on ODATA-1020 at 1/18/17 9:23 PM:
---------------------------------------------------------------

The propertyname@term syntax is something we made up for JSON, since there wasn't a way to embed the annotation within primitive types.  From a generic perspective, I would read "propertyname/@term" as the logical expression for the @term term applied to the propertyname property.

This also aligns well with scenarios where the annotation is nested in the type and not prefixed with a property name.


was (Author: mikep):
The propertyname@term syntax is something we made up for JSON, since there wasn't a way to embed the annotation within primitive types.  From a generic perspective, I would read "propertyname/@term" as the logical expression for the @term term applied to the propertyname property.

> Remove / in reference in instance annotation in filter and orderby expression
> -----------------------------------------------------------------------------
>
>                 Key: ODATA-1020
>                 URL: https://issues.oasis-open.org/browse/ODATA-1020
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions
>    Affects Versions: V4.01_CSD01
>            Reporter: Hubert Heijkers
>             Fix For: V4.01_CSD02
>
>
> In ODATA-933 we allowed using instance annotations in $filter. In doing so we ended up treating annotations as a path segment, matching the path syntax.
> Although perhaps perfectly aligned with the path syntax it looks weird to have two separators, both / and @ sign separating the property to which the annotation applies to and the annotation itself. Everywhere else where we, in our JSON payloads, have an annotation, we use property@annotation.
> I'd propose we'd amend the resolution of ODATA-933 accordingly and omit the / from the reference to the annotation and therefore address an annotation value on a property as 
> NavigationPropertyName@Term#Qualifier instead. 



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