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

Fix issues with Capabilities vocabulary

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.01_CS01
    • Fix Version/s: V4.01_CS02
    • Component/s: Vocabularies
    • Labels:
      None
    • Environment:

      Proposed

    • Proposal:
      Hide

      0) Define a new "SchemeName" TypeDefinition in the Auth vocabulary and use within Auth vocabulary whenever referencing a scheme.
      1) In PermissionType, rename "Scheme" to "Authorization" and change type to be "Auth.SchemeName".
      2) Change the type of OperationRestrictions to be Capability.OperationRestriction, not Collection(Capability.OperationRestriction).
      3) Rename OperationRestriction to OperationRestrictionType
      4) Remove "FunctionImport" from ReadRestrictions

      Show
      0) Define a new "SchemeName" TypeDefinition in the Auth vocabulary and use within Auth vocabulary whenever referencing a scheme. 1) In PermissionType, rename "Scheme" to "Authorization" and change type to be "Auth.SchemeName". 2) Change the type of OperationRestrictions to be Capability.OperationRestriction, not Collection(Capability.OperationRestriction). 3) Rename OperationRestriction to OperationRestrictionType 4) Remove "FunctionImport" from ReadRestrictions

      Description

      There are a few typos in some of the things we added to the Capabilities vocabulary:
      1) In PermissionType, "Scheme" should be of type "Edm.String" (and perhaps renamed "SchemeName") rather than Auth.SecurityScheme. We don't expect to inline the definition of the security scheme (including supported scopes, etc.)
      2) OperationRestrictions should be a single Capability.OperationRestriction, not Collection(Capability.OperationRestriction).
      3) For consistency, OperationRestriction should really be named OperationRestrictionType
      4) We don't have a way to apply restrictions to an ActionImport. We can target a FunctionImport with ReadRestrictions (although it would be a bit strange to have a FunctionImport with Readable=false), and Actions and Functions with OperationRestrictions, but we don't have a way to define permissions, headers, etc. associated with an ActionImport. Everything in OperationRestrictions applies to imports except FilterSegmentSupported.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mikep Michael Pizzo
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: