-
-
Notifications
You must be signed in to change notification settings - Fork 666
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
clarification for V4.1 and V4.2 #2139
Comments
ping @tghosth |
From my understanding, V4.1 is more focused on design/architecture of the access control system and V4.2 on some of the implementation details. Is that correct? |
Not sure we have ever had any guidance there so I am open to suggestions. I think it would be good to have some brief text at the start of each section which explains what sort of requirements are going in there. |
Some guidance would be great - I think that means we have to do that throughout the entire standard. |
Yes, and for that we have a separate issue opened so we don't need to discuss it here: #1797
If we it is not easy to find what is the difference between those section, it is natural to ask, do we need 2 separate chapters. If we use architecture/principle for V4.1 and implementation for V4.2
|
@EnigmaRosa does the split which @elarlang proposed make sense to you? |
Linking it here: #2063 (comment) (potential clarifying for 4.1.3) |
In V4 we have sections:
Can we have clear ruleset, why those are separate and by what conditions one requirement belong to them. For example, why 4.1.3 is in V4.1 not in V4.2 although it's pretty much same requirement as 4.2.1.
The text was updated successfully, but these errors were encountered: