Gert van Valkenhoef

I also encountered this issue. The parser breaks when the OPTIONAL {} is nested inside a GRAPH ?g {} block. So the query ``` SELECT * WHERE { GRAPH ?g...

That is correct. You'd need to have a pretty good understanding of the overall inner workings of the package before attempting this.

Are there any plans to address this feedback? In particular the "type" attribute is important. It would also be useful to be able to specify a MIME-type for documents as...

I think something along these lines would be an improvement, I also tried to address some of the feedback in #9: ``` ``` See also https://www.w3.org/TR/xml-id/ - the XSD/DTD would...

This should already be possible, just specify the (log) hazard ratios in the data.re table. Also see ?mtc.network. If there are multi-arm trials with hazard ratios only you will need...

The standard error of the baseline log-hazard (0.066) in study 5 is greater than that of the log-hazard ratio of Fluticasone arm versus placebo (0.063), which is inconsistent.

Since they give log-hazards, not log-hazard-ratios, the value for placebo is likely correct. I think you want their formula (9) to compute the SE of the LHR in the other...

I'm not sure why this would be the case but I suspect it has to do with priors. Could you try with an explicitly set prior for the heterogeneity parameter...

Ah, in that case it is almost certainly due to the priors on the baseline arms for the arm-based data. Those are now less informative than the old N(0, (15...

You could cat(model$code) to get the code for both and modify the priors for the mu[i] in either one to check. You will probably have to set the inits for...