-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add payload example using Webmention terms #63
Comments
I dunno, it seems unlikely that anyone looking at the LDN spec is going to straight up want to send webmentions as JSON. They might be looking if they want to bridge between LDN and Webmention, in which case this example is already in http://w3c-social.github.io/social-web-protocols/#ldn-to-wm |
The Pingback example is not particularly interesting or useful either. Okay to remove that if need to. There is a sufficient number and variety of examples in the spec in any case. |
Commenting only on the syntax of the example. Is this correct?
I think in this case you would want to have a blank node meaning a message that doesnt have a specific URI. In this case you could leave out the @id completely:
OR to avoid a round trip of the context lookup
Whether or not this example is included, I'd be interested to see the valid syntax on this, as it's something I raised before. Let me know if you think that's correct. :) |
@melvincarvalho if you want to debate the syntax of the examples in the spec, please open a new issue. For the record, either is correct, and both result in different semantics (no |
Okay, the SWP already document covers this. It will be good to get an updated version of that published. |
Given that Webmention is a W3C REC, and that LDN already has an example of sending a Pingback payload, it seems appropriate to add an example using Webmention as well.
I think the Webmention example payload would look like the following, given the Webmention namespace document at https://www.w3.org/ns/webmention
The text was updated successfully, but these errors were encountered: