brickify TableHandler: should we disallow 'query' as an operation?

[brickschema]

brickify TableHandler: should we disallow 'query' as an operation?

[shreyasnagare]

Technically, every operation processed by the TableHandler generates a SPARQL Update query. Even operations with data /template blocks are used to create update queries (wrapped by INSERT DATA { .* } for adding triples to the base graph (blank, in the current implementation):

operations:
  -
    data: |-
      bldg:{VAV name}  brick:hasPoint bldg:{temperature sensor} .
      bldg:{VAV name}  brick:hasPoint bldg:{temperature setpoint} .

But I think it makes sense to let the data and template (Jinja) blocks be specifically for row-wise insertions (exclusive to TableHandler and its subclasses?) and use the query blocks for performing queries (one-time, like Handler does) after the tabular insertion is complete.

py-brickschema/tests/data/brickify/jinja2/template.yml

Lines 12 to 16 in 8d1740f

	data: |-
	bldg:{VAV name} rdf:type brick:RVAV .
	- template: |-
	{{ num_triples(value['VAV name'], "brick:hasPoint", value['temperature sensor'], value['sensors'], "brick:Temperature_Sensor") }}

As a related crazy idea, maybe we add a way for Brickify to load some sort of 'base' graph first?

I didn't think of it at the time but it seems like having non-blank base graphs preloaded could be really useful.