Ok, I'll do that. I'll try to create the pull request within a few days.
Have a nice day
Vincent
Le 31/01/2019 à 16:38, Andy Seaborne a écrit :
On 31/01/2019 15:01, vincent ventresque wrote:
Many thanks for the detailed explanation, all the more as I struggled
a lot of time with a similar p
On 31/01/2019 15:01, vincent ventresque wrote:
Many thanks for the detailed explanation, all the more as I struggled a
lot of time with a similar problem (see my question on stackoverflow :
https://stackoverflow.com/questions/52221250/php-easyrdf-unable-to-get-graph-from-construct-query
).
Many thanks for the detailed explanation, all the more as I struggled a
lot of time with a similar problem (see my question on stackoverflow :
https://stackoverflow.com/questions/52221250/php-easyrdf-unable-to-get-graph-from-construct-query
).
About the pull request : should I remove the 'plai
Hello
Thanks a lot for the explanations!
> And for application/n-quads that is a dataset serialization not a
graph serialization
So do you know why the 'name' $mtNQuads is in s-get?? (line 50)
> Per application/json several people have already commented that there
is no serialization direct
Jena has it's own content negotiation mechanism - I couldn't find an
existing one at the time and it has turned out to be "quite complicated"
for linked data as control of the defaults and choices when not an exact
match is important.
So we have control of the corner cases and defaults.
Inter
No the content types aren't wrong you're just using them for the wrong things.
Per application/json several people have already commented that there is no
serialization directly linked to application/json. There are specific MIME
types for specific variants of JSON e.g. application/ld+json for
Sorry, let me sum up the previous messages :
1) I wanted to export a named graph from tdb to ntriples
2) Andy advised to modify s-get, which I did
3) when modifying s-get, I noticed there were 2 wrong content-types :
application/json & application/n-quads ; both give rdf-xml output
4) Andy s
Vincent,
can you start by explaining what you are trying to do and why, rather
describing how you're doing it?
On Thu, Jan 31, 2019 at 2:20 PM vincent ventresque
wrote:
>
> Sorry, I should have explained more clearly : the previous messages
> where about default settings in s-get, and when creat
Sorry, I should have explained more clearly : the previous messages
where about default settings in s-get, and when creating a new function
to handle --output option, I noticed there was a wrong content-type in
s-get for plain json (see my s-get file here :
https://sourceforge.net/projects/ffl-
I'm not sure what you expect to get back from Fuseki with an "application/json"
mimetype? There is no W3C-spec plain-JSON RDF serialization that I know of. I
suppose there's the old Tallis idea:
https://jena.apache.org/documentation/io/rdf-json.html
but I can't imagine that's what you're lookin
It seems that the problem is completely independent from s-get (see
these results with curl below). So I think there's a default setting
somewhere in Fuseki itself.
#~~~ --header 'Accept: application/json' ~
:~/Documents/fuseki/bin$ curl --header 'Accept: application/
Thanks for your quick reply!
> $mtAppJSON isn't used.
I think my previous msg wasn't clear : I meant raw json and not json-ld
(my code works now for both, and I use $mtAppJSON ; but I had to
replace 'application/json' with 'application/rdf+json' in order to get
json instead of XML ; see the
On 31/01/2019 11:26, vincent ventresque wrote:
Hello,
I found the origin of the problem for json : the $mtAppJSON had the value
'application/json'
$mtAppJSON isn't used.
"application/rdf+json"
isn't JSON-LD (it's the old Talis format).
There is:
$mtJSONLD = 'application/ld+jso
Hello,
I found the origin of the problem for json : the $mtAppJSON had the value
'application/json'
it has to be replaced with
'application/rdf+json'
I've updated the file here :
https://sourceforge.net/projects/ffl-misc/files/fuseki_scripts_custom-ruby/s-get/download
Maybe I'm going to
Hi Andy,
Thanks again for your idea to modify the s-get script, it helped me
understand ruby utilities and http requests (I often use the ruby
scripts but never really looked inside).
Don't know how to submit a pull request, and I'm not a ruby expert!
Therefore I've put a small test file her
Hi Andy,
Many thanks for these ideas, I'm going to try the curl & riot solutions.
> Modify the s-get script to handle --output and set the "Accept:"
header then please submit a pull request for the changes
I had made an attempt to modify the s-get script in the same way as for
s-query but it
On 28/01/2019 11:04, Vincent Ventresque wrote:
Hello,
I want to export a named graph which is stored in a TDB dataset, and I
want to store the output in several files (for the named graph contains
+/- 9.5 M triples).
My idea is to use "split" command in order to cut the output of the
exp
Hello,
I want to export a named graph which is stored in a TDB dataset, and I
want to store the output in several files (for the named graph contains
+/- 9.5 M triples).
My idea is to use "split" command in order to cut the output of the
export into pieces. However, this solution with "split
18 matches
Mail list logo
