Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mark mandatory guidelines #29

Open
LeonBein opened this issue Dec 13, 2021 · 3 comments
Open

Mark mandatory guidelines #29

LeonBein opened this issue Dec 13, 2021 · 3 comments
Labels
Discussion Guidelines question Further information is requested

Comments

@LeonBein
Copy link
Collaborator

Some guidelines (like "goal state should be subset of olc states") are like rules and must not be violated in order to get a valid model.

We should discuss if we should mark these guidelines as such and rephrase "should"s to "must"s
@carlaterboven
Copy link
Collaborator

See https://docs.google.com/spreadsheets/d/1KSPcRBWMFZ6jpeOx_CtvCb6Kc_V-BQMzqGT43eKqy-c/edit#gid=0 in error/warning/warning bulb column too see the differentiation we thought of.

@LeonBein
Copy link
Collaborator Author

Yes, I think that column suffices as classification.

@LeonBein
Copy link
Collaborator Author

Regarding the rephrasing: That is potentially still open, what do you think?

@LeonBein LeonBein added the question Further information is requested label Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Discussion Guidelines question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LeonBein @carlaterboven