Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

API Langtech > Compatibility > Flashcards

Compatibility Flashcards

1
Q

MUST not …
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

MUST not break backward compatibility
SHOULD prefer ..
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare..
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design ..
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always ..
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat ..
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD use..
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid..
MUST use media type versioning
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use ..
MUST not use URL versioning

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not ..

A

MUST not break backward compatibility
SHOULD prefer compatible extensions
MUST prepare clients to accept compatible API extensions
SHOULD design APIs conservatively
MUST always return JSON objects as top-level data structures
MUST treat OpenAPI specification as open for extension by default
SHOULD used open-ended list of values (x-extensible-enum) for enumerations
SHOULD avoid versioning
MUST use media type versioning
MUST not use URL versioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly

API Langtech (6 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions