REMINDER: Align with OGC API Common ....

[pvretano]

Now that OGC API Common is on the verge of being released by the SWG to the TC for an adoption vote I wanted to create this issue as a reminder that we need to align Parts 1 & 2 with common. There are differences. For example Part 1 uses "conformance" as the rel for the conformance link while common uses the URL "http://www.opengis.net/def/rel/ogc/1.0/conformance".

[cportele]

See also #502. I don't think we need to or should change any of the existing requirements classes beyond adding a discussion and recommendations to provide links with the new link relation types or to explicitly state the itemType.

In #502 (comment) I said the following:

My proposal for supporting Common Part 1 in a future revision of Features Part 1 would be to add an additional req/conf class for Common Part 1. Implementations that support all Common Core requirements (the updated link relation type, other API requirements) in addition to the Features Core requirements could declare this through that additional conformance class.

Now I do not even think that we need to do this, since any API that implements Common would declare conformance with the Common conformance classes anyhow.