Support Studio backed by SPARQL view with a specific tag

[samuel-kerrien]

Description

@crisely09 defined a studio for publishing, based on a user defined SPARQL view. That SPARQL view is filtered on a specific resource tag.
Upon building the SPARQL query that loads data, she crafted a ?self variable that contains the rev (i.e. revision) of the resource in order to ensure that upon clicking the row of the generated table, the correct revision opens in the side drawer instead of the LATEST revision.

Solution discussed

We would like to enable a new optional parameter in the SPARQL query that backs the SPARQL based studio table.
This parameter: rev will enable the user to capture the specific revision of the resource to be presented.
It was considered whether tag should also be presented, but since each tag is pointing to a specific revision, rev should suffice.
Consequently, it will be the responsibility of the user to capture the appropriate revision of the resource in the ?rev variable of the SPARQL query. Should the ?self URL also contain a URL, the ?rev will take precedence.
When the user clicks on a row of the studio generated table, the mandatory ?self and optional ?rev will be used to open a side drawer and select the resource at the correct revision. Should not revision be given, the LATEST will be selected.
the ?rev variable is not presented in the generated table. Should the user want to present the revision, an other variable name (e.g. revision) could be used.

Acceptance Criteria

• ?self and ?rev are never displayed
• ?self and ?rev are used to open the appropriate revision of the resource in the side drawer
• Should ?self URL contain a rev or a tag, ?rev takes precedence
• User documentation should be updated to reflect these changes