-
Notifications
You must be signed in to change notification settings - Fork 25
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
no vacabulary defintion for CoAP and MQTT yet #61
Comments
it is fixed now, @sebastiankb could you review it and close it if it is OK |
In TD spec, vocabulary terms are listed in tables with columns "Description", "Assignment" and "Type". The columns used in section 4 Vocabulary are different. Protocol Vocabulary are considered extension to TD vocabulary, therefore, should be described in a consistent way. I plan to create another issue for this. |
thanks @takuki, this was also my first thought. The presentation of the tables should be similar as you can find in the TD spec. I think, the tables are quite clear in understanding what have to be used. @egekorkan where does the MQTT codeNumbers (3, 8, and 10) come from? |
I will rearrange the vocabularies as @takuki and @sebastiankb mentinoed.
They come from the MQTT specification. All the possible values are documented here |
To increase the MQTT recognition I would prefer to rely on the same term usage as you can find in the MQTT specification. That means I would prefer to use the term |
The table in Section 4.3.3 MQTT Vocabulary, there is a row describing mqv:options member. The example used in mqv:options is quoted below.
I think the above example was copied from coap section. |
@mjkoster could you comment why the term |
in section section 3.3 we should clarify that CoAP and MQTT has no standardized RDF representation yet like for http
The text was updated successfully, but these errors were encountered: