Inconsistency in requirement naming for /req/crs/fc-bbox-crs-valid-defaultValue

[joostfarla]

In Part 2 (CRS), there is a requirement (8) named /req/crs/fc-bbox-crs-valid-defaultValue. However, in the corresponding abstract test (10), this requirement is called /req/crs/fc-bbox-crs-default-value, which currently does not resolve. I believe these 2 names should be identical. The latter one might be more consistent with the requirement regarding the crs parameter (/req/crs/fc-crs-default-value).

[pvretano]

@joostfarla thanks. I'll fix the the inconsistency ... just need to review the requirement to see if the term "valid" is relevant or not.