You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the contents of a draft dataset are updated, the public http://publishmydata.com/graphs/drafter/graph-modified-times graph is not modified whilst in the draft. In client applications, e.g. muttnik, one needs to check both live and in the draft graph for modified times e.g. http://publishmydata.com/graphs/drafter/draft/7407ab26-9d9f-411d-8fd0-a93e98e7ffd2.
This is because the entire modified graph doesn’t get cloned into the draftset, only the modified graphs. This behaviour is different to the usual Drafter workflow where Drafter transparently takes care of it, such that queries work the same whether inside a draft or not, when rewritten.
The upshot is that just querying the graph in the draft endpoint won't work.
For example, the following query for modified times on a Dataset does not work in muttnik when in draft:
When the contents of a draft dataset are updated, the public
http://publishmydata.com/graphs/drafter/graph-modified-times
graph is not modified whilst in the draft. In client applications, e.g. muttnik, one needs to check both live and in the draft graph for modified times e.g.http://publishmydata.com/graphs/drafter/draft/7407ab26-9d9f-411d-8fd0-a93e98e7ffd2
.This is because the entire modified graph doesn’t get cloned into the draftset, only the modified graphs. This behaviour is different to the usual Drafter workflow where Drafter transparently takes care of it, such that queries work the same whether inside a draft or not, when rewritten.
The upshot is that just querying the graph in the draft endpoint won't work.
For example, the following query for modified times on a Dataset does not work in muttnik when in draft:
the above is rewritten to:
The text was updated successfully, but these errors were encountered: