curation plan in sparql template
subjects and coverages in sparql template
provided service
actor members
has_maintaining_team with optional contact points
PP1 currently offers
Curates relationships
curation relationships
Fixed hosted_by
formatting
Thanks to sprql template activitytype can be accessed as literal
Thanks to sparql template service competence can be accessed as a simple label
Optional rdfs:label in sparql templates
optional description in sparql templates
Because of how we construct the RDF that we read from Virtuoso (see sparql templates), the title is always a literal.
resolved TODOs
Enrich the values to add to a resource in the catalogue
Can't use jena Query because does not support inference rule, can't use jena HttpEngine because it does not support long queryif we do not use Query: hence let's query with handmade post request to the sparql endpoint.
sparql queries are now freemarker templates where the subjectURL can be injected
Comments in sparql are identified by #, not //
Added declaration to use inference rules
Additional methods needed by the JRR publishing workflow
Can't find a way to use the DEFINE virtuoso pragma using the jena connector.
SPARQL queries
SPARQL queries that will be used to get the info for the JRR and catalogue