astm-utm Protocol issues

astm-utm / Protocol

ASTM UTM Protocol (API and sequence diagrams)

15 stars 10 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Fix CSTP0035 requirement reference

#71 barroco closed 6 months ago
1
`Circle` does not require `center` or `radius` properties

#70 eval-on-point opened 1 year ago
0
Make final changes for 1.0

#69 BenjaminPelletier closed 2 years ago
0
Update to 0.3.17+uspace

#68 barroco closed 2 years ago
0
Update API to match 0.4 text prior to second ballot

#67 BenjaminPelletier closed 2 years ago
3
Add type to GeoZone reason property

#66 barroco closed 2 years ago
1
Appropriate use of exclusiveMinimum and exclusiveMaximum

#65 nasajoey opened 2 years ago
4
Add missing type to make openapi2proto

#64 StevenPG closed 2 years ago
0
Logging update

#63 rchampagne closed 3 years ago
0
Add POST/GET note, harmonize operationIds, rev version

#62 BenjaminPelletier closed 3 years ago
0
Harmonize with text of standard

#61 BenjaminPelletier closed 3 years ago
0
Resolve most open issues as of 5/19

#60 BenjaminPelletier closed 3 years ago
0
Add polling frequency indication to position reports

#59 BenjaminPelletier closed 3 years ago
0
Clarify that accuracy field in situational awareness position report is optional

#58 BenjaminPelletier closed 3 years ago
0
Logging

#57 rchampagne closed 3 years ago
0
Add ED-269 GeoZone structure

#56 BenjaminPelletier closed 3 years ago
4
Fix constraint reference error conditions

#55 BenjaminPelletier closed 3 years ago
0
Resolve issues as of 2021-01-14

#54 BenjaminPelletier closed 3 years ago
0
Clean up repo

#53 BenjaminPelletier closed 3 years ago
1
Add operation priorities

#52 BenjaminPelletier closed 3 years ago
0
Use RID-style geo format rather than GeoJSON

#51 BenjaminPelletier closed 3 years ago
0
Clarify that any object field can be set to null rather than omitted for the same effect

#50 BenjaminPelletier closed 3 years ago
0
Specify expected value for "no-fly" constraint type

#49 BenjaminPelletier closed 3 years ago
0
Add operation ID to telemetry model

#48 BenjaminPelletier closed 3 years ago
0
Implement basic down-USS mitigation

#47 BenjaminPelletier closed 3 years ago
0
Fix issues as of 2020-09-25

#46 BenjaminPelletier closed 3 years ago
1
Clearly document Subscription dependency behavior

#45 BenjaminPelletier closed 3 years ago
0
Separate entity_conflicts by type in AirspaceConflictResponse

#44 BenjaminPelletier closed 3 years ago
1
Clarify expected USS behavior when transitioning Operations

#43 BenjaminPelletier closed 3 years ago
0
Clarify behavior of GET /operations/{id} when operation is Ended

#42 BenjaminPelletier closed 3 years ago
1
Add data logging pseudo-endpoint

#41 BenjaminPelletier closed 3 years ago
1
Restore sequential version for Operation references and Constraint references

#40 BenjaminPelletier closed 3 years ago
0
Investigate multiple scope specification

#39 BenjaminPelletier closed 3 years ago
0
Harmonize with text of standard

#38 BenjaminPelletier closed 2 years ago
0
Clean up missing OVNs response

#37 BenjaminPelletier closed 3 years ago
0
Make ID terminology consistent

#36 BenjaminPelletier closed 3 years ago
1
Fix issues with known solutions as of 2020-06-24

#35 BenjaminPelletier closed 4 years ago
0
Clarify mapping between DELETE and "Ended"

#34 BenjaminPelletier closed 4 years ago
0
Add versioning to update/delete

#33 BenjaminPelletier closed 4 years ago
0
Wrong scopes for Constraint details endpoints

#32 BenjaminPelletier closed 3 years ago
1
clarify JWT Claim 'scope' datatype in ASTM and RID specs

#31 issmith1 closed 4 years ago
1
Start and end times for Operations and Constraints should be required

#30 BenjaminPelletier closed 4 years ago
0
aud is not a required field

#29 nasajoey closed 3 years ago
1
Altitude bounds in Volume3D should not be required in general

#28 BenjaminPelletier closed 4 years ago
1
`state` field in OperationDetails is not required

#27 BenjaminPelletier closed 4 years ago
1
Specify that at least one notification type is required in Subscription

#26 BenjaminPelletier closed 4 years ago
3
if 'anyOf' is imported to AWS API Gateway, schema-level validations are silently omitted by Gateway

#25 issmith1 opened 4 years ago
5
Remove regex expressions

#24 BenjaminPelletier opened 4 years ago
1
Make "references" terminology consistent

#23 BenjaminPelletier closed 4 years ago
1
Remove single scope specification

#22 BenjaminPelletier closed 4 years ago
2