Perhaps --output-file and --output-format to disambiguate? On 21 Sep 2015 19:25, "Andy Seaborne (JIRA)" <[email protected]> wrote:
> > [ > https://issues.apache.org/jira/browse/JENA-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901138#comment-14901138 > ] > > Andy Seaborne commented on JENA-1032: > ------------------------------------- > > Another strand: what about other commands? > > > riot --to-file parameter > > ------------------------ > > > > Key: JENA-1032 > > URL: https://issues.apache.org/jira/browse/JENA-1032 > > Project: Apache Jena > > Issue Type: Improvement > > Components: RIOT > > Affects Versions: Jena 3.0.0 > > Reporter: Stian Soiland-Reyes > > Priority: Minor > > Labels: file, output > > > > The {{riot}} command line does not have an option to specify the output > file to write to, forcing users to use shell redirections, e.g. > > {code} > > riot file.ttl > file.nt > > {code} > > This comes up as an issue for the Docker image > https://hub.docker.com/r/stain/jena/ - as you can't (easily) do {{> > file.txt}} as arguments to docker run to do redirections within the Docker > container. > > Lacking an output file parameter also makes it harder to call riot from > other programming languages, e.g. called from a Python script. > > The problem is that the {{--output}} parameter (and --out) is already > used to specify the output FORMAT rather than the output FILE. Perhaps > --to-file ? > > Suggested use: > > {code} > > riot --output jsonld --to-file /tmp/output.jsonld /tmp/input.ttl > > {code} > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
