-
Notifications
You must be signed in to change notification settings - Fork 18
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
Blog prep - animation announcement #158
Conversation
@@ -0,0 +1,19 @@ | |||
<p> | |||
The Web of Things standardization activities are now illustrated through a new animation! | |||
This animation shows how a web developer can implement Internet of Things solutions while being interoperable and not locked into frameworks. |
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.
... not locked into specific frameworks.
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.
from today's marketing call: ... not locked into vendor specific frameworks.
Resolution is done in tomorrow's main call.
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.
Just small comment above. Also ok to submit this blog post as is.
@@ -0,0 +1,19 @@ | |||
<p> | |||
The Web of Things standardization activities are now illustrated through a new animation! | |||
This animation shows how a web developer can implement Internet of Things solutions while being interoperable and not locked into frameworks. |
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.
from today's marketing call: ... not locked into vendor specific frameworks.
Resolution is done in tomorrow's main call.
Note: marked as draft only because I'm cleaning up the image links. The text itself should be ready for final review, so please go ahead.
Upon reviewing the publication policy I realized that it said a resolution was required, but I explicitly said we would NOT be doing resolutions in the April 14 main call (and indeed, as expected, the turnout was low during Easter). So although I think this is a statement of fact and non-controversial, I don't want to violate the policy myself right after setting it up, so will hold off until we can have a resolution in the next main call. As it happens, I did make quite a few changes (which need review) and also need time to get the image in the right place so I can use it.