OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-1318) Fix issues with Capabilities vocabulary

Michael Pizzo created ODATA-1318:

             Summary: Fix issues with Capabilities vocabulary
                 Key: ODATA-1318
                 URL: https://issues.oasis-open.org/browse/ODATA-1318
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Vocabularies
    Affects Versions: V4.01_CS01
         Environment: Proposed
            Reporter: Michael Pizzo
             Fix For: V4.01_CS02

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.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]