The Privacy by Design SDK version 0.4.0 is now available.
What's new? A new feature - the Data Privacy Inspector (DPI).
Scan content and return a score on the likelihood of it containing private data. Use the default settings or build your own DPI object and train it.
It looks like pbd could use some effort on its documentation. For instance, the summary documentation of most of the modules reads "Background", which isn't very informative.
I only read the dsg documentation with any thoroughness, and am very confused as to why its functions are written as a trait at all. Is the idea to make it easier to swap out a different cryptographic scheme? If so, it would seem worth discussing that. Similarly, since all the methods have default implementations, it would seem worth documenting which ones can be replaced in which ways without introducing cryptographic weaknesses. If the goal isn't for users to replace those implementations, then don't make it a trait.
Thank you for the constructive feedback. It's always good to have a second pair of eye and perspective.
The summary documentations that reads "Background" should be changed to a short description. There is full documentation in each module.
The idea of bundling the dsg methods into a trait is to allow developers to include the dsg functionality in their own Structs by implementing the trait. This allows them to extend the functionality of their own objects without having to manage a separate object.
But it looks to me like it doesn't need to be methods on a type at all, and could just be free functions, which I'd find less confusing.
I try to follow Object Oriented Design practices so that developers using the SDK can use it for their own OO Projects.
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.