It is inconvenient to host the EJP-RD VP API at the existing individuals Beacon v2 endpoint location. The EJP-RD VP API is a specific 'Beacon v2 flavour', e.g. using specific required ontologies and custom age query handling. Systems that implement the standard Beacon v2 framework and model along with EJP-RD VP API might want to offer both the standard Beacon v2 individuals endpoint as well as the VP API flavoured endpoint. Suggestion is to rename the VP API endpoint to something likeejp-vp-individuals so it can peacefully co-exists with the standard individuals endpoint.