introducing a base has been suggested in #47 - additionally we should allow for any part to be relatively put inside the base through adding | base
we already have the uritexpand function, but it could be made to operate in a filter fashion. so this could work: "/some/{part}{?x,y}" | uritexpand(_) | base
producing a hashkey that obfuscates, but reliably reproduces keys based on internal object identifiers (or a list thereof) --> should be doable through concatenating the string representations of the keys, and pulling them through uuid-5 with some assigned namespace (which could be provided or else default to the baseref?) | hashkey my_ns
making whatever input end-up as a _:identifier to introduce a blanknode with | hashkey | bnode
skolemisation of iri as described in https://www.w3.org/2011/rdf-wg/wiki/Skolemisation -- rdflib.terms seems to have code on board already for parts of this --> | hashkey | skolem_iri this one will likely also need to some base href injected or else default to #47
Some ideas:
| base"/some/{part}{?x,y}" | uritexpand(_) | base| hashkey my_ns_:identifierto introduce a blanknode with| hashkey | bnode| hashkey | skolem_irithis one will likely also need to some base href injected or else default to #47