[OASIS Issue Tracker] (ODATA-1600) Functions and Actions as Interfaces

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

Heiko Theissen created ODATA-1600:
-------------------------------------

             Summary: Functions and Actions as Interfaces
                 Key: ODATA-1600
                 URL: https://issues.oasis-open.org/browse/ODATA-1600
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Vocabularies
            Reporter: Heiko Theissen


I would like to define an OData function or action outside of a service that serves as an interface. Such a function/action could then be invoked by a special client whenever a service implements it.

The functions {{isancestor}} and {{isdescendant}} defined in the Aggregation vocabulary are similar, but we assume they are implemented by _every_ service that uses the {{Aggregation.RecursiveHierarchy}} annotation.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)