Backwards Compatibility for Dual 1.0.3 and 2.0.0 Conformance #270
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As requested by @rchadwic and @milt:
This is a small change that will make it possible for an LRS to receive a conformance certificate for both the 1.0.3 spec and the 2.0 / IEEE spec.
In short, this will:
X-Experience-API-Version
header for both suites.For the Alternative Request Syntax portion, this has been removed due to the IEEE document not mentioning any special treatment for that syntax. Since the CTS shouldn't be testing anything aside from the strict spec documents themselves, it didn't make much sense to force an LRS vendor to not provide that syntax if they wanted to.
The branch with these changes is currently live on our staging CTS at https://lrstest.staging.adlnet.gov, so feel free to check if things are behaving as expected.
Thanks!
-Trey