GitLab

MEC013 Location API v2.1.1 is not fully supported by the MEC013 test suites

UELOCLOOK uses endpoint location/v2/users, and not location/v2/query/users UEINFOLOOK uses endpoint location/v2/users, and not location/v2/query/users RLOCLOOK uses endpoint location/v2/zones, and not location/v2/query/zones

All schemas for every test suites seem to use not named object, although the spec seemed to show the use of inline (named) objects. This result in validation to be missing one level of hierarchy (does not match the content of the file LocationAPI describe in the header which uses inline objects in its responses)

Note: Note that UEINFOSUB uses values instead of arrays as specified v2.1.1 in its default editable fields (interestRealm, userCriteria)