why is there no endpoint for /artefacts/{artefactID}/resources/classes/{uri}

[syphax-bouazzouni]

[jonquet]

The idea was that the call: /artefacts/{artefactID}/resources/{resourceID}
With resourceID certainly being an URI (but without putting this as a constraint)

Will be more generic and replace:

• /artefacts/{artefactID}/resources/classes/{resourceID}
• /artefacts/{artefactID}/resources/concepts/{resourceID}
• /artefacts/{artefactID}/resources/properties/{resourceID}
• /artefacts/{artefactID}/resources/individuals/{resourceID}
• /artefacts/{artefactID}/resources/schemes/{resourceID}
• /artefacts/{artefactID}/resources/collection/{resourceID}
• /artefacts/{artefactID}/resources/labels/{resourceID}

However, nothing prevent to actually implement them.

[jonquet]

With respect to the use of URI directly inside the service URL (approach blocked by some web servers now) then the proposition would be to implement:
/artefacts/{artefactID}/resources?uri=GIVENURI

We can say that one of the 2 calls should be available

[jonquet]

Or /artefacts/{artefactID}/resources/resource?uri=GIVENURI
In order to avoid the the situation where the /resources call sometime return a hydra:Collection and sometime not.

What do you think @syphax-bouazzouni ?