OASIS Open Data Protocol (OData) TCIcon indicating the project type

OASIS Open Data Protocol (OData) TC

Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-372

Addressing Derived Types

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: V4.0_WD01
    • Component/s: URL Conventions
    • Labels:
      None
    • Environment:

      [Closed]

    • Resolution:
      Hide

      No action

      Show
      No action

      Description

      I would like to seek clarification on below scenario....

      Suppose, I have 3 entity types 1) VirtualSystem 2) HyperVSystem and 3) VMWareSystem. Here, VirtualSystem is the base EntityType for both HyperVSystem and VMWareSystem. Now, if I define EntityContainer having only EnitySet for VirtualSystem. Are the following URLs correct?

      1) http://host/service/VirtualSystems
      Returns only instances of EntityType VirtualSystem

      2) http://host/service/VirtualSystems/HyperVSystem
      Returns only instances of EntityType HyperVSystem

      3) http://host/service/VirtualSystems/VMWareSystem
      Returns only instances of EntityType VMWareSystem

      How to get all instances of VirtualSystem, HyperVSystem and VMWareSystem in a single query?

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          ralfhandl Ralf Handl added a comment -

          http://host/service/VirtualSystems will return all instances of VirtualSystem, HyperVSystem and VMWareSystem in a single query.

          http://host/service/VirtualSystems/Model.HyperVSystem will restrict to instances of type "HyperVSystem" in schema "Model", and instances of any type that further specializes Model.HyperVSystem.

          http://host/service/VirtualSystems/Model.VMWareSystem will similarly restrict to instances of Model.VMWareSystem and its specializations.

          This is described in URL Conventions, section 4.9 Addressing Derived Types.

          We don't have a way to only request instances of Model.VirtualSystem that are not also instances of a derived type.

          If you are satisfied with this, please close the issue.

          Show
          ralfhandl Ralf Handl added a comment - http://host/service/VirtualSystems will return all instances of VirtualSystem, HyperVSystem and VMWareSystem in a single query. http://host/service/VirtualSystems/Model.HyperVSystem will restrict to instances of type "HyperVSystem" in schema "Model", and instances of any type that further specializes Model.HyperVSystem. http://host/service/VirtualSystems/Model.VMWareSystem will similarly restrict to instances of Model.VMWareSystem and its specializations. This is described in URL Conventions, section 4.9 Addressing Derived Types. We don't have a way to only request instances of Model.VirtualSystem that are not also instances of a derived type. If you are satisfied with this, please close the issue.
          Hide
          Permalink
          raman99 Ramanjaneyulu Malisetti (Inactive) added a comment -

          Thank you for the clarification. It is good if Spec is updated with such details.

          What is the best way to limit "http://host/service/VirtualSystems" return only instance of VirtualSystem type but not derived types' instances. Can spec include query option?

          Show
          raman99 Ramanjaneyulu Malisetti (Inactive) added a comment - Thank you for the clarification. It is good if Spec is updated with such details. What is the best way to limit "http://host/service/VirtualSystems" return only instance of VirtualSystem type but not derived types' instances. Can spec include query option?
          Hide
          Permalink
          sdrees Stefan Drees (Inactive) added a comment - - edited

          I think the samples given by Ralf are derived from those in section 4.9 as he indicates, thus "the Spec" contains "such details" already

          Is there a possibly less irritating sample you might offer for the follow-up question, where you only want the base type instances not including any derived type instances? I find myself caught in regarding these derived types as concrete types for the virtual type "VirtualSystem" ... and wonder if the intended latter query is a quest for NULLs so to say, those where another concrete type was not yet defined to put candidates in ... as I said, I am not sure where you are heading at ... otherwise $filter is a nice system query option ...

          So having said that I second Ralf in asking to close the issue with no action.

          Show
          sdrees Stefan Drees (Inactive) added a comment - - edited I think the samples given by Ralf are derived from those in section 4.9 as he indicates, thus "the Spec" contains "such details" already Is there a possibly less irritating sample you might offer for the follow-up question, where you only want the base type instances not including any derived type instances? I find myself caught in regarding these derived types as concrete types for the virtual type "VirtualSystem" ... and wonder if the intended latter query is a quest for NULLs so to say, those where another concrete type was not yet defined to put candidates in ... as I said, I am not sure where you are heading at ... otherwise $filter is a nice system query option ... So having said that I second Ralf in asking to close the issue with no action.
          Hide
          Permalink
          raman99 Ramanjaneyulu Malisetti (Inactive) added a comment -

          Thank you.

          Show
          raman99 Ramanjaneyulu Malisetti (Inactive) added a comment - Thank you.

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              raman99 Ramanjaneyulu Malisetti (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: