Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
Hi Andy,
getting back to this after, well, a long summer.
I have a remark regarding your following comment:
> RDFDataMgr
>
> The way to set things specially for a writing is to do:
>
> WriterDatasetRIOT w =
RDFDataMgr.createDatasetWriter(RDFFormat.JSONLD_COMPACT_FLAT) ;
> w.write(System.out, dataset.asDatasetGraph(), null, "http://base";,
RIOT.getContext()) ;
>
> rather than add RDFDataMgr.write(..., Context cxt)
I understand the point of not adding new methods to RDFDataMgr.
However:
- there are read methods with a Context param (so, we would get some
symetry between read and write methods)
- and I have the feeling that writing down a Model gets more convoluted for
the user without the write methods with the Context param.
If we have a write with the Context param, one just has to:
```
private void writeExample(OutputStream out, Model m, RDFFormat f, Context
jenaContext) {
try {
RDFDataMgr.write(out, m, f, jenaContext) ;
...
```
Without it:
```
private void writeExample(OutputStream out, Model m, RDFFormat f, Context
jenaContext) {
try {
WriterDatasetRIOT w = RDFDataMgr.createDatasetWriter(f) ;
DatasetGraph g = DatasetFactory.create(m).asDatasetGraph();
PrefixMap pm = RiotLib.prefixMap(g);
String base = null;
w.write(out, g, pm, base, jenaContext) ;
...
```
I've had to search a little bit to write it. I guess that other users also
would. Would it justify the extra RDFDataMgr.write(..., Context cxt)? That's
the question I am asking.
Best,
fps
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
