Skip to content

Commit

Permalink
Merge pull request #62 from astm-utm/update-text
Browse files Browse the repository at this point in the history
Add POST/GET note, harmonize operationIds, rev version
  • Loading branch information
rchampagne authored Jun 25, 2021
2 parents 810d9ad + b652b62 commit bba0359
Showing 1 changed file with 29 additions and 15 deletions.
44 changes: 29 additions & 15 deletions utm.yaml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
openapi: 3.0.2
info:
title: UTM API (USS->DSS and USS->USS)
version: 0.3.14
version: 0.3.15
description: |-
Interface definitions for 'Discovery and Synchronization Service' (DSS) and 'UAS Service Supplier (USS).
Expand Down Expand Up @@ -439,15 +439,15 @@ components:
exclusiveMinimum: false
default: 0

SearchSubscriptionParameters:
QuerySubscriptionParameters:
description: |-
Parameters for a request to find subscriptions matching the provided criteria.
type: object
properties:
area_of_interest:
$ref: '#/components/schemas/Volume4D'

SearchSubscriptionsResponse:
QuerySubscriptionsResponse:
description: Response to DSS query for subscriptions in a particular geographic
area.
required:
Expand Down Expand Up @@ -773,15 +773,15 @@ components:
operational_intent_reference:
$ref: '#/components/schemas/OperationalIntentReference'

SearchOperationalIntentReferenceParameters:
QueryOperationalIntentReferenceParameters:
description: |-
Parameters for a request to find OperationalIntentReferences matching the provided criteria.
type: object
properties:
area_of_interest:
$ref: '#/components/schemas/Volume4D'

SearchOperationalIntentReferenceResponse:
QueryOperationalIntentReferenceResponse:
description: Response to DSS query for OperationalIntentReferences in an area
of interest.
required:
Expand Down Expand Up @@ -903,15 +903,15 @@ components:
constraint_reference:
$ref: '#/components/schemas/ConstraintReference'

SearchConstraintReferenceParameters:
QueryConstraintReferenceParameters:
description: |-
Parameters for a request to find ConstraintReferences matching the provided criteria.
type: object
properties:
area_of_interest:
$ref: '#/components/schemas/Volume4D'

SearchConstraintReferencesResponse:
QueryConstraintReferencesResponse:
description: Response to DSS query for ConstraintReferences in an area of interest.
required:
- constraint_references
Expand Down Expand Up @@ -1940,7 +1940,7 @@ paths:
content:
application/json:
schema:
$ref: '#/components/schemas/SearchOperationalIntentReferenceParameters'
$ref: '#/components/schemas/QueryOperationalIntentReferenceParameters'
required: true
tags:
- Operational intent references
Expand All @@ -1950,13 +1950,20 @@ paths:
- utm.strategic_coordination
summary: Query all operational intent references in the specified area/volume/time
from the DSS.
operationId: searchOperationalIntentReferences
description: |-
Note that this endpoint does not produce any mutations in the DSS
despite using the HTTP POST verb. The HTTP GET verb is traditionally
used for operations like this one, but requiring or using a request body
for HTTP GET requests is non-standard and not supported by some
architectures. POST is used here instead of GET to ensure robust
support for the use of a request body.
operationId: queryOperationalIntentReferences
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/SearchOperationalIntentReferenceResponse'
$ref: '#/components/schemas/QueryOperationalIntentReferenceResponse'
description: Operational intents were successfully retrieved.
'400':
content:
Expand Down Expand Up @@ -2294,7 +2301,7 @@ paths:
content:
application/json:
schema:
$ref: '#/components/schemas/SearchConstraintReferenceParameters'
$ref: '#/components/schemas/QueryConstraintReferenceParameters'
required: true
tags:
- Constraint references
Expand All @@ -2306,13 +2313,20 @@ paths:
- utm.constraint_ingestion
summary: Query all constraint references in the specified area/volume from the
DSS.
description: |-
Note that this endpoint does not produce any mutations in the DSS
despite using the HTTP POST verb. The HTTP GET verb is traditionally
used for operations like this one, but requiring or using a request body
for HTTP GET requests is non-standard and not supported by some
architectures. POST is used here instead of GET to ensure robust
support for the use of a request body.
operationId: queryConstraintReferences
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/SearchConstraintReferencesResponse'
$ref: '#/components/schemas/QueryConstraintReferencesResponse'
description: Constraint references were successfully retrieved.
'400':
content:
Expand Down Expand Up @@ -2503,7 +2517,7 @@ paths:
- Authority:
- utm.constraint_management
summary: Update the specified constraint reference in the DSS.
operationId: putConstraintReference
operationId: updateConstraintReference
responses:
'200':
content:
Expand Down Expand Up @@ -2625,7 +2639,7 @@ paths:
content:
application/json:
schema:
$ref: '#/components/schemas/SearchSubscriptionParameters'
$ref: '#/components/schemas/QuerySubscriptionParameters'
required: true
tags:
- Subscriptions
Expand Down Expand Up @@ -2655,7 +2669,7 @@ paths:
content:
application/json:
schema:
$ref: '#/components/schemas/SearchSubscriptionsResponse'
$ref: '#/components/schemas/QuerySubscriptionsResponse'
description: Subscriptions were retrieved successfully.
'400':
content:
Expand Down

0 comments on commit bba0359

Please sign in to comment.