yaml + metadata is fiddly; try allowing turtle.
Treat turtle and yaml metadata equally. Storing metadata from Turtle as rdflib.Graph makes sense; getting it into a python object (as metadata from YAML is stored in md.meta) is circuitous, but does suggest an extension of how metadata is stored
[x] parse embeded turtle with rdflib & serialize into html
[x] allow JSON-LD context to be set (having a context means you get compact JSON-LD)
[ ] allow Turtle context (@base, @vocab, @prefix) to be set
[x] store parsed graph in md object as md.graphs
[x] store json-ld serialization of graph in md object as md.jsonld
[x] store python dict representation json-ld in md.meta
[x] store json-ld serialzn of YAML metadata in as md.jsonld
[x] parse json-ld from YAML with rdflib & store in md.graphs
yaml + metadata is fiddly; try allowing turtle. Treat turtle and yaml metadata equally. Storing metadata from Turtle as rdflib.Graph makes sense; getting it into a python object (as metadata from YAML is stored in md.meta) is circuitous, but does suggest an extension of how metadata is stored
@base
,@vocab
,@prefix
) to be set