These are chat archives for csarven/ldn

16th
Apr 2017
Sarven Capadisli
@csarven
Apr 16 2017 08:15
"@id": "", in JSON-LD is same as <> in Turtle.
Thanks for the syntax fix. Updated.
Sarven Capadisli
@csarven
Apr 16 2017 08:34
@melvincarvalho See https://www.w3.org/TR/json-ld/#base-iri .. "This document uses an empty @id, which resolves to the document base. However, if the document is moved to a different location, the IRI would change."
Melvin Carvalho
@melvincarvalho
Apr 16 2017 09:35
what does <> expand to in a PUT?
Im still a bit confused. "@id": "", throws errors in the json ld playground, but leaving it out does not throw errors.
Sarven Capadisli
@csarven
Apr 16 2017 09:38
I don't tihnk the method matters. The parser has a value for the base IRI or derives it and just uses that.
I'm not seeing an error
Melvin Carvalho
@melvincarvalho
Apr 16 2017 09:39
ok, well it seems inconsistent, even among the examples mentioned ... i certainly find it confusing, perhaps it will become clearer in time
Sarven Capadisli
@csarven
Apr 16 2017 09:39
What's inconsistent exactly?
or what's confusing?
Is <> confusing?
Melvin Carvalho
@melvincarvalho
Apr 16 2017 09:39
to sometimes use <> and other times use []
Sarven Capadisli
@csarven
Apr 16 2017 09:40
I don't understand what [] has anything to do with this.
Melvin Carvalho
@melvincarvalho
Apr 16 2017 09:40
isnt that the syntax for a bnode?
Sarven Capadisli
@csarven
Apr 16 2017 09:40
When you see "@id": "" in JSON-LD, think <> in Turtle
Melvin Carvalho
@melvincarvalho
Apr 16 2017 09:40
in turtle
seems problematic, if you click on the tabs in the playground, it errors out
Sarven Capadisli
@csarven
Apr 16 2017 09:45
There is a button for permalink.. can you give me that link?
Bart van Leeuwen
@semanticfire
Apr 16 2017 10:05
@csarven did you see my notes ?
Sarven Capadisli
@csarven
Apr 16 2017 10:26
I think we shuffled around with that in the past. IIRC, the reason for how it is now was to be in favour of showing different payloads.
i.e., if we showed say one payload in Sender, the Consumer example would have the same in its response. There'd be repetition.
Melvin Carvalho
@melvincarvalho
Apr 16 2017 13:10
Processing error: Error: [jsig.sign] The data to sign is empty. This error may be because a "@context" was not supplied in the input thereby causing any terms or prefixes to be undefined.
but removal of @id="" fixes it
try any of the examples
if the example in the spec breaks the playground, something's not right! :)
but ill not raise an issue
Melvin Carvalho
@melvincarvalho
Apr 16 2017 13:15
i suspect it'll get through ... I doubt anyone has had a serious look at the examples, if a syntax error can get through ...
i would like to be able to sign notifications tho, because then I can see who sent them, and it may help with spam
also i am doing a lot of work with payments
and notifications / credits
for which signing becomes more important
Bart van Leeuwen
@semanticfire
Apr 16 2017 15:10
btw, as for w3c process errors / typos in examples can be fixed after rectrack
Sarven Capadisli
@csarven
Apr 16 2017 15:36
@melvincarvalho
Please copy/paste the code you are referring to. Or give me the permalink so i can see exactly what you are seeing.
The corrected Pingback example from https://linkedresearch.org/ldn/ works for me at JSON-LD playground.
Pingback doesn't have a context file, which is fine.. because the example is not trying to fetch the context.
Sarven Capadisli
@csarven
Apr 16 2017 15:41
And the NQuads tab shows:
<http://json-ld.org/playground/> <http://purl.org/net/pingback/source> <http://example.net/note#foo> .
<http://json-ld.org/playground/> <http://purl.org/net/pingback/target> <http://example.org/article#results> .
<http://json-ld.org/playground/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/net/pingback/Item> .
Melvin Carvalho
@melvincarvalho
Apr 16 2017 16:41
@csarven try clicking all the tabs on that example, it gives errors
Sarven Capadisli
@csarven
Apr 16 2017 16:41
I have. I don't get errors.