[OASIS Issue Tracker] (ODATA-797) Org.OData.Capabilities.V1 term property FilterRestrictions/RequiresFilter has wrong facets

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

Gerald Krause created ODATA-797:
-----------------------------------

             Summary: Org.OData.Capabilities.V1 term property FilterRestrictions/RequiresFilter has wrong facets
                 Key: ODATA-797
                 URL: https://issues.oasis-open.org/browse/ODATA-797
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Vocabularies
    Affects Versions: V4.0_OS
            Reporter: Gerald Krause
             Fix For: V4.0_ERRATA03


Type of term FilterRestrictions is defined as:
      <ComplexType Name="FilterRestrictionsType">
        <Property Name="Filterable" Type="Edm.Boolean" DefaultValue="true">
          <Annotation Term="Core.Description" String="$filter is supported" />
        </Property>
        <Property Name="RequiresFilter" Type="Edm.Boolean" Nullable="true">
          <Annotation Term="Core.Description" String="$filter is required" />
        </Property>
        <Property Name="RequiredProperties" Type="Collection(Edm.PropertyPath)">
          <Annotation Term="Core.Description"
            String="These properties must be specified in the $filter clause (properties of derived types are not allowed here)" />
        </Property>
        <Property Name="NonFilterableProperties" Type="Collection(Edm.PropertyPath)">
          <Annotation Term="Core.Description" String="These properties cannot be used in $filter expressions" />
        </Property>
      </ComplexType>

The term lacks the intended default of "false" for property RequiresFilter. On the other hand, it has a Nullable="true" facet, which is the default anyway and can be omitted therefore.



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