-
Notifications
You must be signed in to change notification settings - Fork 36
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
Remove abbreviated format from docs #451
Conversation
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 sure on the best way forward to address the one comment.
docs/howto/communicating_results.md
Outdated
|
||
The reason a stakeholder might publish something like `U:LESe` is that it expresses that the analyst thought about [*Utility*](#utility) but does not have anything to communicate. | ||
The reason a stakeholder might publish a decision point with more than one value is that it expresses that the analyst thought about [*Utility*](#utility) but does not have anything to communicate. |
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.
"more than one value" is not the same as "all values". I think the sentence only makes sense in the context of "all values" ?
Also possible this sentence is just confusing / not something we would recommend people do, so possible option is to remove the whole discussion of the topic, which more broadly is "how to document an analyst looked but didn't learn anything"
That would probably be a separate issue? So the minimum required to just address this translation here is s/more than one value/all values/
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.
took the easy way out in e01f6a5
I'll spawn a separate issue to revisit the Partial or Incomplete Information section in the future
implement suggested change
Leaving a breadcrumb here that there is some additional discussion in #333 about the consequences of this PR. |
This PR removes the "abbreviated format" aka "vector format" from the documentation.