-
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
Create an overview diagram #4
Comments
@sandhawke Is this required for the spec (as per W3C) or a nice to have / something you'd like to see? Are the other specs doing it; yes/no; why not? Any particular reason why LDN should? I'm not opposed to having one. PRs are welcome. I'd like to know the boundaries and whether you are okay either way if this makes it into the spec or not (i.e., issue closing for whatever reason at any time). |
Totally a would-be-nice-to-have. Maybe as a sequence diagram... http://stackoverflow.com/questions/1367059/tool-for-drawing-protocol-sequence-diagrams Or something that shows the parties spread out in 2 dimensions instead of one. |
👍 |
Created an overview diagram: https://github.com/csarven/ldn/blob/6ad955c8e1fe67846cea7fd8f51837cf6802208b/linked-data-notifications-overview.svg . Live on the Editor's Draft as well. Happy to improve on that. Does it sufficiently address this issue? |
👍 |
Maybe it would be good, to distinguish between links/properties and requests, as I did in https://github.com/white-gecko/2016-08-29-LDN-Colloquium/blob/master/LingedDataNotifications/LDN-overview-all.svg |
Raised by @sandhawke
The text was updated successfully, but these errors were encountered: