You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just like FAQs are a good way to start discussions and make small incremental consensus gains, I also think we should start a 'definitions' document. I think it unlikely that this document will eventually be standardized as a standalone document, but I do think it likely that the definitions themselves will end up in our work products.
So the the issue is should we create a definitions document and start defining terms (either directly or by referencing other standards that already defined the terms).
The text was updated successfully, but these errors were encountered:
I propose that a definitions page be added to the working directory (see Issue #9 and Pull Request #10). Individual Terms can get proposed in Issues, discussion can occur on each issue and via discussion in meetings, and then PR's can be created and approved as consensus is reached on each term. Note it may be a two-stage process in we may first agree that we need to define a particular term so a PR adds it to the page as a term without a definition. And then at a later time, once consensus is reached on the definition, then another PR is made with the definition.
Just like FAQs are a good way to start discussions and make small incremental consensus gains, I also think we should start a 'definitions' document. I think it unlikely that this document will eventually be standardized as a standalone document, but I do think it likely that the definitions themselves will end up in our work products.
So the the issue is should we create a definitions document and start defining terms (either directly or by referencing other standards that already defined the terms).
The text was updated successfully, but these errors were encountered: