-
-
Notifications
You must be signed in to change notification settings - Fork 7
Write a JSON Schema case study for the W3C Web of Things #18
Write a JSON Schema case study for the W3C Web of Things #18
Conversation
Fixes: json-schema-org/community#221 Fixes: w3c/wot-marketing#329 Signed-off-by: Juan Cruz Viotti <[email protected]>
Hi @Relequestual and @egekorkan, I'm opening this PR with what we have so far so that we can collaborate and get it out soon! Some action items:
Thanks a lot! |
It doesn't seem like we will get a deployment preview of this branch for some reason. I'm attaching a PDF of how this looks like for me. You can also locally see the case study by running the following commands:
How the W3C Web of Things brings JSON Schema to the Internet of Things | JSON Schema Blog.pdf |
Hi @jviotti and @Relequestual ! Thanks for taking our input and turning it into a text that can be already read quite well. I can provide feedback, should I do it on the GitHub review or the PDF annotations? I would prefer GitHub option but I am ok for both. Regarding other points:
|
@egekorkan Awesome! Please post any comments on GitHub. The PDF is just a rendering on my local environment to simplify showing it to you :)
The Twitter cover looks pretty neat IMO, as it's more hardware-ish, probably more than what I'd be able to create myself out of the two logos 😅 What do you think @Relequestual ? |
pages/posts/w3c-wot-case-study.md
Outdated
- name: Juan Cruz Viotti | ||
photo: /img/avatars/jviotti.webp | ||
link: https://twitter.com/jviottidc | ||
excerpt: "Using JSON Schema at the W3C Web of Things to counter the fragmentation of the Internet of Things" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually "countering the fragmentation" is something we want to avoid since it starts with a negative tone. I would propose (from our input document):
Using JSON Schema at the W3C Web of Things to create an interoperability layer so that different IoT platforms, protocols and standards can operate together.
I hope it is not too late to fit into the small part that is under the title
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense! Done
pages/posts/w3c-wot-case-study.md
Outdated
To solve these problems, the W3C Web of Things works on providing standardized | ||
building blocks that make use of JSON Schema. | ||
|
||
JSON Schema is used for validating abstractions of physical entities called |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
abstraction of a physical entity can be understood differently by different people. Not sure of the best replacement but maybe "description of network-facing capabilities of physical entities"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think that reads well. Done
pages/posts/w3c-wot-case-study.md
Outdated
[Thing Descriptions][thing-description], and to model and describe data sent by | ||
Internet of Things consumers and producers in a multi-protocol manner. | ||
|
||
We are on-board with JSON Schema since Draft 4, and even the first draft |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we use another subject than "we"? There are other places with it as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True. Other case studies use "We" only in quotations. I'll fix it everywhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Signed-off-by: Juan Cruz Viotti <[email protected]>
Signed-off-by: Juan Cruz Viotti <[email protected]>
Signed-off-by: Juan Cruz Viotti <[email protected]>
Signed-off-by: Juan Cruz Viotti <[email protected]>
Signed-off-by: Juan Cruz Viotti <[email protected]>
Signed-off-by: Juan Cruz Viotti <[email protected]>
I have addressed all your comments @egekorkan . Please give it another round of review! I also added a "thank you" note at the end like for other case studies. |
Thank you @jviotti ! Can you generate a new PDF so that I can send it for reviews in the WoT group? |
Also, given that the cover picture was given to us by @Citrullin, @Citrullin is it fine to use it here (copyrights etc.)? |
I just want to say I'm so happy to see this. I enjoyed meeting the WoT folks at their conference in Santa Clara several years ago, when we had just started to revive work on the JSON Schema spec. I'm really glad to see that the work we've done since then is of interest, and particularly excited to see how JSON Schema vocabularies can fit with Semantic Web approaches. I never had as much time to keep up with the WoT work as I would have liked, but a better way to integrate with JSON LD/Semantic Web has always been something I'd love to see. I prioritized OAS integration in part because they had a major revision timed right for 2020-12, but the Thing Description has always been another major JSON Schema use case I kept in mind. |
Thank you for all your support over the years! Maybe @sebastiankb can remember more from Santa Clara event but having one the authors of JSON Schema since the beginning was a big support :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have given it another read since forgetting about the text definitely helps ;) I will do another read next week
Co-authored-by: Ege Korkan <[email protected]>
Co-authored-by: Ege Korkan <[email protected]>
Co-authored-by: Ege Korkan <[email protected]>
Co-authored-by: Ege Korkan <[email protected]>
Added! |
Signed-off-by: Juan Cruz Viotti <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey! sorry for being absent. I read the article and I liked a lot. Well done and thanks for your work :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is my last feedback after reading for one last time. We did not receive any further feedback from the WG so this can be published once these small changes are done.
Co-authored-by: Ege Korkan <[email protected]>
Co-authored-by: Ege Korkan <[email protected]>
Co-authored-by: Ege Korkan <[email protected]>
Co-authored-by: Ege Korkan <[email protected]>
Co-authored-by: Ege Korkan <[email protected]>
Revisions accepted! |
🥳 Let us know when the blog article is published. I have recently subscribed to the RSS feed and follow on Twitter but I can still miss it :) |
I'm going to give it a final read through this week! =D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor fixes, but the content is all good by me.
After tose are resolve, I say it's good to publish.
@egekorkan did you want to know when it will be published or just when it's published?
I'll probably merge in UK time, although anyone else is free to merge when my outstanding comments are resolved.
Thanks @Relequestual , I think the changes are good, just that there was a missing s for the last one. I cannot suggest changes on a suggested change so I had to create a new one.
Just when it is published :) I am not sure if the merge of this PR means publication, if it does, I will get the notification for sure :) |
Co-authored-by: Ben Hutton <[email protected]>
Co-authored-by: Ben Hutton <[email protected]>
Co-authored-by: Ben Hutton <[email protected]>
Signed-off-by: Juan Cruz Viotti <[email protected]>
All done! @Relequestual Don't forget to update the post date before publishing though |
Fixes: json-schema-org/community#221
Fixes: w3c/wot-marketing#329
Signed-off-by: Juan Cruz Viotti [email protected]