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

EntitySet may be qualified with namespace or alias and EntityContainer

    Details

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

      [Proposed]

      Description

      The current rule for resourcePath allows qualifying an entity set with the name of its entity container, which is necessary if the entity container is not the default container.

      Functions and actions can additionally be qualified with the namespace as a prefix to the entity container. This option is missing for entity sets.

        Attachments

          Activity

          Hide
          ralfhandl Ralf Handl added a comment -

          This rule extension would only make sense for entity sets "imported" via a Using element.

          That the current rules don't allow addressing entity sets imported via Using is an indicator that Using isn't that useful, and I rather think that we should remove Using from the CSDL, or at least restrict it to "importing" types, actions, and functions only.

          Show
          ralfhandl Ralf Handl added a comment - This rule extension would only make sense for entity sets "imported" via a Using element. That the current rules don't allow addressing entity sets imported via Using is an indicator that Using isn't that useful, and I rather think that we should remove Using from the CSDL, or at least restrict it to "importing" types, actions, and functions only.

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              handl Ralf Handl
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: