-
Notifications
You must be signed in to change notification settings - Fork 12
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
Resolve Directory Access Control branch #72
Comments
The conversation regarding the need for a The initial idea behind the
After several conversations with Victor Wallin and a discussion during the weekly coreLang meeting on June 15th the decision was made that the current |
This means that the directory access branch is in fact no longer needed. However, it should still be left intact, especially the DAC_v0.5.1rc2 tag which is used by the SOCCRATES project. After the SOCCRATES project deems it no longer necessary the directory access branch should be removed. |
Since we are using This is not currently an issue since the disclose, search, and read levels would be needed for discovery and reconnaissance purposes, which coreLang does not currently cover anyway. The auth would be needed if we decide to implement an |
The directory_access_control branch was introduced to provide directory access control modelling capabilities.
This was requested by Victor from foreseeti for a language they are developing. Once this language has matured we should permanently resolve this branch. Until then the branch should be kept up to date when a release is made and master should be merged into it.
The current opinion is that we do not want want to include two distinct access control models in coreLang and therefore this branch should be removed. However, we may decide that the benefits of the two different models are worthwhile and we can merge the changes into master.
The text was updated successfully, but these errors were encountered: