Drop VPDiscoverable and VPQueyable

[henrietteharmse]

This is based on the discussion during General Meeting 2023/05/12:

[11:29] Brookes, Anthony J. (Prof.) (Guest)
Mark Wilkinson

I think we have discarded the "Discoverable" tag, because the FDPs are now required to register themselves in the VP index, so there's no benefit to that tag anymore... is that not correct?

Agreed. We don't need the 'discoverable' tag. And as Marc said, we don't the queryable tag either, as DCAT has a placeholder for services URLs.

[11:29] Marc Hanauer
Mark Wilkinson
I think we have discarded the "Discoverable" tag, because the FDPs are now required to register themselves in the VP index, so there's no benefit to that tag anymore... is that not correct?
same for "queryable". By the fact to have a dcat:service properly described with url endpoint, it's enough...

[markwilkinson]

We have changed our minds :-) Sorry!

What we have envisioned is:

predicate: vpConnection
domain: dcat:Resource <<------!!! allows us to make any layer "discoverable"
range: VPConnection (a class)

VPDiscoverable subClassof VPConnection (Erik P suggests that we use punning, rather than using a literal here)
VPQueryable subClassof VPConnection
VPXXXXXX subClassof VPQueryable (we will eventually subclass this to cover all the different kinds of query)

Is this clear?

[henrietteharmse]

I think that is very doable. I will be able to attend to this around end of June.

[henrietteharmse]

See #45

[henrietteharmse]

Completed with
commit